Re: a stop job is running for user manager

David Wright writes: > On Fri 18 Feb 2022 at 21:13:16 (+), Richmond wrote: >> Махно writes: >> > 2022-02-18, pn, 03:28 David Wright rašė: >> >> On Thu 17 Feb 2022 at 13:44:46 (+), Richmond wrote: >> >> > David Wright writes: >> >> > > On Thu 17 Feb 2022 at 01:00:30 (+), Richmond

Re: a stop job is running for user manager

On Fri 18 Feb 2022 at 21:13:16 (+), Richmond wrote: > Махно writes: > > 2022-02-18, pn, 03:28 David Wright rašė: > >> On Thu 17 Feb 2022 at 13:44:46 (+), Richmond wrote: > >> > David Wright writes: > >> > > On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: > >> > >> Since upgrading

Re: a stop job is running for user manager

Махно writes: > Hello! I would suggest that you report this issue to Debian BTS by > using the reportbug program. Also, i think you should wait for a > person, responsible for the maintenance of this package and wait for > an answer. Perhaps. Yesterday I found a site that suggested removing

Re: a stop job is running for user manager

Hello! I would suggest that you report this issue to Debian BTS by using the reportbug program. Also, i think you should wait for a person, responsible for the maintenance of this package and wait for an answer. 2022-02-18, pn, 03:28 David Wright rašė: > > On Thu 17 Feb 2022 at 13:44:46 (+),

Re: a stop job is running for user manager

On Thu 17 Feb 2022 at 13:44:46 (+), Richmond wrote: > David Wright writes: > > On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: > >> Since upgrading to Debian 11 I sometimes see "a stop job is running for > >> user manager..." on shutdown and it waits 90 seconds. The last comment > >>

Re: a stop job is running for user manager

David Wright writes: > On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: >> Since upgrading to Debian 11 I sometimes see "a stop job is running for >> user manager..." on shutdown and it waits 90 seconds. The last comment >> in this thread says "Installing systemd from backsports solved

Re: a stop job is running for user manager

David Wright writes: > On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: >> Since upgrading to Debian 11 I sometimes see "a stop job is running for >> user manager..." on shutdown and it waits 90 seconds. The last comment >> in this thread says "Installing systemd from backsports solved

Re: a stop job is running for user manager

On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: > Since upgrading to Debian 11 I sometimes see "a stop job is running for > user manager..." on shutdown and it waits 90 seconds. The last comment > in this thread says "Installing systemd from backsports solved this issue." > >

Re: A stop job is running for...

On 12/05/2015 01:21 AM, Himanshu Shekhar wrote: Well, Google shall help! The two articles seem much technical for a kid like me. Still, the content made me feel that there shall be something convincing, which is why I posted it on this mail. 1.

Re: A stop job is running for...

On Wed 02 Dec 2015 at 18:17:18 (+0100), Michael Biebl wrote: > Am 02.12.2015 um 18:05 schrieb Jape Person: > > On 12/02/2015 10:49 AM, David Wright wrote: > >> I have observed behaviour where, when the time limit of 90 seconds is > >> reached, the limit increases by another 90 seconds and nothing

Systemd debugging (was ... Re: A stop job is running for...)

On Thu, Dec 03, 2015 at 10:07:01PM +0100, Michael Biebl wrote: > Two issues that come to mind here: > a/ cups-browsed.service declares a dependency on avahi-daemon.service. > So it should be stopped before avahi-daemon. But apparently you don't > have any avahi-daemon process anymore. > Would be

Re: A stop job is running for...

Well, Google shall help! The two articles seem much technical for a kid like me. Still, the content made me feel that there shall be something convincing, which is why I posted it on this mail. 1. https://lists.fedoraproject.org/pipermail/users/2014-February/446722.html # for NTP 2.

Re: A stop job is running for...

On Thu, 03 Dec 2015, David Wright wrote: > Which data do you mean? For example, a database server[1] which has a transaction outstanding or needs a long time to write to disk for an orderly shutdown. > By the time these Stop jobs start running, there are just system > processes running. I don't

Re: A stop job is running for...

HTTP; Thu, 3 Dec 2015 02:17:13 -0800 (PST) Received: by 10.202.67.66 with HTTP; Thu, 3 Dec 2015 02:17:13 -0800 (PST) In-Reply-To: <565d0045.4040...@comcast.net> References: <565d0045.4040...@comcast.net> Date: Thu, 3 Dec 2015 15:47:13 +0530 Message-ID: Subject: Re: A stop job is running

Re: A stop job is running for...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 03, 2015 at 05:50:09AM -0500, Gene Heskett wrote: > On Thursday 03 December 2015 02:41:57 Nicolas George wrote: [...] > > Libre Software development is a meritocracy, not a democracy [...] Hm. Somehow I feel that while true, this is

Re: A stop job is running for...

