pvestatd died or lock inside cos of nfs storage absense

I

immo

Renowned Member
Nov 20, 2014
96
1
73
We had a nfs server fault. It looks like that due to this the pvestatd died as well and didnt restart. Is that a bug or a feature ?

Mar 22 11:48:43 prox01 pvestatd[26389]: got timeout
Mar 22 11:48:43 prox01 pvestatd[26389]: status update time (5.253 seconds)
Mar 22 11:50:12 prox01 pvestatd[26389]: got timeout
Mar 22 11:50:12 prox01 pvestatd[26389]: status update time (5.250 seconds)
Mar 22 11:51:33 prox01 pvestatd[26389]: got timeout
Mar 22 11:51:33 prox01 pvestatd[26389]: status update time (5.253 seconds)


since 11:51 there was no further update for the proxmox gui and it looked like cluster is down. But VMs which are not hosted on this nfs server whwre running fine.

Only a restart of the pvestatd solved this.
Which kind of logs do you need for further analysis ?
 
Hi, if a storage has problems something like this can happen. You can disable storages:

Code: 
pvesm set <storagename> --disable 1
 
You must log in or register to reply here.
Top Bottom