Problems running Tor relay and nyx

Hello @all.

I have 2 Tor-relays - 1 is running with nyx and the second is unable to run.
If i start nyx i alwys get “Unable to connect to tor. Are you sure it’s running?”
When i look at systemctls status i see this:

tor.service loaded active exited Anonymizing overlay network for TCP (multi-instance-master)
● tor@default.service loaded failed failed Anonymizing overlay network for TCP

Can anyone of you explain to me why the default service failed !? I made the same things at my second Server and have no Problems o_O …

TiA

Steve

We can’t, we don’t know what went wrong. You should journalctl -eu tor@default to figure out the problem.

Hi HackerNCoder.

This is the output from my NEW relay (without any other things on it - only Debian, 20 Minutes old)

Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: Starting Anonymizing overlay network for TCP...
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18809]: Feb 15 17:37:06.325 [notice] Tor 0.4.5.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, >
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18809]: Feb 15 17:37:06.326 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://sup>
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18809]: Feb 15 17:37:06.326 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18809]: Feb 15 17:37:06.326 [notice] Read configuration file "/etc/tor/torrc".
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18809]: Feb 15 17:37:06.328 [notice] Based on detected system memory, MaxMemInQueues is set to 1451 MB. You can >
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18809]: Feb 15 17:37:06.328 [warn] Failed to parse/validate config: RelayBandwidthBurst (4294967295) must be at >
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18809]: Feb 15 17:37:06.328 [err] Reading config failed--see warnings above.
Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: tor@default.service: Control process exited, code=exited, status=1/FAILURE
Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: tor@default.service: Failed with result 'exit-code'.
Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: Failed to start Anonymizing overlay network for TCP.
Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: tor@default.service: Scheduled restart job, restart counter is at 1.
Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: Stopped Anonymizing overlay network for TCP.
Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: Starting Anonymizing overlay network for TCP...
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18813]: Feb 15 17:37:06.561 [notice] Tor 0.4.5.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, >
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18813]: Feb 15 17:37:06.561 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://sup>
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18813]: Feb 15 17:37:06.561 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18813]: Feb 15 17:37:06.561 [notice] Read configuration file "/etc/tor/torrc".
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18813]: Feb 15 17:37:06.562 [notice] Based on detected system memory, MaxMemInQueues is set to 1451 MB. You can >
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18813]: Feb 15 17:37:06.562 [warn] Failed to parse/validate config: RelayBandwidthBurst (4294967295) must be at >
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18813]: Feb 15 17:37:06.563 [err] Reading config failed--see warnings above.
Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: tor@default.service: Control process exited, code=exited, status=1/FAILURE
Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: tor@default.service: Failed with result 'exit-code'.
Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: Failed to start Anonymizing overlay network for TCP.
Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: tor@default.service: Scheduled restart job, restart counter is at 2.
Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: Stopped Anonymizing overlay network for TCP.
Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: Starting Anonymizing overlay network for TCP...
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18817]: Feb 15 17:37:06.796 [notice] Tor 0.4.5.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, >
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18817]: Feb 15 17:37:06.797 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://sup>
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18817]: Feb 15 17:37:06.797 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18817]: Feb 15 17:37:06.797 [notice] Read configuration file "/etc/tor/torrc".
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18817]: Feb 15 17:37:06.799 [notice] Based on detected system memory, MaxMemInQueues is set to 1451 MB. You can >
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18817]: Feb 15 17:37:06.799 [warn] Failed to parse/validate config: RelayBandwidthBurst (4294967295) must be at >
Feb 15 17:37:06 debian-2gb-hel1-2 tor[18817]: Feb 15 17:37:06.799 [err] Reading config failed--see warnings above.
Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: tor@default.service: Control process exited, code=exited, status=1/FAILURE
Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: tor@default.service: Failed with result 'exit-code'.
Feb 15 17:37:06 debian-2gb-hel1-2 systemd[1]: Failed to start Anonymizing overlay network for TCP.
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: tor@default.service: Scheduled restart job, restart counter is at 3.
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: Stopped Anonymizing overlay network for TCP.
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: Starting Anonymizing overlay network for TCP...
Feb 15 17:37:07 debian-2gb-hel1-2 tor[18821]: Feb 15 17:37:07.051 [notice] Tor 0.4.5.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, >
Feb 15 17:37:07 debian-2gb-hel1-2 tor[18821]: Feb 15 17:37:07.052 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://sup>
Feb 15 17:37:07 debian-2gb-hel1-2 tor[18821]: Feb 15 17:37:07.052 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 15 17:37:07 debian-2gb-hel1-2 tor[18821]: Feb 15 17:37:07.052 [notice] Read configuration file "/etc/tor/torrc".
Feb 15 17:37:07 debian-2gb-hel1-2 tor[18821]: Feb 15 17:37:07.053 [notice] Based on detected system memory, MaxMemInQueues is set to 1451 MB. You can >
Feb 15 17:37:07 debian-2gb-hel1-2 tor[18821]: Feb 15 17:37:07.054 [warn] Failed to parse/validate config: RelayBandwidthBurst (4294967295) must be at >
Feb 15 17:37:07 debian-2gb-hel1-2 tor[18821]: Feb 15 17:37:07.054 [err] Reading config failed--see warnings above.
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: tor@default.service: Control process exited, code=exited, status=1/FAILURE
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: tor@default.service: Failed with result 'exit-code'.
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: Failed to start Anonymizing overlay network for TCP.
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: tor@default.service: Scheduled restart job, restart counter is at 4.
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: Stopped Anonymizing overlay network for TCP.
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: Starting Anonymizing overlay network for TCP...
Feb 15 17:37:07 debian-2gb-hel1-2 tor[18825]: Feb 15 17:37:07.311 [notice] Tor 0.4.5.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, >
Feb 15 17:37:07 debian-2gb-hel1-2 tor[18825]: Feb 15 17:37:07.311 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://sup>
Feb 15 17:37:07 debian-2gb-hel1-2 tor[18825]: Feb 15 17:37:07.311 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 15 17:37:07 debian-2gb-hel1-2 tor[18825]: Feb 15 17:37:07.311 [notice] Read configuration file "/etc/tor/torrc".
Feb 15 17:37:07 debian-2gb-hel1-2 tor[18825]: Feb 15 17:37:07.313 [notice] Based on detected system memory, MaxMemInQueues is set to 1451 MB. You can >
Feb 15 17:37:07 debian-2gb-hel1-2 tor[18825]: Feb 15 17:37:07.313 [warn] Failed to parse/validate config: RelayBandwidthBurst (4294967295) must be at >
Feb 15 17:37:07 debian-2gb-hel1-2 tor[18825]: Feb 15 17:37:07.313 [err] Reading config failed--see warnings above.
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: tor@default.service: Control process exited, code=exited, status=1/FAILURE
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: tor@default.service: Failed with result 'exit-code'.
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: Failed to start Anonymizing overlay network for TCP.
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: tor@default.service: Scheduled restart job, restart counter is at 5.
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: Stopped Anonymizing overlay network for TCP.
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: tor@default.service: Start request repeated too quickly.
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: tor@default.service: Failed with result 'exit-code'.
Feb 15 17:37:07 debian-2gb-hel1-2 systemd[1]: Failed to start Anonymizing overlay network for TCP.

