Hi Neil, Well, that shouldn't happen ;) Could you please send us a backtrace with the gdb? If the process still can be attached to, you can use
$ gdb $ONE_LOCATION/bin/oned <oned-pid> then, in the (gdb) prompt (gdb) bt and send us the output. If this is not possible, could you please set you system to produce core files, and send it to us (it should appear under $ONE_LOCATION/var after the oned crashed again). To achieve this: $ ulimit -c unlimited Best regards, -Tino -- Constantino Vázquez Blanco | dsa-research.org/tinova Virtualization Technology Engineer / Researcher OpenNebula Toolkit | opennebula.org On Fri, Jul 30, 2010 at 11:07 AM, Neil Mooney <neil.moo...@sara.nl> wrote: > Oned just crashed , leaving just this message in the log: > > [2046071.765934] oned[17361] general protection ip:7feaaee82e0a > sp:7feaa5fcc940 error:0 in libc-2.11.2.so[7feaaee11000+158000] > > Our distro is Debian / squeeze running a 2.6.32-5-amd64 kernel. > > We are seeing crashes quite often now, considering auto-restarting from > nagios or similar ... > > Cheers > > Neil > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org