Cannot remove / destroy

J

JustaGuy

Renowned Member
Jan 1, 2010
324
2
83
When I try to remove this machine, I get "failed to remove". That's the best I get out of the logs.
/var/log/faillog is full of cryptic characters:
var-log-faillog..jpgfailsyslog..jpg

pveversion says:
pve-manager/1.5/4660
kernel is 2.6.32-1-pve

This is a machine that froze & was preventing the pve host from rebooting.
After reinstalling from the new iso, it ran fine for about a week & here we are again.
I wound up rebooting with the power button & doing another vzrestore.
So far this restoration's ok, after a day.
 
the screenshots aren´t readable here, too small.

a sidenote: if you run 2.6.32, so you have no OpenVZ. so you can´t use vzrestore, you mean qmrestore?
 
the screenshot is well now, but not showing the whole info. take a look on the syslog via console (the logfile is here: /var/log/syslog)
 
take a look on the syslog
Click to expand...
I downloaded /var/log/syslog as soon as I got in this morning & it was too late to see what happened.
One good thing is that it did show that a machine whose backup occurs 3 machines later than the one in question completed with errors, which I wouldn't have been aware of otherwise.
Shouldn't there have been an email about that?

"Administration/Logs/Tasks" - any hint there?
Click to expand...
I never knew the rows in the "Finished Maintainance Tasks" column were clickable.
This indicates the freeze problem I tried to resolve with a reboot was compounded by my using the power button to force it through.

Under it's start command says:
/usr/sbin/qm start 100
VM is locked (backup)
VM 100 start failed -

Another problem that I posted about here immediateley comes to mind with regard to snapshot backups behaving like I'd imagine a suspend backup would.

There have been numerous proper reboots since the power button-triggered power down. Seems pve doesn't know there's a lock to release anymore.

How does one handle this?
 
Last edited:
syslog files are stored for 7 days, for each day one new file (standard on Debian Linux systems). the rotation happens in the morning, in my case 6:25 am.

just type the following to see all syslogs:

Code: 
ls -allh /var/log/sys*
-rw-r----- 1 root adm 181K Feb 20 16:52 /var/log/syslog
-rw-r----- 1 root adm 461K Feb 20 06:25 /var/log/syslog.1
-rw-r----- 1 root adm 26K Feb 19 06:25 /var/log/syslog.2.gz
-rw-r----- 1 root adm 26K Feb 18 06:25 /var/log/syslog.3.gz
-rw-r----- 1 root adm 26K Feb 17 06:25 /var/log/syslog.4.gz
-rw-r----- 1 root adm 25K Feb 16 06:25 /var/log/syslog.5.gz
-rw-r----- 1 root adm 25K Feb 15 06:25 /var/log/syslog.6.gz
-rw-r----- 1 root adm 27K Feb 14 06:25 /var/log/syslog.7.gz

if a VM is locked (e.g. because of failed backup), just unlock it.

Code: 
qm unlock VMID
see also the man pages of 'qm' for a complete reference:
Code: 
man qm
 
You must log in or register to reply here.
Top Bottom