emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#41791: closed ([Shepherd] loses track of Tor)


From: GNU bug Tracking System
Subject: bug#41791: closed ([Shepherd] loses track of Tor)
Date: Thu, 12 Jan 2023 14:15:01 +0000

Your message dated Thu, 12 Jan 2023 15:14:02 +0100
with message-id <87k01rhmc5.fsf@gnu.org>
and subject line Re: bug#41791: [Shepherd] loses track of Tor
has caused the debbugs.gnu.org bug report #41791,
regarding [Shepherd] loses track of Tor
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
41791: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=41791
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [Shepherd] loses track of Tor Date: Wed, 10 Jun 2020 17:20:01 +0200
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

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Re: bug#41791: [Shepherd] loses track of Tor Date: Thu, 12 Jan 2023 15:14:02 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
Hi Tobias,

Tobias Geerinckx-Rice <me@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’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]