GNU bug report logs - #41791
[Shepherd] loses track of Tor

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 41791 in the body.
You can then email your comments to 41791 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: bug-guix <at> gnu.org
Subject: [Shepherd] loses track of Tor
Date: Wed, 10 Jun 2020 17:20:01 +0200

[Message part 1 (text/plain, inline)]

All,

--8<---------------cut here---------------start------------->8---
~ λ while :; do sudo herd restart tor; done
Service tor is not running.
Service tor has been started.
Service tor has been stopped.
Service tor could not be started.
Service tor is not running.
Service tor could not be started.
^C
~ λ pgrep tor
22926
23004
--8<---------------cut here---------------end--------------->8---

This has (this year) happened to nginx in tight edit.conf/restart 
loops too, but I can't say if the two are at all related.

Here's the output of ‘herd status’ but it's not very useful to me:

--8<---------------cut here---------------start------------->8---
λ sudo herd status
Started:
+ dovecot
+ file-system-/dev/pts
+ file-system-/dev/shm
+ file-system-/gnu/store
+ file-systems
+ guix-daemon
+ loopback
+ mcron
+ networking
+ nginx
+ root
+ root-file-system
+ smtpd
+ ssh-daemon
+ syslogd
+ term-tty1
+ udev
+ urandom-seed
+ user-file-systems
+ user-processes
+ virtual-terminal
Stopped:
- tor
One-shot:
* host-name
* user-homes
--8<---------------cut here---------------end--------------->8---

He looks guilty:

--8<---------------cut here---------------start------------->8---
λ sudo cat /var/run/tor/tor.pid
cat: /var/run/tor/tor.pid: No such file or directory
--8<---------------cut here---------------end--------------->8---

From ps auxwww:

--8<---------------cut here---------------start------------->8---
~ λ head -n6 /gnu/store/5ivhkbd0pzhnnmk38yn7cygcyd02kkk5-torrc
### These lines were generated from your system configuration:
User tor
DataDirectory /var/lib/tor
PidFile /var/run/tor/tor.pid
Log notice syslog
### End of automatically generated lines.
--8<---------------cut here---------------end--------------->8---

No contradictory lines added.

Kind regards,

T G-R

[signature.asc (application/pgp-signature, inline)]

Message #12 received at 41791-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Tobias Geerinckx-Rice <me <at> tobias.gr>
Cc: 41791-done <at> debbugs.gnu.org
Subject: Re: bug#41791: [Shepherd] loses track of Tor
Date: Fri, 12 Jun 2020 00:11:53 +0200

Hi Tobias,

Tobias Geerinckx-Rice <me <at> tobias.gr> skribis:

> ~ λ while :; do sudo herd restart tor; done
> Service tor is not running.
> Service tor has been started.
> Service tor has been stopped.
> Service tor could not be started.
> Service tor is not running.
> Service tor could not be started.
> ^C
> ~ λ pgrep tor
> 22926
> 23004

Oops, this one is fixed by b6b95685d0b478698d648f13afd927b1e1700d99.
It’s a regression introduced when switching to the Shepherd 0.8.1.

> This has (this year) happened to nginx in tight edit.conf/restart 
> loops too, but I can't say if the two are at all related.

The nginx issue may be different.  The Shepherd 0.8.0 included fixes
that should help for multi-process services like nginx.  Let me know if
it happens again.

Thanks for reporting the issue… and apologies for grumpily pushing you
to do so on IRC.  It’s a positive outcome at any rate!

Ludo’.

Message #15 received at 41791-done <at> debbugs.gnu.org (full text, mbox):

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 41791-done <at> debbugs.gnu.org
Subject: Re: bug#41791: [Shepherd] loses track of Tor
Date: Fri, 12 Jun 2020 14:03:29 +0200

[Message part 1 (text/plain, inline)]

Ludovic Courtès 写道：
> Oops, this one is fixed by 
> b6b95685d0b478698d648f13afd927b1e1700d99.

Impressive fanservice as always.

> The nginx issue may be different.  The Shepherd 0.8.0 included 
> fixes
> that should help for multi-process services like nginx.  Let me 
> know if
> it happens again.

I will.  It's possible that it hasn't happened since 0.8.0.

> Thanks for reporting the issue… and apologies for grumpily 
> pushing you
> to do so on IRC.  It’s a positive outcome at any rate!

The day I get to berate anyone for being grumpy will be a strange 
day in hell.

Thanks!

T G-R

[signature.asc (application/pgp-signature, inline)]

Message #24 received at 41791 <at> debbugs.gnu.org (full text, mbox):

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: 41791 <at> debbugs.gnu.org
Cc: Caleb Herbert <csh <at> bluehome.net>,
 Wiktor Żelazny <wz <at> freeshell.de>,
 Ludovic Courtès <ludo <at> gnu.org>
Subject: [Shepherd] loses track of Tor
Date: Sun, 28 Nov 2021 13:39:11 +0100

[Message part 1 (text/plain, inline)]

All,

Unfortunately, this bug seems to have recropped up: 
<https://lists.gnu.org/archive/html/help-guix/2021-11/msg00126.html>.

Kind regards,

T G-R

[signature.asc (application/pgp-signature, inline)]

Message #27 received at 41791 <at> debbugs.gnu.org (full text, mbox):

From: Attila Lendvai <attila <at> lendvai.name>
To: "41791 <at> debbugs.gnu.org" <41791 <at> debbugs.gnu.org>
Subject: Re: [Shepherd] loses track of Tor
Date: Mon, 28 Feb 2022 19:09:22 +0000

i'm not sure this is related, but it's certainly a bug in MAKE-KILL-DESTRUCTOR
that it doesn't wait for the process to quit after sending it a signal, and thus
may restart the service while the previous instance is still running.

it's also not sending it a kill -9 after a timeout if the process is not
responsive.

--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“[Design] Patterns mean "I have run out of language."”
	— Rich Hickey

Message #32 received at 41791-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Tobias Geerinckx-Rice <me <at> tobias.gr>
Cc: 41791-done <at> debbugs.gnu.org
Subject: Re: bug#41791: [Shepherd] loses track of Tor
Date: Thu, 12 Jan 2023 15:14:02 +0100

Hi Tobias,

Tobias Geerinckx-Rice <me <at> tobias.gr> skribis:

> ~ λ while :; do sudo herd restart tor; done
> Service tor is not running.
> Service tor has been started.
> Service tor has been stopped.
> Service tor could not be started.
> Service tor is not running.
> Service tor could not be started.
> ^C
> ~ λ pgrep tor
> 22926
> 23004

I don’t see that happening with the Shepherd 0.9.3.  I believe this was
fixed by making ‘stop’ synchronous:

  https://issues.guix.gnu.org/58485

Closing!

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.