Greetings, I don't know this one, but my first inclination would be to modify your grub boot. Remove the bits that you don't absolutely need (eg: quiet) and add rd.break to get in as root. If that works, maybe you can explore the issue a bit more. If not, maybe something in the messages on the screen will give you a hint as to what to try next.
Do your servers support serial output? Can you possibly connect from another server/laptop in order to watch the boot process? That helps sometimes when the messages scroll past the screen way too fast. ~Stack~ On 5/4/19 3:47 AM, Bill Maidment wrote: > 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 <[email protected]> >> Sent: Saturday 4th May 2019 18:16 >> To: [email protected] >> 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 >
signature.asc
Description: OpenPGP digital signature
