Bug#873613: systemd gets confused at shutdown time

Felipe Sateler fsateler at debian.org
Tue Aug 29 15:17:03 BST 2017


Control: tags -1 moreinfo

On Tue, Aug 29, 2017 at 10:35 AM, Harald Dunkel <harald.dunkel at aixigo.de> wrote:
> Package: systemd
> Version: 232-25+deb9u1
>
> At shutdown time systemd just shows a message saying
>
>         watchdog: watchdog0: watchdog did not stop!
>
> for 5 minutes :-(.
>
> If I boot without quiet, then systemd reveals that it gets
> confused by service dependencies, nfs mount points and
> probably some virtual block devices (mdadm, lvm2, crypt,
> etc).

Please attach the full configuration for your mount points.

> Basic problem seems to be indicated by the message
>
>         nfs: server nfs-home not responding, timed out
>

Looks like systemd shut down your network before it unnmounted remote
filesystems.

> pretty late at shutdown time. 90 secs before it tried to
> unmount the local mount points. Apparently it ignored NFS
> completely. No wonder that it got stuck.
>
> Would you mind to check and fix for stretch?

Could you attach full logs? Attaching the info generated by reportbug
would be useful too.


-- 

Saludos,
Felipe Sateler




More information about the Pkg-systemd-maintainers mailing list