Greets,

Steve

Ah :slight_smile:

I found the error

It was the Bandwith - now i have to take a look at the others :slight_smile:

No … Error at the second Server:

root@matrix:~# journalctl -xe
Feb 15 17:59:32 matrix tor[50080]: Feb 15 17:59:32.170 [warn] Could not bind to :::443: Address already in use. Is Tor already running?
Feb 15 17:59:32 matrix tor[50080]: Feb 15 17:59:32.170 [notice] Opening Directory listener on 0.0.0.0:9030
Feb 15 17:59:32 matrix tor[50080]: Feb 15 17:59:32.170 [notice] Opened Directory listener connection (ready) on 0.0.0.0:9030
Feb 15 17:59:32 matrix tor[50080]: Feb 15 17:59:32.170 [notice] Closing partially-constructed Control listener connection (ready) on 127.0.0.1:9051
Feb 15 17:59:32 matrix tor[50080]: Feb 15 17:59:32.170 [notice] Closing partially-constructed OR listener connection (ready) on 0.0.0.0:9001
Feb 15 17:59:32 matrix tor[50080]: Feb 15 17:59:32.170 [notice] Closing partially-constructed OR listener connection (ready) on [::]:9001
Feb 15 17:59:32 matrix tor[50080]: Feb 15 17:59:32.170 [notice] Closing partially-constructed Directory listener connection (ready) on 0.0.0.0:9030
Feb 15 17:59:32 matrix tor[50080]: Feb 15 17:59:32.170 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Feb 15 17:59:32 matrix tor[50080]: Feb 15 17:59:32.170 [err] Reading config failed--see warnings above.
Feb 15 17:59:32 matrix systemd[1]: tor@default.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit tor@default.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Feb 15 17:59:32 matrix systemd[1]: tor@default.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit tor@default.service has entered the 'failed' state with result 'exit-code'.
Feb 15 17:59:32 matrix systemd[1]: Failed to start Anonymizing overlay network for TCP.
░░ Subject: A start job for unit tor@default.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit tor@default.service has finished with a failure.
░░
░░ The job identifier is 11190 and the job result is failed.
Feb 15 17:59:32 matrix systemd[1]: tor@default.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit tor@default.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Feb 15 17:59:32 matrix systemd[1]: Stopped Anonymizing overlay network for TCP.
░░ Subject: A stop job for unit tor@default.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit tor@default.service has finished.
░░
░░ The job identifier is 11260 and the job result is done.
Feb 15 17:59:32 matrix systemd[1]: tor@default.service: Start request repeated too quickly.
Feb 15 17:59:32 matrix systemd[1]: tor@default.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit tor@default.service has entered the 'failed' state with result 'exit-code'.
Feb 15 17:59:32 matrix systemd[1]: Failed to start Anonymizing overlay network for TCP.
░░ Subject: A start job for unit tor@default.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit tor@default.service has finished with a failure.
░░
░░ The job identifier is 11260 and the job result is failed.
Feb 15 17:59:34 matrix kernel: [UFW AUDIT] IN= OUT=eth0 SRC=5.75.184.204 DST=152.89.160.131 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=25123 DF PROTO=TCP SPT=42658 DPT=60092 WINDOW=64240 RES=0x00 SYN URGP=0
Feb 15 17:59:34 matrix kernel: [UFW ALLOW] IN= OUT=eth0 SRC=5.75.184.204 DST=152.89.160.131 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=25123 DF PROTO=TCP SPT=42658 DPT=60092 WINDOW=64240 RES=0x00 SYN URGP=0
Feb 15 17:59:38 matrix sshd[50049]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.145  user=root
Feb 15 17:59:39 matrix kernel: [UFW AUDIT] IN=eth0 OUT= MAC=96:00:01:e5:72:a4:d2:74:7f:6e:37:e3:86:dd SRC=2a00:1098:0084:01c8:0000:0000:0000:0158 DST=2a01:04f8:1c1e:5f49:0000:0000:0000:0001 LEN=80 TC=0 HOPLIMIT=54 FLOWLBL=452975 PROTO=TCP SPT=56206 DPT=443 WINDOW=648>
Feb 15 17:59:39 matrix kernel: [UFW AUDIT] IN=eth0 OUT= MAC=96:00:01:e5:72:a4:d2:74:7f:6e:37:e3:86:dd SRC=2a00:1098:0084:01c8:0000:0000:0000:0158 DST=2a01:04f8:1c1e:5f49:0000:0000:0000:0001 LEN=80 TC=0 HOPLIMIT=54 FLOWLBL=863283 PROTO=TCP SPT=56216 DPT=443 WINDOW=648>
Feb 15 17:59:39 matrix kernel: [UFW AUDIT] IN= OUT=eth0 SRC=2a01:04f8:1c1e:5f49:0000:0000:0000:0001 DST=2a01:04ff:ff00:0000:0000:0000:0add:0001 LEN=94 TC=0 HOPLIMIT=64 FLOWLBL=585099 PROTO=UDP SPT=39133 DPT=53 LEN=54
Feb 15 17:59:39 matrix kernel: [UFW ALLOW] IN= OUT=eth0 SRC=2a01:04f8:1c1e:5f49:0000:0000:0000:0001 DST=2a01:04ff:ff00:0000:0000:0000:0add:0001 LEN=94 TC=0 HOPLIMIT=64 FLOWLBL=585099 PROTO=UDP SPT=39133 DPT=53 LEN=54
Feb 15 17:59:39 matrix kernel: [UFW AUDIT] IN=eth0 OUT= MAC=96:00:01:e5:72:a4:d2:74:7f:6e:37:e3:86:dd SRC=2a00:1098:0084:01c8:0000:0000:0000:0158 DST=2a01:04f8:1c1e:5f49:0000:0000:0000:0001 LEN=80 TC=0 HOPLIMIT=53 FLOWLBL=887376 PROTO=TCP SPT=56226 DPT=443 WINDOW=648>
Feb 15 17:59:39 matrix kernel: [UFW AUDIT] IN=eth0 OUT= MAC=96:00:01:e5:72:a4:d2:74:7f:6e:37:e3:86:dd SRC=2a00:1098:0084:01c8:0000:0000:0000:0157 DST=2a01:04f8:1c1e:5f49:0000:0000:0000:0001 LEN=80 TC=0 HOPLIMIT=53 FLOWLBL=417408 PROTO=TCP SPT=53546 DPT=443 WINDOW=648>
Feb 15 17:59:39 matrix sshd[50049]: Failed password for root from 61.177.172.145 port 43172 ssh2
Feb 15 17:59:39 matrix kernel: [UFW AUDIT] IN=eth0 OUT= MAC=96:00:01:e5:72:a4:d2:74:7f:6e:37:e3:86:dd SRC=2a00:1098:0084:01c8:0000:0000:0000:0158 DST=2a01:04f8:1c1e:5f49:0000:0000:0000:0001 LEN=80 TC=0 HOPLIMIT=53 FLOWLBL=747018 PROTO=TCP SPT=56234 DPT=443 WINDOW=648>

I found the second error :wink:

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