Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #242003 > unrolled thread

Service stuck at shutdow

Back to article view | Back to linux.debian.user

Contents

  Service stuck at shutdow Erwan David <erwan@rail.eu.org> - 2021-11-10 18:40 +0100
    Re: Service stuck at shutdow Charles Curley <charlescurley@charlescurley.com> - 2021-11-10 19:50 +0100
    Re: Service stuck at shutdow Tixy <tixy@yxit.co.uk> - 2021-11-10 20:10 +0100
      Re: Service stuck at shutdow Erwan David <erwan@rail.eu.org> - 2021-11-10 22:20 +0100
        Re: Service stuck at shutdow Charles Curley <charlescurley@charlescurley.com> - 2021-11-10 23:30 +0100
        Re: Service stuck at shutdown David Wright <deblis@lionunicorn.co.uk> - 2021-11-11 06:20 +0100
          Re: Service stuck at shutdown Erwan David <erwan@rail.eu.org> - 2021-11-11 18:00 +0100
            Re: Service stuck at shutdown Erwan David <erwan@rail.eu.org> - 2021-11-12 09:40 +0100

#242003 — Service stuck at shutdow

Since some time, I always have to wait 1 min 30 at shut down because 
some service does not stop (for user erwan is said).

How can I debug this, know which service is blocking the shutdown ?

[toc] | [next] | [standalone]

#242004

On Wed, 10 Nov 2021 18:33:10 +0100
Erwan David <erwan@rail.eu.org> wrote:

> Since some time, I always have to wait 1 min 30 at shut down because 
> some service does not stop (for user erwan is said).
> 
> How can I debug this, know which service is blocking the shutdown ?

1) Check your logs, especially /var/log/syslog.

2) Make the boot and shutdown process more verbose, and watch the
   shutdown process. As root, in the file /etc/default/grub, find the
   line that sets GRUB_CMDLINE_LINUX_DEFAULT, and take out the word
   "quiet". Then run update-grub, and reboot. You should see a lot more
   messages. Then shut down again, and watch. N.B.: A mistake here
   could clobber your system badly, so be careful.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#242005

On Wed, 2021-11-10 at 18:33 +0100, Erwan David wrote:
> Since some time, I always have to wait 1 min 30 at shut down because 
> some service does not stop (for user erwan is said).
> 
> How can I debug this, know which service is blocking the shutdown ?

Assuming you system is using systemd then look at the logs for the last
boot with:

#journalctl -b-1

and scroll to the end where you will see what was going on during
shutdown. Errors will likely be highlighted in red (they are for me).

The times I've had hanging during shutdown is due to the network being
shut down before network filesystems are unmounted.

-- 
Tixy

[toc] | [prev] | [next] | [standalone]

#242007

Le 10/11/2021 à 20:01, Tixy a écrit :
> On Wed, 2021-11-10 at 18:33 +0100, Erwan David wrote:
>> Since some time, I always have to wait 1 min 30 at shut down because
>> some service does not stop (for user erwan is said).
>>
>> How can I debug this, know which service is blocking the shutdown ?
> Assuming you system is using systemd then look at the logs for the last
> boot with:
>
> #journalctl -b-1
>
> and scroll to the end where you will see what was going on during
> shutdown. Errors will likely be highlighted in red (they are for me).
>
> The times I've had hanging during shutdown is due to the network being
> shut down before network filesystems are unmounted.
>
Thanks, for me the culprint is 'dconf worker' (I see it being killed 
with a 'timeout error') about 90s after preceding message.

I do not know where it comes from, I have dconf-service installed as a 
dependency of many things, thus it is not removable. However I do not 
find any messages about dconf, and what does not work correctly.

