Hi Lennart,
The issue reproduced at 2021-04-22T15:45:30.230Z, I ran 'sudo journalctl -b',
the log began at Apr 22 15:45:48 which is later than the issue reproduced.
How can I get more early and detailed systemd log?
--
Best regards,
Pengpeng
On 2021/4/23, 4:01 PM, "Lennart Poettering" <lenn...@poettering.net> wrote:
On Di, 20.04.21 16:48, Pengpeng Sun (pengpe...@vmware.com) wrote:
> Thanks Lennart!
> I reproduced the issue after set "systemd-analyze log-level debug". It
turns out 'systemctl reboot' triggered before all the steps logged in
'journalctl -a'. But I did get the stderr of 'systemctl reboot', paste it as
below, please check if it helps to locate the root cause.
> And besides 'journalctl -a', where can I get the systemd debug logs?
>
> stderr: Bus n/a: changing state UNSET → OPENING
> Bus n/a: changing state OPENING → AUTHENTICATING
> Executing dbus call org.freedesktop.systemd1.Manager
StartUnit(reboot.target, replace-irreversibly)
> Bus n/a: changing state AUTHENTICATING → RUNNING
> Sent message type=method_call sender=n/a
destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1
interface=org.freedesktop.systemd1.Manager member=StartUnit cookie=1
reply_cookie=0 signature=ss error-name=n/a error-message=n/a
> Got message type=method_return sender=org.freedesktop.systemd1
destination=n/a path=n/a interface=n/a member=n/a cookie=5 reply_cookie=1
signature=o error-name=n/a error-message=n/a
> Sent message type=method_call sender=n/a
destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1
interface=org.freedesktop.systemd1.Manager member=GetUnit cookie=2
reply_cookie=0 signature=s error-name=n/a error-message=n/a
That looks like the debug log of systemctl on the client side? I was
more interested int the logs of systemd, i.e. of PID 1.
Lennart
--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