On Thursday 03 December 2015 02:41:57 Nicolas George wrote: > Le duodi 12 frimaire, an CCXXIV, Gene Heskett a écrit : > >But it bugs the heck out of me that the guy/gal > > doing the codeing doesn't watch the user lists, so it all has to > > wait on someone qualified enough to

Re: A stop job is running for...

On 12/03/2015 05:22 AM, Himanshu Shekhar wrote: The complete message is really important. Perhaps, I would investigate. Hello! I did give the complete messages. Both start with A stop job is running for... The endings are Make remote CUPS printers available locally and Network Time

Re: A stop job is running for...

On Wed 02 Dec 2015 at 16:59:23 (-0600), Don Armstrong wrote: > On Wed, 02 Dec 2015, Jape Person wrote: > > It's occurred to me that, though I have occasionally seen service > > shutown issues with sysv-init, they were never as pervasive or > > repetitve as it has been since switching to systemd as

Re: A stop job is running for...

On 12/03/2015 01:00 PM, Michael Biebl wrote: Am 03.12.2015 um 18:18 schrieb Jape Person: A stop job is running for... The endings are Make remote CUPS printers available locally and Network Time Synchronization I've checked for CUPS and NTP errors in the logs and have found nothing. I

Re: A stop job is running for...

Am 03.12.2015 um 21:21 schrieb Jape Person: > /usr/sbin/cupsd -l > root 715 0.0 0.1 250812 8680 ?Ssl 11:37 0:00 > /usr/sbin/cups-browsed > lp 993 0.0 0.0 78772 5584 ?S11:38 0:00 > /usr/lib/cups/notifier/dbus dbus:// > root 1114 0.0 0.0 43828

Re: A stop job is running for...

On 12/03/2015 01:23 PM, Rick Thomas wrote: Hi JP On Dec 3, 2015, at 9:18 AM, Jape Person wrote: On 12/03/2015 05:22 AM, Himanshu Shekhar wrote: The complete message is really important. Perhaps, I would investigate. Hello! I did give the complete messages. Both start

Re: A stop job is running for...

Am 03.12.2015 um 18:18 schrieb Jape Person: > A stop job is running for... > > The endings are > > Make remote CUPS printers available locally > > and > > Network Time Synchronization > > I've checked for CUPS and NTP errors in the logs and have found nothing. > I presume that's because this

Re: A stop job is running for...

Hi JP On Dec 3, 2015, at 9:18 AM, Jape Person wrote: > On 12/03/2015 05:22 AM, Himanshu Shekhar wrote: >> The complete message is really important. Perhaps, I >> would investigate. > > Hello! > > I did give the complete messages. Both start with > > A stop job is running

Re: A stop job is running for...

On 12/02/2015 06:06 AM, Martin Read wrote: On 02/12/15 03:07, James P. Wallen wrote: Thanks for your response, Sven. It's nice to know that someone else has seen this type of problem. I was thinking that this could be self-inflicted. Perhaps that's a little less likely now. So, is this

Re: A stop job is running for...

On Wed 02 Dec 2015 at 11:06:09 (+), Martin Read wrote: > On 02/12/15 03:07, James P. Wallen wrote: > >Thanks for your response, Sven. It's nice to know that someone else has > >seen this type of problem. I was thinking that this could be > >self-inflicted. Perhaps that's a little less likely

Re: A stop job is running for...

