Node with question mark

[Zaman]

ilo/ibmc or sth?

Then try open support ticket to reboot it for u

 

[uzair]

ilo/ibmc or sth?

Sorry I didn't get it

 

[uzair]

Then try open support ticket to reboot it for u

How's it possible? My proxmox environment is hosted on a private ip scheme so how would the tech support reboot it for me ?

 

[yuvalattar]

@Rebirthz check whether all the storage devices are online and accessible

 

[usridzero]

hey guys,
I'm having the same issue and was able to fix it with `systemctl restart pvestatd`.

While looking at the journal for the pvestatd I saw this:
```
Dec 17 17:17:35 pve pvestatd[1442]: auth key pair too old, rotating..
Dec 18 15:59:16 pve systemd[1]: pvestatd.service: Main process exited, code=killed, status=11/SEGV
Dec 18 15:59:16 pve systemd[1]: pvestatd.service: Failed with result 'signal'.
Dec 18 15:59:16 pve systemd[1]: pvestatd.service: Consumed 4min 23.492s CPU time.
Dec 22 19:58:10 pve systemd[1]: Starting pvestatd.service - PVE Status Daemon...
```

Can anyone explain what's going on with the key pairs? Thanks

 

[BrUz]

hey guys,
I'm having the same issue and was able to fix it with `systemctl restart pvestatd`.

While looking at the journal for the pvestatd I saw this:
```
Dec 17 17:17:35 pve pvestatd[1442]: auth key pair too old, rotating..
Dec 18 15:59:16 pve systemd[1]: pvestatd.service: Main process exited, code=killed, status=11/SEGV
Dec 18 15:59:16 pve systemd[1]: pvestatd.service: Failed with result 'signal'.
Dec 18 15:59:16 pve systemd[1]: pvestatd.service: Consumed 4min 23.492s CPU time.
Dec 22 19:58:10 pve systemd[1]: Starting pvestatd.service - PVE Status Daemon...
```

Can anyone explain what's going on with the key pairs? Thanks

Same here, restart of pvestatd helped!

pve: 8.3.3