Your message dated Wed, 3 Apr 2019 00:28:11 +0200
with message-id <8d2b0dd0-47b8-a669-b0b2-c0abba668...@debian.org>
and subject line Re: Bug#873613: systemd gets confused at shutdown time
has caused the Debian Bug report #873613,
regarding systemd gets confused at shutdown time
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
873613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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). Basic problem seems to be indicated by the message
nfs: server nfs-home not responding, timed out
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?
Thanx in advance
Harri
--- End Message ---
--- Begin Message ---
On Wed, 14 Feb 2018 23:01:38 +0100 Michael Biebl <bi...@debian.org> wrote:
> On Fri, 1 Dec 2017 10:39:33 +0100 Harald Dunkel
> <harald.dun...@aixigo.de> wrote:
> > Hi Felipe,
> >
> > sorry for the delay.
> >
> > On 9/5/17 10:09 PM, Felipe Sateler wrote:
> > >
> > >
> > > On Mon, Sep 4, 2017 at 3:26 AM, Harald Dunkel <harald.dun...@aixigo.de
> > > <mailto:harald.dun...@aixigo.de>> wrote:
> > >
> > > If there is already a patch 6588, then would you mind to include
> > > it for Stretch?
> > >
> > >
> > > Before this is considered, we need confirmation it fixes the issue. Could
> > > you try that patch?
> > >
> >
> > I applied 9cbc4547702aac28466c497f720038b9e2dc510c to 232-25+deb9u1:
> > No luck. It still gets stuck at shutdown time for about 3 minutes.
> >
> > Attached you can find 2 screenshots I managed to take. The list-open.service
> > was in place. Please note the "nfs-data not responding" due to the lost
> > network connection. "nfs-data" is a CNAME for the NFServer for both
> > /home and /data.
> >
> > Maybe its an option to not shutdown the network at all?
>
> That's up to the network config system.
>
> NetworkManager e.g. does not shut down ethernet connections when being
> stoppend.
This doesn't look like a systemd problem, but more like a problem of the
network config system shutting down the network too early during
shutdown. If this is still an issue on an up-to-date stretch or buster
system, please file a bug report against the network configuration tool
you are using.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
