VM container won't start-up after VE hard shut-down
- Thread starter Petrus4
- Start date
Some more info:
command logs
/usr/sbin/vzctl start 101
Starting container ...
vzquota : (warning) Incorrect quota shutdown for id 101, recalculating disk usage
vzquota : (error) quota check : lstat `sess_1c7d0cab3baa429af3a6a632785c40ec': No such file or directory
vzquota on failed [1]
VM 101 start failed -
INIT LOG
starting init logger
* Setting preliminary keymap... [ OK ]
* Starting basic networking... [ OK ]
* Loading kernel modules... * Loading manual drivers... [ OK ]
* Setting kernel variables... [ OK ]
* Activating swap... [ OK ]
mount: permission denied
* Mounting local filesystems... [ OK ]
* Activating swapfile swap... [ OK ]
* Checking minimum space in /tmp... [ OK ]
* Skipping firewall: ufw (not enabled)... [ OK ]
* Configuring network interfaces... [ OK ]
* Starting system log daemon... [ OK ]
* Starting OpenBSD Secure Shell server sshd [ OK ]
* Starting MySQL database server mysqld [ OK ]
* Checking for corrupt, not cleanly closed and upgrade needing tables.
* Starting ClamAV virus database updater freshclam [ OK ]
* Starting internet superserver inetd [ OK ]
* Starting Postfix Mail Transport Agent postfix [ OK ]
* Starting deferred execution scheduler atd [ OK ]
* Starting periodic command scheduler crond [ OK ]
* Starting web server apache2 [ OK ]
* Running local boot scripts (/etc/rc.local) [ OK ]
command logs
/usr/sbin/vzctl start 101
Starting container ...
vzquota : (warning) Incorrect quota shutdown for id 101, recalculating disk usage
vzquota : (error) quota check : lstat `sess_1c7d0cab3baa429af3a6a632785c40ec': No such file or directory
vzquota on failed [1]
VM 101 start failed -
INIT LOG
starting init logger
* Setting preliminary keymap... [ OK ]
* Starting basic networking... [ OK ]
* Loading kernel modules... * Loading manual drivers... [ OK ]
* Setting kernel variables... [ OK ]
* Activating swap... [ OK ]
mount: permission denied
* Mounting local filesystems... [ OK ]
* Activating swapfile swap... [ OK ]
* Checking minimum space in /tmp... [ OK ]
* Skipping firewall: ufw (not enabled)... [ OK ]
* Configuring network interfaces... [ OK ]
* Starting system log daemon... [ OK ]
* Starting OpenBSD Secure Shell server sshd [ OK ]
* Starting MySQL database server mysqld [ OK ]
* Checking for corrupt, not cleanly closed and upgrade needing tables.
* Starting ClamAV virus database updater freshclam [ OK ]
* Starting internet superserver inetd [ OK ]
* Starting Postfix Mail Transport Agent postfix [ OK ]
* Starting deferred execution scheduler atd [ OK ]
* Starting periodic command scheduler crond [ OK ]
* Starting web server apache2 [ OK ]
* Running local boot scripts (/etc/rc.local) [ OK ]
SOLVED: Re: VM container won't start-up after VE hard shut-down
It turns out the containers quota system was crashed and I had to reset it by the doing the following command:
101 is the VMID so fill in your own ID of your crashed VM
After that the contaner booted up with no issues.
I then had to repair my mysql tables but that has nothing to do with the container not booting up.
Problem Solved!
It turns out the containers quota system was crashed and I had to reset it by the doing the following command:
Code:
# vzquota off 101
# vzquota on 101101 is the VMID so fill in your own ID of your crashed VM
After that the contaner booted up with no issues.
I then had to repair my mysql tables but that has nothing to do with the container not booting up.
Problem Solved!
