GNU bug report logs - #47899
Shepherd Loses Track of Tor Service

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#47899: closed (Shepherd Loses Track of Tor Service)
Date: Sat, 18 Feb 2023 14:07:02 +0000

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

Your message dated Sat, 18 Feb 2023 15:06:03 +0100
with message-id <87r0unhxv8.fsf <at> gnu.org>
and subject line Re: bug#47899: Shepherd Loses Track of Tor Service
has caused the debbugs.gnu.org bug report #47899,
regarding Shepherd Loses Track of Tor Service
to be marked as done.

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


-- 
47899: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=47899
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Noah Landis <noahlandis <at> posteo.net>
To: bug-guix <at> gnu.org
Subject: Shepherd Loses Track of Tor Service
Date: Mon, 19 Apr 2021 19:16:55 +0000

I was trying to replicate my system on another machine and when I
finished I realised I could not restart tor. After that I was frustrated
and did a fresh install and after running 'guix pull' and 'sudo guix
system reconfigure /etc/config.scm' tor could still not be
started. I went on the irc and nckx told me to run 'pgrep tor' which
returned a number. After running 'sudo kill that-number' and 'sudo herd
enable tor && sudo herd restart tor', the tor service could be
started. I then rebooted and it once again could not be started, yet
'prgep tor' returned a number.

Thanks!

-- 
Noah Landis  <noahlandis <at> posteo.net>
GPG key = 3D5E 7A7A 0DF1 B4D8 669C F3EE 30B8 3188 A3AF F882
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[Message part 3 (message/rfc822, inline)]

From: Ludovic Courtès <ludo <at> gnu.org>
To: Noah Landis <noahlandis <at> posteo.net>
Cc: 47899-done <at> debbugs.gnu.org
Subject: Re: bug#47899: Shepherd Loses Track of Tor Service
Date: Sat, 18 Feb 2023 15:06:03 +0100

Hi Noah,

Noah Landis <noahlandis <at> posteo.net> skribis:

> I was trying to replicate my system on another machine and when I
> finished I realised I could not restart tor. After that I was frustrated
> and did a fresh install and after running 'guix pull' and 'sudo guix
> system reconfigure /etc/config.scm' tor could still not be
> started. I went on the irc and nckx told me to run 'pgrep tor' which
> returned a number. After running 'sudo kill that-number' and 'sudo herd
> enable tor && sudo herd restart tor', the tor service could be
> started. I then rebooted and it once again could not be started, yet
> 'prgep tor' returned a number.

Apologies for the late reply.  Version 0.9.3 of the Shepherd, released a
few months ago, fixed things in this area, and it’s likely that the bug
is gone now.

I’m closing this issue but please do reopen it if you notice something
fishy!

Thanks,
Ludo’.

Previous Next

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