[DRBD-user] Pair rebooting issue

[Tony Lownds]

Hi

When one of my machines goes down, the other one reboots as well.
I've set handlers which should avoid this:

   handlers {
     pri-on-incon-degr "logger -p local2.emerg -t DRBD pri-on-incon- 
degr tripped";
     pri-lost-after-sb "logger -p local2.emerg -t DRBD pri-lost-after- 
sb tripped";
     local-io-error "logger -p local2.emerg -t DRBD local-io-error  
tripped";
     #outdate-peer "/usr/sbin/drbd-peer-outdater"; # needs more setup  
to use
   }

I'm using drbd 8.0.6 on the boxes. Below is the log of the machine  
that didn't crash, but
rebooted anyway.

Apr 26 04:02:42 fx-2 kernel: drbd0: PingAck did not arrive in time.
Apr 26 04:02:42 fx-2 kernel: drbd0: peer( Primary -> Unknown )  
conn( Connected -> NetworkFailure ) pdsk( UpToDate -> DUnknown )
Apr 26 04:02:42 fx-2 kernel: drbd0: asender terminated
Apr 26 04:02:42 fx-2 kernel: drbd0: Terminating asender thread
Apr 26 04:02:42 fx-2 kernel: drbd0: short read receiving data: read  
2448 expected 4096
Apr 26 04:02:42 fx-2 kernel: drbd0: error receiving Data, l: 4120!
Apr 26 04:02:42 fx-2 kernel: drbd0: Writing meta data super block now.
Apr 26 04:02:42 fx-2 kernel: drbd0: tl_clear()
Apr 26 04:02:42 fx-2 kernel: drbd0: Connection closed
Apr 26 04:02:42 fx-2 kernel: drbd0: conn( NetworkFailure ->  
Unconnected )
Apr 26 04:02:42 fx-2 kernel: drbd0: receiver terminated
Apr 26 04:02:42 fx-2 kernel: drbd0: receiver (re)started
Apr 26 04:02:42 fx-2 kernel: drbd0: conn( Unconnected -> WFConnection )
Apr 26 04:03:27 fx-2 syslogd 1.4.1: restart.

I can't see any kernel panics on the console because the machines are  
set up to reboot
automatically.

Any suggestions of what I should try next?

-Tony Lownds