Backup process don't work correct

N

nick

Renowned Member
Mar 28, 2007
364
1
83
Hi all,

I just discover in 1 PVE server that after 1 working period when everything is normal, the backup process don't start anymore. If I reboot the server, everything is back to normal, but after another period, again...same issue.

Where I need to search for this error?

Thank you.
 
take a look on the backup logs (/var/log/vzdump/)
 
here are the logs of backup's. All files are looking ok...and successful backups! Last file Feb. 15'th. And I have daily backup jobs!
 
hi
what I've seen here is a vzdump process hanging (for different reasons) - then no new backups are made until one kills this hung process..
 
I look in syslog but nothing unusual...a lot of cluster synchronization logs...and that's it. I don't see error logs.

How can I restart the backup process?

I try to restart cron process and this was the output:

Code: 
Feb 25 17:52:51*
cron
17847*
(CRON) INFO (pidfile fd = 3)
Feb 25 17:52:51*
cron
17848*
(CRON) STARTUP (fork ok)
Feb 25 17:52:51*
cron
17848*
(CRON) INFO (Skipping @reboot jobs -- not system startup)
Feb 25 17:53:15*
cron
17920*
(CRON) INFO (pidfile fd = 3)
Feb 25 17:53:15*
cron
17921*
(CRON) STARTUP (fork ok)
Feb 25 17:53:15*
cron
17921*
(CRON) INFO (Skipping @reboot jobs -- not system startup)
Feb 25 17:53:30*
proxwww
17926*
Starting new child 17926
Feb 25 17:53:44*
pvedaemon
1973*
WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 25 17:53:44*
proxwww
17928*
Starting new child 17928
Feb 25 17:53:44*
pvedaemon
11754*
WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 25 17:53:49*
pvemirror
4141*
starting cluster syncronization
Feb 25 17:53:49*
pvemirror
4141*
syncing templates
Feb 25 17:53:49*
pvemirror
4141*
cluster syncronization finished (0.09 seconds (files 0.00, config 0.00))
Feb 25 17:53:49*
pvedaemon
11754*
WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 25 17:53:50*
pvedaemon
11754*
WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 25 17:53:58*
pvedaemon
11754*
WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 25 17:54:00*
pvedaemon
11754*
WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 25 17:54:04*
pvedaemon
11754*
WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 25 17:54:05*
pvedaemon
11754*
WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 25 17:54:09*
pvedaemon
11754*
WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 25 17:54:11*
pvedaemon
1973*
WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 25 17:54:16*
pvedaemon
11754*
WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 25 17:54:16*
pvedaemon
1973*
WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 25 17:54:49*
pvemirror
4141*
starting cluster syncronization
Feb 25 17:54:49*
pvemirror
4141*
syncing templates
Feb 25 17:54:49*
pvemirror
4141*
cluster syncronization finished (0.06 seconds (files 0.00, config 0.00))
Feb 25 17:55:01*
cron
17958*
(root) CMD (/usr/share/vzctl/scripts/vpsnetclean)
Feb 25 17:55:01*
cron
17959*
(root) CMD (/usr/share/vzctl/scripts/vpsreboot)
 
I don't see anything. Maybe if I give you all log files into a zip...
 
I still look in log's but no records regarding VZdump....

Anyway I reboot the server and everything it's back to normal. I will try to make a hardware test...maybe it's a hardware failure.
 
You must log in or register to reply here.
Top Bottom