Weird Network Error

Home » CentOS » Weird Network Error
CentOS 1 Comment

a previously rock solid reliable server of mine crashed last night, the server was still running but eth0, a Intel 82574L using the e1000e driver, went down. The server has a Supermicro X8DTE-F (dual Xeon X5650, yada yada). server is a drbd master, so that was the first thing to notice network issues. Just a couple days ago I ran yum update to the latest, I do this about once a month.

/var/log/messages logged…

(prior to this was nothing but normal smbd complaining about CUPS not configured).

May 9 22:30:21 sg1 kernel: block drbd0: PingAck did not arrive in time. May 9 22:30:21 sg1 kernel: block drbd0: peer( Secondary -> Unknown )
conn( Connected -> NetworkFailure ) pdsk( UpToDate -> DUnknown )
May 9 22:30:21 sg1 kernel: block drbd0: asender terminated May 9 22:30:21 sg1 kernel: block drbd0: Terminating drbd0_asender May 9 22:30:22 sg1 kernel: block drbd0: new current UUID
BC856D7A6F94F041:237F4033E81B62DF:1E248D699B6793A9:1E238D699B6793A9
May 9 22:30:22 sg1 kernel: block drbd0: Connection closed May 9 22:30:22 sg1 kernel: block drbd0: conn( NetworkFailure ->
Unconnected )
May 9 22:30:22 sg1 kernel: block drbd0: receiver terminated May 9 22:30:22 sg1 kernel: block drbd0: Restarting drbd0_receiver May 9 22:30:22 sg1 kernel: block drbd0: receiver (re)started May 9 22:30:22 sg1 kernel: block drbd0: conn( Unconnected ->
WFConnection )
May 9 22:30:34 sg1 kernel: ————[ cut here ]———-

One thought on - Weird Network Error

  • John R Pierce wrote:


    This is going to sound really stupid, but consider replacing the patch cord. If that doesn’t work… should I assume that this m/b has at least two embedded NIC? If so, try using the other NIC.

    mark “I haven’t done both of those in the last few months, no….”