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

Previous Next

Package: guix;

Reported by: Noah Landis <noahlandis <at> posteo.net>

Date: Mon, 19 Apr 2021 19:18:01 UTC

Severity: normal

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


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

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’.




This bug report was last modified 2 years and 98 days ago.

Previous Next


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