Containers show as stopped

dredfunk

New Member
May 17, 2015
5
0
1
Hello,

I don't know what happened but today when I logged in to the Proxmox GUI I noticed that all containers show as offline. No stats are being shown for any container. vzlist shows them as running. Any know what happened? Please see the screenshot below.

proxmox.jpg
 
is pvestatd daemon running? If not. try to start?

# service pvestatd start

Are there any hints in syslog?
 
pvestatd appears to be running:

root@vps3:~# service pvestatd status
running

syslog shows this:

May 18 13:17:53 vps3 pvestatd[3085]: openvz status update error: unable to parse config line: <=▒▒#177
May 18 13:17:53 vps3 pvestatd[3085]: openvz console cleanup error: unable to parse config line: <=▒▒#177
May 18 13:18:01 vps3 /USR/SBIN/CRON[461287]: (root) CMD (/nodewatch/php/bin/php /nodewatch/scripts/nodewatch_cron5min.php)
May 18 13:18:03 vps3 pvestatd[3085]: openvz status update error: unable to parse config line: <=▒▒#177
May 18 13:18:03 vps3 pvestatd[3085]: openvz console cleanup error: unable to parse config line: <=▒▒#177
May 18 13:18:13 vps3 pvestatd[3085]: openvz status update error: unable to parse config line: <=▒▒#177
May 18 13:18:13 vps3 pvestatd[3085]: openvz console cleanup error: unable to parse config line: <=▒▒#177
May 18 13:18:23 vps3 pvestatd[3085]: openvz status update error: unable to parse config line: <=▒▒#177
May 18 13:18:23 vps3 pvestatd[3085]: openvz console cleanup error: unable to parse config line: <=▒▒#177

Can you please advise what happened?

Thank you!
 
Hi Dietmar,

I did a grep inside all confs and this is what came up that matched 177:

root@vps3:/etc/vz/conf# grep 177 *
144.conf:DESCRIPTION="Client%3A CLIENT_NAME (ID%3A 467)%0D%0AEmail%3A EMAIL@gmail.com%0D%0ACompany%3A XY%0D%0A%0D%0AService ID%3A 751 (Provisioning%3A Auto)%0D%0AProduct%3A OpenVZ (ID%3A 177)"

Do you think there's something wrong with this line?
 
One config file contains an error - should be ease to find. You can try to move files out of the way for testing.