From: "Wiktor Żelazny" <wz@freeshell.de>
To: Caleb Herbert <csh@bluehome.net>
Cc: help-guix@gnu.org
Subject: Re: shepherd: Service tor could not be started.
Date: Sun, 28 Nov 2021 12:37:41 +0100 [thread overview]
Message-ID: <20211128113741.lq6r2kprjdmd7l4d@wzguix> (raw)
In-Reply-To: <3f3dfaef-32dd-1873-3b7a-bd8ab857f7b6@bluehome.net>
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
On Fri, Nov 26, 2021 at 07:16:23PM -0600, Caleb Herbert wrote:
> To complete the upgrade, run 'herd restart SERVICE' to stop,
> upgrade, and restart each service that was not automatically restarted.
> Run 'herd status' to view the list of services on your system.
> root@bender ~# herd restart tor
> Service tor is not running.
> Service tor could not be started.
Hi Celeb,
To my understanding for some reason one cannot stop a tor service using
GNU Shepherd. When I need to restart, I kill the tor process using `kill
<PID>`, and only then run `herd restart tor`.
> * Running Tor manually
> Nov 26 19:01:57.107 [warn] Could not bind to 127.0.0.1:9050: Address
> already in use. Is Tor already running?
Apparently, tor is running. It tends to happen to me after reconnecting
to the Internet that I cannot use tor, anymore, although the process is
still running. I need to perform the above procedure to make it usable
again.
Not sure if that addresses your problem, but you can try this poor-man’s
method.
WŻ
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2021-11-28 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 1:16 shepherd: Service tor could not be started Caleb Herbert
2021-11-28 11:37 ` Wiktor Żelazny [this message]
2021-11-29 22:16 ` Caleb Herbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211128113741.lq6r2kprjdmd7l4d@wzguix \
--to=wz@freeshell.de \
--cc=csh@bluehome.net \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).