I’ve been having problems with a remote system failing to reboot and having to ask somebody to power it off and on. I have an idea the problem is due to an NFS mount but I can’t find boot.omsg after I restart so I’m unable to see the shutdown log.
Can anyone advise if something needs to be changed to get this log and/or is it somewhere else.
On 2015-07-08 21:56, davidlwilcox wrote:
>
> I’ve been having problems with a remote system failing to reboot and
> having to ask somebody to power it off and on. I have an idea the
> problem is due to an NFS mount but I can’t find boot.omsg after I
> restart so I’m unable to see the shutdown log.
>
> Can anyone advise if something needs to be changed to get this log
> and/or is it somewhere else.
Since systemd that file is deprecated, years ago. Depending on the
openSUSE version you would look at /var/log/messages or at the command
journalctl output.
However, if your machine boots using plymouth, which is doubtful for a
remote or headless machine, then this creates a boot.log file, I think.
Unsure it contains all the data, though. I would not rely on it.
Having now found that I can look at the previous boot using journalctl is there any quick way to get to the shutdown messages. All I seem to be able to do at the moment is have to search through a lot of data to get to the last bit.
On 2015-07-09 15:26, arvidjaar wrote:
>
> davidlwilcox;2718906 Wrote:
>> Having now found that I can look at the previous boot using journalctl
>
> journalctl -b -1
And then hit the ‘end’ key to get to the end of the halt sequence.
> Note also the the old methosds can also be installed if you want/need
> the old log files
yep.
I have a local service that writes a marker to the logs. A line that I
can easily search for to locate a boot or a halt. I got valuable help in
these forums to get the trick working on systemd
For example, if I see the boot start line, without a corresponding halt
line just above, I know for certain that the previous session crashed.