SO now the question is what the fuck is dconf doing, and how to correct 
it (and no I have no idea of how dconf works, and even what problem it 
is intended to solve.

[toc] | [prev] | [next] | [standalone]

#242009

On Wed, 10 Nov 2021 22:18:07 +0100
Erwan David <erwan@rail.eu.org> wrote:

> Thanks, for me the culprint is 'dconf worker' (I see it being killed 
> with a 'timeout error') about 90s after preceding message.
> 
> I do not know where it comes from, I have dconf-service installed as
> a dependency of many things, thus it is not removable. However I do
> not find any messages about dconf, and what does not work correctly.
> 
> SO now the question is what the fuck is dconf doing, and how to
> correct it (and no I have no idea of how dconf works, and even what
> problem it is intended to solve.

Well, there are plenty of resources for finding out what something
does. "man dconf" is a bust. More fruitful:

charles@hawk:~/versioned$ apt-cache search dconf
dconf-cli - simple configuration storage system - utilities
dconf-gsettings-backend - simple configuration storage system - GSettings back-end
dconf-service - simple configuration storage system - D-Bus service
libdconf-dev - simple configuration storage system - development files
libdconf-doc - simple configuration storage system - documentation
libdconf1 - simple configuration storage system - runtime library
dconf-editor - simple configuration storage system - graphical editor
libzadc4 - accelerated libz implementation (Accelerated Data Compression/ADC)
libc-bin - GNU C Library: Binaries
libmed-tools - Runtime tools to handle MED files
pg-cloudconfig - Set optimized defaults for PostgreSQL in virtual environments
charles@hawk:~/versioned$ apt-cache show dconf-service
Package: dconf-service
Source: dconf
Version: 0.38.0-2
Installed-Size: 110
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Architecture: amd64
Depends: default-dbus-session-bus | dbus-session-bus, libdconf1 (= 0.38.0-2), libc6 (>= 2.28), libglib2.0-0 (>= 2.55.2)
Recommends: dconf-gsettings-backend
Description-en: simple configuration storage system - D-Bus service
 DConf is a low-level key/value database designed for storing desktop
 environment settings.
 .
 This package contains the DConf service, which applications talk to
 using D-Bus in order to obtain their settings. It is mostly used by the
 GSettings backend.
Description-md5: 8339e79de2cc17111e9f391efbb6d79f
Multi-Arch: foreign
Homepage: https://wiki.gnome.org/Projects/dconf
Tag: role::shared-lib
Section: libs
Priority: optional
Filename: pool/main/d/dconf/dconf-service_0.38.0-2_amd64.deb
Size: 37368
MD5sum: ae01132eaebbe3db11bb8800822d8f55
SHA256: 639125f7a44d11f96661c61a07abbb58da0e5636ed406ac186adcef8651775c2

charles@hawk:~/versioned$ 

Buried in all that output is the web site,
https://wiki.gnome.org/Projects/dconf, which you can now look at to see
what it does.


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#242011 — Re: Service stuck at shutdown

On Wed 10 Nov 2021 at 22:18:07 (+0100), Erwan David wrote:
> Le 10/11/2021 à 20:01, Tixy a écrit :
> > On Wed, 2021-11-10 at 18:33 +0100, Erwan David wrote:
> > > Since some time, I always have to wait 1 min 30 at shut down because
> > > some service does not stop (for user erwan is said).
> > > 
> > > How can I debug this, know which service is blocking the shutdown ?
> > Assuming you system is using systemd then look at the logs for the last
> > boot with:
> > 
> > #journalctl -b-1
> > 
> > and scroll to the end where you will see what was going on during
> > shutdown. Errors will likely be highlighted in red (they are for me).
> > 
> > The times I've had hanging during shutdown is due to the network being
> > shut down before network filesystems are unmounted.
> > 
> Thanks, for me the culprint is 'dconf worker' (I see it being killed
> with a 'timeout error') about 90s after preceding message.
> 
> I do not know where it comes from, I have dconf-service installed as a
> dependency of many things, thus it is not removable. However I do not
> find any messages about dconf, and what does not work correctly.
> 
> SO now the question is wtf is dconf doing, and how to
> correct it (and no I have no idea of how dconf works, and even what
> problem it is intended to solve.

A workaround that might shorten the wait, but only if you're confident
that there aren't processes that need that long to complete, is to edit
the line   DefaultTimeoutStopSec=90s   in /etc/systemd/system.conf to
something smaller.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#242021 — Re: Service stuck at shutdown

Le 11/11/2021 à 06:16, David Wright a écrit :
> On Wed 10 Nov 2021 at 22:18:07 (+0100), Erwan David wrote:
>> Le 10/11/2021 à 20:01, Tixy a écrit :
>>> On Wed, 2021-11-10 at 18:33 +0100, Erwan David wrote:
>>>> Since some time, I always have to wait 1 min 30 at shut down because
>>>> some service does not stop (for user erwan is said).
>>>>
>>>> How can I debug this, know which service is blocking the shutdown ?
>>> Assuming you system is using systemd then look at the logs for the last
>>> boot with:
>>>
>>> #journalctl -b-1
>>>
>>> and scroll to the end where you will see what was going on during
>>> shutdown. Errors will likely be highlighted in red (they are for me).
>>>
>>> The times I've had hanging during shutdown is due to the network being
>>> shut down before network filesystems are unmounted.
>>>
>> Thanks, for me the culprint is 'dconf worker' (I see it being killed
>> with a 'timeout error') about 90s after preceding message.
>>
>> I do not know where it comes from, I have dconf-service installed as a
>> dependency of many things, thus it is not removable. However I do not
>> find any messages about dconf, and what does not work correctly.
>>
>> SO now the question is wtf is dconf doing, and how to
>> correct it (and no I have no idea of how dconf works, and even what
>> problem it is intended to solve.
> A workaround that might shorten the wait, but only if you're confident
> that there aren't processes that need that long to complete, is to edit
> the line   DefaultTimeoutStopSec=90s   in /etc/systemd/system.conf to
> something smaller.
>
> Cheers,
> David.
>
>

I do not know : I was not even aware that kde was using dconf.

 From what I could see, it seems that kded5 starts dconf-service at end 
of session, I presume to save some settings (but which one s ?) and 
something fails

would it help to remove the ~/.config/dconf/user file when kde is not 
running ? The /etc/dconf/db directory is empty.

I do not understand what dconf-editor shows me.


SHould I file a bug report to dconf-service or kded5 ?

[toc] | [prev] | [next] | [standalone]

#242048 — Re: Service stuck at shutdown

Le 11/11/2021 à 17:55, Erwan David a écrit :
> Le 11/11/2021 à 06:16, David Wright a écrit :
>> A workaround that might shorten the wait, but only if you're confident
>> that there aren't processes that need that long to complete, is to edit
>> the line   DefaultTimeoutStopSec=90s   in /etc/systemd/system.conf to
>> something smaller.
>>
>> Cheers,
>> David.
>>
>>
>
> I do not know : I was not even aware that kde was using dconf.
>
> From what I could see, it seems that kded5 starts dconf-service at end 
> of session, I presume to save some settings (but which one s ?) and 
> something fails
>
> would it help to remove the ~/.config/dconf/user file when kde is not 
> running ? The /etc/dconf/db directory is empty.
>
> I do not understand what dconf-editor shows me.
>
>
> Sould I file a bug report to dconf-service or kded5 ?
>
>

I tried removung the file, works once, but nort more. since 
deconf-service(1) says it is crash proof I added an override to 
dconf.service unit :

TimeoutStopFailureMode=kill
TimeoutStopSec=10s

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web