Problem when hosting a middle/guard: Trouble when restarting Tor daemon

kaiod · March 24, 2023, 12:43pm

Hey, I would like to get support for the following problem. I am hosting a relay, and I had the following problem when restarting the deamon.

● tor@default.service - Anonymizing overlay network for TCP
   Loaded: loaded (/lib/systemd/system/tor@default.service; static; vendor preset: enabled)
   Active: failed (Result: start-limit-hit) since Fri 2023-03-24 09:29:10 -03; 4s ago
  Process: 92910 ExecStart=/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 (code=exited, status=1/FAILURE)
  Process: 92906 ExecStartPre=/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 --verify-config (code=exited, st
  Process: 92903 ExecStartPre=/usr/bin/install -Z -m 02755 -o debian-tor -g debian-tor -d /var/run/tor (code=exited, status=0/SUCCESS)
 Main PID: 92910 (code=exited, status=1/FAILURE)

Mar 24 09:29:10 server systemd[1]: tor@default.service: Main process exited, code=exited, status=1/FAILURE
Mar 24 09:29:10 server systemd[1]: Failed to start Anonymizing overlay network for TCP.
Mar 24 09:29:10 server systemd[1]: tor@default.service: Unit entered failed state.
Mar 24 09:29:10 server systemd[1]: tor@default.service: Failed with result 'exit-code'.
Mar 24 09:29:10 server systemd[1]: tor@default.service: Service hold-off time over, scheduling restart.
Mar 24 09:29:10 server systemd[1]: Stopped Anonymizing overlay network for TCP.
Mar 24 09:29:10 server systemd[1]: tor@default.service: Start request repeated too quickly.
Mar 24 09:29:10 server systemd[1]: Failed to start Anonymizing overlay network for TCP.
Mar 24 09:29:10 server systemd[1]: tor@default.service: Unit entered failed state.
Mar 24 09:29:10 server systemd[1]: tor@default.service: Failed with result 'start-limit-hit'.

Any solutions to this issue?

Cryptux · March 24, 2023, 1:54pm

Hi,

How looks your torrc configuration file? Your relay is new or already running?

kaiod · March 24, 2023, 3:14pm

Welcome @Cryptux, here is the torrc file, it is a new relay.

#Example torrc for relay nodes
#Non-exit, logs, no socks proxy, ORPort 9001


#RELAY CONFIG:

##Open ORPort on 9001 for inbound relay traffic.
###You will definitely need to expose this port to NAT and adjust iptables as necessary.
ORPort 9001

##Set a nickname.

##Disable exit relaying.
###Exit relays are a very important part of the tor network.
###However, you should not attempt to run one unless you are fully aware of the potential consequences of doing so.
###Therefore, this config blocks exit relaying by default.
ExitPolicy reject *:*

#TOR CONFIG:

##Disable Socks to avoid exposing the relay.
SocksPort 0

##Log to /var/log/tor/notice.log.
###Log file will contain useful information for running this relay.

Nickname xxxxx # Change "myNiceRelay" to something you like

Below is the error again

tor@default.service - Anonymizing overlay network for TCP
   Loaded: loaded (/lib/systemd/system/tor@default.service; static; vendor preset: enabled)
   Active: failed (Result: start-limit-hit) since Fri 2023-03-24 11:46:26 -03; 2min 59s ago
  Process: 95317 ExecStart=/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 (code=exited, status
  Process: 95313 ExecStartPre=/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 --verify-config (
  Process: 95310 ExecStartPre=/usr/bin/install -Z -m 02755 -o debian-tor -g debian-tor -d /var/run/tor (code=exited, status=0/SUCCESS)
 Main PID: 95317 (code=exited, status=1/FAILURE)

Mar 24 11:46:26 server systemd[1]: tor@default.service: Main process exited, code=exited, status=1/FAILURE
Mar 24 11:46:26 server systemd[1]: Failed to start Anonymizing overlay network for TCP.
Mar 24 11:46:26 server systemd[1]: tor@default.service: Unit entered failed state.
Mar 24 11:46:26 server systemd[1]: tor@default.service: Failed with result 'exit-code'.
Mar 24 11:46:26 server systemd[1]: tor@default.service: Service hold-off time over, scheduling restart.
Mar 24 11:46:26 server systemd[1]: Stopped Anonymizing overlay network for TCP.
Mar 24 11:46:26 server systemd[1]: tor@default.service: Start request repeated too quickly.
Mar 24 11:46:26 server systemd[1]: Failed to start Anonymizing overlay network for TCP.
Mar 24 11:46:26 server systemd[1]: tor@default.service: Unit entered failed state.
Mar 24 11:46:26 server systemd[1]: tor@default.service: Failed with result 'start-limit-hit'.

Cryptux · March 24, 2023, 8:00pm

All other settings are commented?

I don’t see a miss config (even if I’m not expert), except the SocksPort other settings are used to my relay too (normal).

So if you comment SocksPort, still error?

I found this old post from here: Error message on new relay if it can help you

Enkidu-6 · March 29, 2023, 11:16am

Not sure if you’ve redacted some of the info in your torrc file or it simply doesn’t have the info. It’s missing a few things. You don’t have an email address, IP address, path to log file or data directory, etc …

A basic sample of a torrc file for a non-exit relay looks something like this:

ControlSocket /run/tor/control
ControlSocketsGroupWritable 1
CookieAuthentication 1
CookieAuthFile /run/tor/control.authcookie
CookieAuthFileGroupReadable 1

SOCKSPort 0

Log notice file /var/log/tor/notices.log

DataDirectory /var/lib/tor

ORPort Port_Number

Address Domain_name or IPAddress

Nickname Your_Nickname

ContactInfo Nickname <your_email_address>

ExitRelay 0

EntryStatistics 1
ConnDirectionStatistics 1

# If you run more than one relay, add the fingerprints for  all your relays:
MyFamily