<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Dear Ante, That's what I thought; hence the reason I ask if some how passing it up to the OS could trigger the reboot. In that case, is there any way you suggest I could remotely debug the cause of this reboot that I can only recreate in the circumstances described?? Thanks, Henri Ante Karamatic wrote: <blockquote cite="mid:20080906160857.068e159a@titanium" type="cite"> <pre wrap="">On Sat, 06 Sep 2008 11:40:37 +0100 Henri Cook <a class="moz-txt-link-rfc2396E" href="mailto:ubuntu-server@theplayboymansion.net"><ubuntu-server@theplayboymansion.net></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">What i'm wondering is - could DRBD be passing this networkfailure event up to the kernel somehow and triggering a reboot - does a machine ever auto-reboot on network failure? At the moment i'm looking at it as a DRBD problem but didn't want to narrow my scope too early. </pre> </blockquote> <pre wrap=""> DRBD doesn't do that. DRBD can detect that other machine is down, but it doesn't do reboots. Whole purpose of DRBD is two keep filesystem going on the other node :) Unless you configured it to do reboots on network failure. Check you /etc/drbd.conf </pre> </blockquote> </body> </html>