tom Proxmox Staff Member Staff member Aug 29, 2006 15,893 1,137 273 Feb 21, 2013 #2 restart pvestatd. #/etc/init.d/pvestatd restart and also update your packages to last stable. see http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_2.x_to_latest_2.2
restart pvestatd. #/etc/init.d/pvestatd restart and also update your packages to last stable. see http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_2.x_to_latest_2.2
I Ismael Zarco Lamas Guest Feb 21, 2013 #3 In one cluster OK, in other i have this: root@ns204xxx:/# /etc/init.d/pvestatd restartRestarting PVE Status Daemon: pvestatdERROR: can't aquire lock '/var/run/pvestatd.pid.lock' - Recurso no disponible temporalmente (warning). Click to expand...
In one cluster OK, in other i have this: root@ns204xxx:/# /etc/init.d/pvestatd restartRestarting PVE Status Daemon: pvestatdERROR: can't aquire lock '/var/run/pvestatd.pid.lock' - Recurso no disponible temporalmente (warning). Click to expand...
I Ismael Zarco Lamas Guest Feb 21, 2013 #4 2 clusters still are in red - - - Updated - - - tom said: and also update your packages to last stable. see http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_2.x_to_latest_2.2 Click to expand... I have the lastest version in 2 nodes
2 clusters still are in red - - - Updated - - - tom said: and also update your packages to last stable. see http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_2.x_to_latest_2.2 Click to expand... I have the lastest version in 2 nodes