OpenVZ Hangs on PAE Kernel [message #15778] |
Sun, 12 August 2007 15:29 |
|
I am trying to run the OpenVZ PAE kernel with 8 gigs of ram to back the server, however the server keeps suffering from hangings.
It starts 2 or 3 vpses fine, but once it hits 4 or so, it hangs without a kernel panic or any other proper error message.
The kernel version is 2.6.18-8.1.8.el5.028stab039.1PAE but it also does it on 2.6.18-ovz028stab039.1-enterprise
Anybody have the same problem and come up with a solution? Node is running CentOS 5. Thanks.
BTW: The server is running a 32 bit os.
|
|
|
|
Re: OpenVZ Hangs on PAE Kernel [message #15784 is a reply to message #15778] |
Mon, 13 August 2007 05:45 |
vaverin
Messages: 708 Registered: September 2005
|
Senior Member |
|
|
Hi Ryan,
Could you please describe the node state in more details:
- is the node accessible via ssh?
- is the node pingable?
- what happened on active shells? do you have any reaction on keyboard?
- do you have local console? couls you try to use Magic Sysrq keys?
http://wiki.openvz.org/Magic_SysRq_Key
- could you please attach remote console (serial- or netconsole ) to node log collection?
http://wiki.openvz.org/Remote_console_setup
Is the problem reproduceable?
In general in case of node hangs the troubleshooting procedure is following:
- attach remote console and tune the node logs collection
- reproduce the hang
- describe the node state by using Magic SysRq keys:
We need to know:
"Show Pc" (alt+sysrq+p) -- several times
"Show CPUs" (alt+sysrq+w) -- several times too
This debug describes the state of CPUs, what the tasks they executed.
Then please press "Show Tasks" (alt+sysrq+t). this debug outputs information about all the tasks on the node and it may take a lot of time, up to several minutes or even more, depending on number of processes running on your node. It is most important information, and it should be collected without the loss. In case of local logs some part of this information is loses, that why it's important to attach the remote console to the node.
Then please press again alt+sysrq+p and alt+sysrq+w again,
then "Show Mem" (alt+sysrq+m) and "Show Vsched" (alt+sysrq+V).
Now you can reboot the node and send the colected logs to us, via attachement or via bugzilla:
http://bugzilla.openvz.org/
thank you,
Vasily Averin
|
|
|
|
Re: OpenVZ Hangs on PAE Kernel [message #16208 is a reply to message #15784] |
Tue, 28 August 2007 03:58 |
WireSix
Messages: 3 Registered: August 2007
|
Junior Member |
|
|
Q: is the node accessible via ssh?
A: no, entirely offline, unpingable
Q: is the node pingable?
A: see above
Q: what happened on active shells? do you have any reaction on keyboard?
A: nothing, totally dead
Q: do you have local console? couls you try to use Magic Sysrq keys?
A: KVM/IP is available, absolutely no response, also tried on local console, no response
Q: could you please attach remote console (serial- or netconsole ) to node log collection?
A: installed and netconsole had no output different from true console.
vaverin wrote on Mon, 13 August 2007 01:45 | Hi Ryan,
Could you please describe the node state in more details:
- is the node accessible via ssh?
- is the node pingable?
- what happened on active shells? do you have any reaction on keyboard?
- do you have local console? couls you try to use Magic Sysrq keys?
http://wiki.openvz.org/Magic_SysRq_Key
- could you please attach remote console (serial- or netconsole ) to node log collection?
http://wiki.openvz.org/Remote_console_setup
Is the problem reproduceable?
In general in case of node hangs the troubleshooting procedure is following:
- attach remote console and tune the node logs collection
- reproduce the hang
- describe the node state by using Magic SysRq keys:
We need to know:
"Show Pc" (alt+sysrq+p) -- several times
"Show CPUs" (alt+sysrq+w) -- several times too
This debug describes the state of CPUs, what the tasks they executed.
Then please press "Show Tasks" (alt+sysrq+t). this debug outputs information about all the tasks on the node and it may take a lot of time, up to several minutes or even more, depending on number of processes running on your node. It is most important information, and it should be collected without the loss. In case of local logs some part of this information is loses, that why it's important to attach the remote console to the node.
Then please press again alt+sysrq+p and alt+sysrq+w again,
then "Show Mem" (alt+sysrq+m) and "Show Vsched" (alt+sysrq+V).
Now you can reboot the node and send the colected logs to us, via attachement or via bugzilla:
http://bugzilla.openvz.org/
thank you,
Vasily Averin
|
|
|
|
|