[SOLVED] Changing IP for pvestatd

[PacDDrake]

I have recently changed the IP for my HomeLab from '192.168.178.54' to '192.168.178.169'.

Since doing so pvestatd still tries to connect to the old IP, which leads to a timeout and all my system info in the web interface not being accessible.

Jun 25 09:55:16 pve pvestatd[1639]: lxc status update error: couldn't create carbon socket [192.168.178.54]:3000 - Connection timed out
Jun 25 09:55:17 pve pvestatd[1639]: storage status update error: couldn't create carbon socket [192.168.178.54]:3000 - Connection timed out
Jun 25 09:55:24 pve pvestatd[1639]: node status update error: couldn't create carbon socket [192.168.178.54]:3000 - Connection timed out
Jun 25 09:55:25 pve pvestatd[1639]: qemu status update error: couldn't create carbon socket [192.168.178.54]:3000 - Connection timed out

How can I point pvestatd to the right IP to get status updates running again?

 

[mira]

You have to update your /etc/hosts file with your new IP.

 

[PacDDrake]

Already done that when I had the problem that the welcome message did still show the old IP.

IPv4 config in /etc/hosts:

127.0.0.1 localhost.localdomain localhost
192.168.178.169 pve.fritz.box pve

I have also already rebooted and restarted pvestatd multiple times.

 

[mira]

Have you updated your metrics server entry?
`couldn't create carbon socket` would hint at an old entry there.

 

[PacDDrake]

The metrics server apparently got shut down and got assigned a new IP when rebooted.
I have fixed the issue by setting it on a static IP and updating the entry for the metrics server.

TL;DR: If you have a metrics server configured that cannot be reached pvestatd will apparently not update the status of your devices in the web GUI either.
Deleting or fixing the metrics server entry fixed the Issue for me.