SCIENTIFIC-LINUX-USERS Archives

May 2019

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Can't reboot after latest updates
From:
Bill Maidment <[log in to unmask]>
Reply To:
Bill Maidment <[log in to unmask]>
Date:
Sat, 4 May 2019 18:47:43 +1000
Content-Type:
text/plain
Parts/Attachments:
text/plain (21 lines) 
Correction. Every 2 minutes, not every 2 seconds.
I've advised my colleague to try a hard reboot to see if that gets us out of trouble.

 
-----Original message-----
> From:Bill Maidment <[log in to unmask]>
> Sent: Saturday 4th May 2019 18:16
> To: [log in to unmask]
> Subject: Can't reboot after latest updates
> 
> Hi
> Today, a colleague ran yum update on our SL7.6 server and after reboot the server refuses to start with the following message every 2 seconds:
> 
> System Journal ID 20156 – failed to send WATCHDOG=1 notification message.  Transport endpoint is not connected.
> 
> Any ideas how to fix this. Google shows this as an occasional issue, but with no specific help.
> .
> 
> Cheers
> Bill Maidment

ATOM RSS1 RSS2