Just had a kernel panic with 2.6.32-042stab037.1 Is that the latest stock kernel? No details in /var/log/messages, all I have is a screenshot of the Call Trace from the console: Would it make sense installing kdump in case it happens again? kdump wants to install busybox, whats the implications of that? Should I open a bug report with OpenVZ when all I have is a screenshot?
Re: kernel panic with 2.6.32-042stab037.1
We got the similar problem on three different servers during a one day. All of them are CentsOS 5.7 64bit with the latest RHEL6 kernel 2.6.32-042stab039.2 We have two crash screenshots from the console also. Must we open a bug on bugzilla ?
Also have problem with HNs and newer kernel then 2.6.32-042stab018.1.
Dear all, If you have kernel crashes please follow these instruction http://wiki.openvz.org/When_you_have_an_oops#If_you_have_had _an_oops shortly: - please switch to last released kernel, your issue can be fixed already. - please check your hardware and be sure that it isn't hardware-related issue - please configure remote console (serial- or netconsole) and to save kernel messages on another node. http://wiki.openvz.org/Remote_console_setup Alternatively you configure kdump, it allows to save kernel core dump. Kernel messages of crashed kernel can be extracted from this core dump - then please submit new bug to bugzilla.openvz.org thank you, Vasily Averin
Thanks for the input. So (according to the link you posted) it's ok to post a crash report with a screenshot. Good to know. Both kdump and remote console seems a lot of work just to get a coredump, don't those things happen automatically?