Well the hard reboot has got the server running OK.
The logs show that a backup drive was at 100% full halfway through a backup in
April. This went unnoticed until the reboot.
Somehow the drive seemed to remain in an unstable state, which the hard reboot
cleared.
Cheers
Bill
-Original message-
> From:Bill Maidment
> Sent: Saturday 4th May 2019 18:47
> To: SCIENTIFIC-LINUX-USERS@FNAL.GOV
> Subject: RE: Can't reboot after latest updates
>
> 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
> > Sent: Saturday 4th May 2019 18:16
> > To: SCIENTIFIC-LINUX-USERS@FNAL.GOV
> > 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
