Re: question about a poweroff issue

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Mi, 26.02.20 13:50, piliu (piliu@xxxxxxxxxx) wrote:

> Hi,
>
> I encountered a systemd bug during saving vmcore for kdump kernel.
>
> I got the following message:
>
> [   60.283489] systemd[1]: Started Reload Configuration from the Real Root.
> [   60.290912] systemd[1]: Reached target Initrd File Systems.
> [   60.296162] systemd[1]: Reached target Initrd Default Target.
> [   60.299343] systemd[1]: Starting dracut pre-pivot and cleanup hook...
>          Starting dracut pre-pivot and cleanup hook...
> [  OK  ] Started dracut pre-pivot and cleanup hook.
> [   60.338320] systemd[1]: Started dracut pre-pivot and cleanup hook.
> [   60.340503] systemd[1]: Starting Kdump Vmcore Save Service...
>          Starting Kdump Vmcore Save Service...
> kdump: dump target /dev/mapper/rhel_storageqe--25-root is not mounted,
> trying to mount...
> kdump: saving to
> /sysroot//mnt/kdump_multi/var/crash/127.0.0.1-2020-02-20-05:00:45/
> kdump: saving vmcore-dmesg.txt
> kdump: saving vmcore-dmesg.txt complete
> kdump: saving vmcore
> Copying data                                      : [100.0 %] /
>  eta: 0s
> kdump: saving vmcore complete
> Bus n/a: changing state UNSET → OPENING
> Bus n/a: changing state OPENING → AUTHENTICATING
> 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=Reboot cookie=1
> reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
> [   66.032946] systemd[1]: Shutting down.
> Got message type=method_return sender=org.freedesktop.systemd1
> destination=n/a path=n/a interface=n/a member=n/a cookie=1
> reply_cookie=1 signature=n/a error-name=n/a error-message=n/a
> Bus n/a: changing state RUNNING → CLOSED
> [   66.060777] printk: systemd-shutdow: 350 output lines suppressed due
> to ratelimiting
> [   66.316784] printk: systemd-journal: 13 output lines suppressed due
> to ratelimiting
> [  156.506161] qla2xxx [0000:08:00.1]-fffa:1: Adapter shutdown
> [  156.535660] qla2xxx [0000:08:00.1]-00af:1: Performing ISP error
> recovery - ha=00000000350c9f53.
> [  156.581142] qla2xxx [0000:08:00.1]-fffe:1: Adapter shutdown successfully.
> [  156.612816] qla2xxx [0000:08:00.0]-fffa:0: Adapter shutdown
> [  156.638997] qla2xxx [0000:08:00.0]-00af:0: Performing ISP error
> recovery - ha=000000007acbb643.
> [  156.681032] qla2xxx [0000:08:00.0]-fffe:0: Adapter shutdown successfully.
>
>
> In the kdump script, for the final step, it calls "systemctl reboot -f".
> But it seems the system is experiencing poweroff instead of reboot.

Pass "printk.devkmsg=on" so that you can actually see the debug output
of systemd-shutdown. It might tell you what is going on.

> Further more, in kdump script, even if I placed "sleep 60" before
> "systemctl reboot -f", the extra command did not take effect, and the
> system just start to poweroff immediately. So I guess there is another
> process to launch the poweroff action, but how to know what is it?

Enable debug logging, and use "printk.devkmsg=on", then you should be
able to figure out what is going on.

https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1

Lennart

--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel