I updated one of our nodes today (subscription repository). The node was running kernel version 2.6.32-23-pve before, update ended without any errors or warnings.
At first reboot the system locked up after starting the first container.
After disabling any Container or VM via single-user mode and editing the config files, the system hangs after the message:
"startpar: service(s) returned failure: apache2 ... failed!
With apache2 disabled the host starts up, i can get to management console and ssh, but as soon as i start up any VM or container, the system locks up again...
The system then sits there for a while, then starts to drop random tasks with "blocked for more than 120seconds" messages.
I can still type but the system doesn't respond - ping goes through, but sshd is not running, so i can't get into the system.
no response to any keyboard input to reboot it, so i have to colt-reset the machine...
no errors (except the "blocked for more...") in syslog or kern.log
I'm pretty down with ideas where to start - disks are clean, RAM is OK (according to fsck and memtest)...
At first reboot the system locked up after starting the first container.
After disabling any Container or VM via single-user mode and editing the config files, the system hangs after the message:
"startpar: service(s) returned failure: apache2 ... failed!
With apache2 disabled the host starts up, i can get to management console and ssh, but as soon as i start up any VM or container, the system locks up again...
The system then sits there for a while, then starts to drop random tasks with "blocked for more than 120seconds" messages.
I can still type but the system doesn't respond - ping goes through, but sshd is not running, so i can't get into the system.
no response to any keyboard input to reboot it, so i have to colt-reset the machine...
no errors (except the "blocked for more...") in syslog or kern.log
I'm pretty down with ideas where to start - disks are clean, RAM is OK (according to fsck and memtest)...