On 12/02/2015 06:06 AM, Martin Read wrote: The default and per-service timeout values for stopping a service (after which systemd gives up and sends fatal signals to all of the service's processes) are configurable; see the systemd-system.conf(5) and systemd.service(5) man pages for details.

Re: A stop job is running for...

On Wednesday 02 December 2015 06:06:09 Martin Read wrote: > On 02/12/15 03:07, James P. Wallen wrote: > > Thanks for your response, Sven. It's nice to know that someone else > > has seen this type of problem. I was thinking that this could be > > self-inflicted. Perhaps that's a little less

Re: A stop job is running for...

On 12/02/2015 10:49 AM, David Wright wrote: On Wed 02 Dec 2015 at 11:06:09 (+), Martin Read wrote: On 02/12/15 03:07, James P. Wallen wrote: Thanks for your response, Sven. It's nice to know that someone else has seen this type of problem. I was thinking that this could be self-inflicted.

Re: A stop job is running for...

On 12/02/2015 12:17 PM, Michael Biebl wrote: Am 02.12.2015 um 18:05 schrieb Jape Person: On 12/02/2015 10:49 AM, David Wright wrote: I have observed behaviour where, when the time limit of 90 seconds is reached, the limit increases by another 90 seconds and nothing else happens (for hours). eg

Re: A stop job is running for...

Am 02.12.2015 um 18:05 schrieb Jape Person: > On 12/02/2015 10:49 AM, David Wright wrote: >> I have observed behaviour where, when the time limit of 90 seconds is >> reached, the limit increases by another 90 seconds and nothing else >> happens (for hours). eg >> >> [ <*> ] A stop job is running

Re: A stop job is running for...

On 12/02/2015 01:21 PM, Gene Heskett wrote: On Wednesday 02 December 2015 06:06:09 Martin Read wrote: On 02/12/15 03:07, James P. Wallen wrote: Thanks for your response, Sven. It's nice to know that someone else has seen this type of problem. I was thinking that this could be self-inflicted.

Re: A stop job is running for...

Am 02.12.2015 um 18:58 schrieb Jape Person: > On 12/02/2015 12:17 PM, Michael Biebl wrote: >> In case you run into such a situation again, where a service is blocking >> the shutdown you can of course just use force and pull the plug or use >> sysrq b. >> But there is a nicer alternative: just hit

Re: A stop job is running for...

On 12/02/2015 02:04 PM, Michael Biebl wrote: Am 02.12.2015 um 18:58 schrieb Jape Person: On 12/02/2015 12:17 PM, Michael Biebl wrote: In case you run into such a situation again, where a service is blocking the shutdown you can of course just use force and pull the plug or use sysrq b. But

Re: A stop job is running for...

On Wed, 02 Dec 2015, Jape Person wrote: > It's occurred to me that, though I have occasionally seen service > shutown issues with sysv-init, they were never as pervasive or > repetitve as it has been since switching to systemd as the init > system. This is generally because sysv-init tends to not

Re: A stop job is running for...

On Wednesday 02 December 2015 14:02:50 Jape Person wrote: > On 12/02/2015 01:21 PM, Gene Heskett wrote: > > On Wednesday 02 December 2015 06:06:09 Martin Read wrote: > >> On 02/12/15 03:07, James P. Wallen wrote: > >>> Thanks for your response, Sven. It's nice to know that someone > >>> else has

Re: A stop job is running for...

On Thu, 3 Dec 2015 15:48:07 +1300 Chris Bannister wrote: > On Wed, Dec 02, 2015 at 08:12:24PM -0500, Gene Heskett wrote: > > > > In the meantime, its hit another 200 users, discouraging them from ever > > touching linux again. In that regard, we are our own worst

Re: A stop job is running for...

On Wednesday 02 December 2015 21:48:07 Chris Bannister wrote: > On Wed, Dec 02, 2015 at 08:12:24PM -0500, Gene Heskett wrote: > > In the meantime, its hit another 200 users, discouraging them from > > ever touching linux again. In that regard, we are our own worst > > enemy at times.

Re: A stop job is running for...

On Wednesday 02 December 2015 22:05:10 Neal P. Murphy wrote: > On Thu, 3 Dec 2015 15:48:07 +1300 > > Chris Bannister wrote: > > On Wed, Dec 02, 2015 at 08:12:24PM -0500, Gene Heskett wrote: > > > In the meantime, its hit another 200 users, discouraging them from > > >

Re: A stop job is running for...

Le duodi 12 frimaire, an CCXXIV, Gene Heskett a écrit : > But it bugs the heck out of me that the guy/gal > doing the codeing doesn't watch the user lists, so it all has to wait on > someone qualified enough to wade thru the bug reporter forms and > actually file the bug.

Re: A stop job is running for...

On Wed, Dec 02, 2015 at 08:12:24PM -0500, Gene Heskett wrote: > > In the meantime, its hit another 200 users, discouraging them from ever > touching linux again. In that regard, we are our own worst enemy at > times. Unfortunately, the oar I steer this ship with could be swapped > for a

Re: A stop job is running for...

On 12/02/2015 05:59 PM, Don Armstrong wrote: On Wed, 02 Dec 2015, Jape Person wrote: It's occurred to me that, though I have occasionally seen service shutown issues with sysv-init, they were never as pervasive or repetitve as it has been since switching to systemd as the init system. This is

Re: A stop job is running for...

On 02/12/15 03:07, James P. Wallen wrote: Thanks for your response, Sven. It's nice to know that someone else has seen this type of problem. I was thinking that this could be self-inflicted. Perhaps that's a little less likely now. So, is this behavior controlled by systemd? I'm not trying to

Re: A stop job is running for...

On 12/01/2015 09:47 AM, Sven Arvidsson wrote: On Mon, 2015-11-30 at 21:04 -0500, Jape Person wrote: Make remote CUPS printers available locally Network Time Synchronization For several weeks I've been seeing this stop job notification for these two items frequently when rebooting or shutting

Re: A stop job is running for...

On Mon, 2015-11-30 at 21:04 -0500, Jape Person wrote: > Make remote CUPS printers available locally > Network Time Synchronization > > For several weeks I've been seeing this stop job notification for > these > two items frequently when rebooting or shutting down two of my four > testing