[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#41791: [Shepherd] loses track of Tor
From: |
Ludovic Courtès |
Subject: |
bug#41791: [Shepherd] loses track of Tor |
Date: |
Fri, 12 Jun 2020 00:11:53 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (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
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’.