Can't launch 2nd/3rd instance , keeps crashing

Support Relay Operator
1

I’ve been trying since yesterday and i’m at my wits end here. Any ideas or help are GREATLY appreciated folks.

I’ve created two more instances , besides the debian-tor , the default one.

At first, they launched but they kept crashing and restarting in mere minutes in a loop fashion. “What the heck…?”, so i restarted my machine. Aaand they never launched again.

Each has different ORPort,ControlPort,SocksPort, those are covered.
I don’t think it’s a folder rights issue, at least nothing complains for such.

Below are the config files, am i doing something wrong?

DataDirectory /var/lib/tor-instances/@@NAME@@
PidFile /run/tor-instances/@@NAME@@/tor.pid
RunAsDaemon 1
User _tor-@@NAME@@
SyslogIdentityTag @@NAME@@

ControlSocket /run/tor-instances/@@NAME@@/control GroupWritable RelaxDirModeCheck
ControlSocketsGroupWritable 1
SocksPort unix:/run/tor-instances/@@NAME@@/socks WorldWritable

CookieAuthentication 1
CookieAuthFile /run/tor-instances/@@NAME@@/control.authcookie

Log notice syslog

# This is the tor configuration file for tor instance Arte1.
#
# To start/reload/etc this instance, run "systemctl start tor@Arte1" (or reload, or..).
# This instance will run as user _tor-Arte1; its data directory is /var/lib/tor-instances/Arte1.
#
# Append to the list of socks interfaces configured via
# /usr/share/tor/tor-service-defaults-torrc-instances
# which is unix:/run/tor-instances/Arte1/socks

SocksPolicy accept 192.168.0.0/16
SocksPolicy reject *
SocksPort 9060
ORPort 9000
ControlPort 9052
ExtORPort auto
ExitRelay 0
AddressDisableIPv6 1

Log notice file /var/lib/tor-instances/Arte1/notice.log
DataDirectory /var/lib/tor-instances/Arte1
CookieAuthentication 1
CookieAuthFile /run/tor-instances/Arte1/control.authcookie
BandwidthRate 20 MB
BandwidthBurst 20 MB

ContactInfo 50shadesofblue85@gmail.com
Nickname Arte
MyFamily BCD6F192B49F8E24958FF5E60A1BDF8CEA7D1B51,D757F61F8AA6F99F3F79E67CF5A94F259449F52A,CDEB3DEFF99F41233BAE982143365BF4FDE31708,1417DDCB6819F2D0A885313F5F9D8F6313E134F2

ServerDNSDetectHijacking 1
CellStatistics 1
EntryStatistics 1
ConnDirectionStatistics 1

This what i get from systemctl status and journalctl :

arte@ArteDesktopLM:~$ systemctl status tor@Arte1.service
× tor@Arte1.service - Anonymizing overlay network for TCP (instance Arte1)
     Loaded: loaded (/lib/systemd/system/tor@.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/tor@.service.d
             └─override.conf
     Active: failed (Result: exit-code) since Thu 2024-09-19 00:11:27 EEST; 49s ago
    Process: 476127 ExecStartPre=/usr/bin/install -Z -m 02755 -o _tor-Arte1 -g _tor-Arte1 -d /run/tor-instances/Arte1 (code=exited, status=0/SUCCESS)
    Process: 476128 ExecStartPre=/bin/sed -e s/@@NAME@@/Arte1/g; w /run/tor-instances/Arte1.defaults /usr/share/tor/tor-service-defaults-torrc-instances (code=exited, status=0/SUCCESS)
    Process: 476129 ExecStartPre=/usr/bin/tor --defaults-torrc /run/tor-instances/Arte1.defaults -f /etc/tor/instances/Arte1/torrc (code=exited, status=0/SUCCESS)
    Process: 476134 ExecStart=/usr/bin/tor --defaults-torrc /run/tor-instances/Arte1.defaults -f /etc/tor/instances/Arte1/torrc (code=exited, status=1/FAILURE)
   Main PID: 476134 (code=exited, status=1/FAILURE)
        CPU: 99ms


arte@ArteDesktopLM:~$ journalctl -xeu tor@Arte1.service
Sep 19 00:11:27 ArteDesktopLM tor[476134]: Sep 19 00:11:27.278 [notice] Opened Extended OR listener connection (ready) on 127.0.0.1:35439
Sep 19 00:11:27 ArteDesktopLM tor[476134]: Sep 19 00:11:27.278 [notice] Closing partially-constructed Extended OR listener connection (ready) on 127.0.0.1:35439
Sep 19 00:11:27 ArteDesktopLM tor[476134]: Sep 19 00:11:27.278 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Sep 19 00:11:27 ArteDesktopLM tor[476134]: Sep 19 00:11:27.278 [err] Reading config failed--see warnings above.
Sep 19 00:11:27 ArteDesktopLM systemd[1]: tor@Arte1.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit tor@Arte1.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Sep 19 00:11:27 ArteDesktopLM systemd[1]: tor@Arte1.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit tor@Arte1.service has entered the 'failed' state with result 'exit-code'.
Sep 19 00:11:27 ArteDesktopLM systemd[1]: Failed to start Anonymizing overlay network for TCP (instance Arte1).
░░ Subject: A start job for unit tor@Arte1.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit tor@Arte1.service has finished with a failure.
░░ 
░░ The job identifier is 19560 and the job result is failed.

I just can’t find whats wrong. Any ideas?

2

You should post the tor@Arte1.service contents also.
If the service type therein is Type=notify, uncomment the PidFile and RunAsDaemon lines in torrc and try again.

There also should be the line TimeoutStartSec=300 in tor@Arte1.service.

That means systemd waits 5 minutes for a startup notification. If it doesn’t receive this notification, it restarts the instance. If tor runs as daemon, it doesn’t notify systemd. This causes this infinite restart loop.

1 Like
3

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.