My relay stopped working and I don't know why

cocolinofan · February 13, 2025, 9:31pm

Hello,

My relay stopped working (I think) and I don’t know why. How do I know it stopped working? Well, running nyx returns (even after sudo chown $USER:debian-tor /var/run/tor/control.authcookie):

Unable to authenticate: socket connection failed ([Errno 111] Connection refused)

And, it also says on the website that it stopped working, but that’s much slower to update.

My /etc/tor/torrc:

ControlPort 9051
CookieAuthentication 1
CookieAuthFileGroupReadable 1
ORPort 9001 IPv4Only
Nickname FreeInternet
ContactInfo <cocolinofan@protonmail.com>PGP: D8E7 0DAC 2CB9 F4DE 2728 00D5 8CCA F633 B685 9E80

Looking at the running process with htop I see a process running with high CPU usage:
/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 and systemctl status tor returns:

● tor.service - Anonymizing overlay network for TCP (multi-instance-master)
     Loaded: loaded (/lib/systemd/system/tor.service; enabled; preset: enabled)
     Active: active (exited) since Thu 2025-02-13 18:57:03 GMT; 25min ago
    Process: 1319 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
   Main PID: 1319 (code=exited, status=0/SUCCESS)
        CPU: 9ms

Feb 13 18:57:03 battleMini systemd[1]: Starting tor.service - Anonymizing overlay network for TCP (multi-instance-master)...
Feb 13 18:57:03 battleMini systemd[1]: Finished tor.service - Anonymizing overlay network for TCP (multi-instance-master).

Looking at journalctl -e -u tor@default I see:

Feb 13 19:22:11 battleMini tor[1432]: Feb 13 19:22:11.453 [notice] Tor 0.4.7.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.15, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Feb 13 19:22:11 battleMini tor[1432]: Feb 13 19:22:11.453 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 13 19:22:11 battleMini tor[1432]: Feb 13 19:22:11.453 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 13 19:22:11 battleMini tor[1432]: Feb 13 19:22:11.454 [notice] Read configuration file "/etc/tor/torrc".
Feb 13 19:22:11 battleMini tor[1432]: Feb 13 19:22:11.475 [notice] Based on detected system memory, MaxMemInQueues is set to 690 MB. You can override this by setting MaxMemInQueues by hand.
Feb 13 19:22:11 battleMini tor[1432]: Feb 13 19:22:11.476 [notice] By default, Tor does not run as an exit relay. If you want to be an exit relay, set ExitRelay to 1. To suppress this message in the future, set ExitRelay to 0.
Feb 13 19:22:11 battleMini tor[1432]: Feb 13 19:22:11.493 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 13 19:22:11 battleMini tor[1432]: Feb 13 19:22:11.494 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Feb 13 19:22:11 battleMini tor[1432]: Feb 13 19:22:11.494 [notice] Opening Control listener on 127.0.0.1:9051
Feb 13 19:22:11 battleMini tor[1432]: Feb 13 19:22:11.494 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051
Feb 13 19:22:11 battleMini tor[1432]: Feb 13 19:22:11.494 [notice] Opening OR listener on 0.0.0.0:9001
Feb 13 19:22:11 battleMini tor[1432]: Feb 13 19:22:11.494 [notice] Opened OR listener connection (ready) on 0.0.0.0:9001
Feb 13 19:22:11 battleMini Tor[1432]: We compiled with OpenSSL 300000b0: OpenSSL 3.0.11 19 Sep 2023 and we are running with OpenSSL 300000f0: 3.0.15. These two versions should be binary compatible.
Feb 13 19:22:11 battleMini Tor[1432]: Tor 0.4.7.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.15, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Feb 13 19:22:11 battleMini Tor[1432]: Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 13 19:22:11 battleMini Tor[1432]: Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 13 19:22:11 battleMini Tor[1432]: Read configuration file "/etc/tor/torrc".
Feb 13 19:22:11 battleMini Tor[1432]: Based on detected system memory, MaxMemInQueues is set to 690 MB. You can override this by setting MaxMemInQueues by hand.
Feb 13 19:22:11 battleMini Tor[1432]: By default, Tor does not run as an exit relay. If you want to be an exit relay, set ExitRelay to 1. To suppress this message in the future, set ExitRelay to 0.
Feb 13 19:22:11 battleMini Tor[1432]: Opening Socks listener on 127.0.0.1:9050
Feb 13 19:22:11 battleMini Tor[1432]: Opened Socks listener connection (ready) on 127.0.0.1:9050
Feb 13 19:22:11 battleMini Tor[1432]: Opening Control listener on 127.0.0.1:9051
Feb 13 19:22:11 battleMini Tor[1432]: Opened Control listener connection (ready) on 127.0.0.1:9051
Feb 13 19:22:11 battleMini Tor[1432]: Opening OR listener on 0.0.0.0:9001
Feb 13 19:22:11 battleMini Tor[1432]: Opened OR listener connection (ready) on 0.0.0.0:9001
lines 538-603/603 (END)

  `.::///+:/-.        --///+//-:``    cocolino@battleMini 
 `+oooooooooooo:   `+oooooooooooo:    ------------------- 
  /oooo++//ooooo:  ooooo+//+ooooo.    OS: Raspbian GNU/Linux 12 (bookworm) armv7l 
  `+ooooooo:-:oo-  +o+::/ooooooo:     Host: Raspberry Pi 2 Model B Rev 1.1 
   `:oooooooo+``    `.oooooooo+-      Kernel: 6.6.74+rpt-rpi-v7 
     `:++ooo/.        :+ooo+/.`       Uptime: 1 day, 47 mins 
        ...`  `.----.` ``..           Packages: 1645 (dpkg) 
     .::::-``:::::::::.`-:::-`        Shell: bash 5.2.15 
    -:::-`   .:::::::-`  `-:::-       Terminal: /dev/pts/1 
   `::.  `.--.`  `` `.---.``.::`      CPU: BCM2835 (4) @ 900MHz 
       .::::::::`  -::::::::` `       Memory: 104MiB / 920MiB 
 .::` .:::::::::- `::::::::::``::.
-:::` ::::::::::.  ::::::::::.`:::-                           
::::  -::::::::.   `-::::::::  ::::                           
-::-   .-:::-.``....``.-::-.   -::-
 .. ``       .::::::::.     `..`..
   -:::-`   -::::::::::`  .:::::`
   :::::::` -::::::::::` :::::::.
   .:::::::  -::::::::. ::::::::
    `-:::::`   ..--.`   ::::::.
      `...`  `...--..`  `...`
            .::::::::::
             `.-::::-`

I also did some network changes, but I don’t think the problem is related to that. I setup all the port forwarding for port 9001, and the relay has the same external IP.
I am confused.

jarl · February 13, 2025, 11:13pm

I think your tor version i too old, the log says you are running 0.4.7.16. As far as i know this version will be rejected by the authorities. You should update your tor and try again. The current version is 0.4.8.14.

And instead of changing the ownership of the cookie file you can also run nyx as tor user sudo -u debian-tor nyx

atari · February 14, 2025, 4:27pm

Yes, it is too old: Consensus health

You should also have a related warning in your logs.

If your relay still does not work after upgrading, you might have a look at your network changes

cocolinofan · February 14, 2025, 9:30pm

Thank you guys. I will deal with the outdated version of Tor later, I have an ARM 32 bit computer ( armhf) and the official guide says that if you have an armhf on Debian, you are out of luck. I did find something (Debian -- Details of package tor in bookworm-backports) that I thought should give me the latest version of Tor.

But, what confuses me is why I have a process running /usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 using lots CPU and systemctl status tor says active (exited).

P.S. The sudo -u debian-tor nyx returns the same error:

Unable to authenticate: socket connection failed ([Errno 111] Connection refused)

But I suspect nyx is acting up because Tor is not running or not running how it supposed to.

What logs should I look into?

jarl · February 15, 2025, 3:46pm

I guess the tor process is still running because getting rejected by the authorities doesn’t mean it terminates. And since you have a Socks Listener open it continues to hold open some circuits etc.

The relay search link you posted says the relay was on 0.4.8.13 the last time it was seen? Did you run it on another computer before?

atari · February 15, 2025, 3:47pm

How did you install the bookworm backport?

You have to enable the repo: Instructions
and then run
apt-get install tor/bookworm-backports

After that try systemctl stop tor and systemctl start tor again…

cocolinofan · February 15, 2025, 5:54pm

Oh, that’s how you install from the added repository? Thank you, I don’t think I would have figured this out my myself.

I am now running Tor v0.4.8.13
The problem is still there tho

What I did:
sudo systemctl stop tor
sudo systemctl disable tor
sudo apt remove tor
sudo apt autoremove
restart computer
sudo apt-get install tor/bookworm-backports
sudo cp torrc /etc/tor/torrc
sudo systemctl start tor
sudo systemctl enable tor

What I get:
=>sudo -u debian-tor nyx returns Unable to authenticate: socket connection failed ([Errno 111] Connection refused)
=>There is a process running: /usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0
=>systemctl status tor is the same as before active (exited)
=>journalctl -e -u tor@default:

Feb 15 16:45:14 battleMini tor[843]: Feb 15 16:45:14.567 [notice] Opening Control listener on 127.0.0.1:9051
Feb 15 16:45:14 battleMini tor[843]: Feb 15 16:45:14.567 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051
Feb 15 16:45:14 battleMini tor[843]: Feb 15 16:45:14.567 [notice] Opening OR listener on 0.0.0.0:9001
Feb 15 16:45:14 battleMini tor[843]: Feb 15 16:45:14.567 [notice] Opened OR listener connection (ready) on 0.0.0.0:9001
Feb 15 16:45:14 battleMini Tor[843]: We compiled with OpenSSL 300000f0: OpenSSL 3.0.15 3 Sep 2024 and we are running with OpenSSL 300000f0: 3.0.15. These two versions should be binary compatible.
Feb 15 16:45:14 battleMini Tor[843]: Tor 0.4.8.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.15, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Feb 15 16:45:14 battleMini Tor[843]: Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 15 16:45:14 battleMini Tor[843]: Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 15 16:45:14 battleMini Tor[843]: Read configuration file "/etc/tor/torrc".
Feb 15 16:45:14 battleMini Tor[843]: Based on detected system memory, MaxMemInQueues is set to 690 MB. You can override this by setting MaxMemInQueues by hand.
Feb 15 16:45:14 battleMini Tor[843]: By default, Tor does not run as an exit relay. If you want to be an exit relay, set ExitRelay to 1. To suppress this message in the future, set ExitRelay to 0.
Feb 15 16:45:14 battleMini Tor[843]: Opening Socks listener on 127.0.0.1:9050
Feb 15 16:45:14 battleMini Tor[843]: Opened Socks listener connection (ready) on 127.0.0.1:9050
Feb 15 16:45:14 battleMini Tor[843]: Opening Control listener on 127.0.0.1:9051
Feb 15 16:45:14 battleMini Tor[843]: Opened Control listener connection (ready) on 127.0.0.1:9051
Feb 15 16:45:14 battleMini Tor[843]: Opening OR listener on 0.0.0.0:9001
Feb 15 16:45:14 battleMini Tor[843]: Opened OR listener connection (ready) on 0.0.0.0:9001
Feb 15 16:45:41 battleMini Tor[843]: Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Feb 15 16:45:43 battleMini Tor[843]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Feb 15 16:45:46 battleMini Tor[843]: Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Feb 15 16:45:52 battleMini Tor[843]: Your Tor server's identity key fingerprint is 'FreeInternet 78CFF6C66B9AF5CB6ED30472ED3BC39C423F0000'
Feb 15 16:45:52 battleMini Tor[843]: Your Tor server's identity key ed25519 fingerprint is 'FreeInternet i3xbtzCa1+EXalL9KSccRQxUu0V95ABcYBYSV97MHfo'
Feb 15 16:45:52 battleMini Tor[843]: Bootstrapped 0% (starting): Starting
Feb 15 16:50:14 battleMini systemd[1]: tor@default.service: start operation timed out. Terminating.
Feb 15 16:51:14 battleMini systemd[1]: tor@default.service: State 'stop-sigterm' timed out. Killing.
Feb 15 16:51:14 battleMini systemd[1]: tor@default.service: Killing process 843 (tor) with signal SIGKILL.
Feb 15 16:51:14 battleMini systemd[1]: tor@default.service: Main process exited, code=killed, status=9/KILL
Feb 15 16:51:14 battleMini systemd[1]: tor@default.service: Failed with result 'timeout'.
Feb 15 16:51:14 battleMini systemd[1]: Failed to start tor@default.service - Anonymizing overlay network for TCP.
Feb 15 16:51:14 battleMini systemd[1]: tor@default.service: Consumed 6min 654ms CPU time.
Feb 15 16:51:15 battleMini systemd[1]: tor@default.service: Scheduled restart job, restart counter is at 1.
Feb 15 16:51:15 battleMini systemd[1]: Stopped tor@default.service - Anonymizing overlay network for TCP.
Feb 15 16:51:15 battleMini systemd[1]: tor@default.service: Consumed 6min 654ms CPU time.
Feb 15 16:51:15 battleMini systemd[1]: Starting tor@default.service - Anonymizing overlay network for TCP...
Feb 15 16:51:15 battleMini tor[855]: Feb 15 16:51:15.351 [notice] Tor 0.4.8.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.15, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Feb 15 16:51:15 battleMini tor[855]: Feb 15 16:51:15.352 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 15 16:51:15 battleMini tor[855]: Feb 15 16:51:15.352 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 15 16:51:15 battleMini tor[855]: Feb 15 16:51:15.352 [notice] Read configuration file "/etc/tor/torrc".
Feb 15 16:51:15 battleMini tor[855]: Feb 15 16:51:15.366 [notice] Based on detected system memory, MaxMemInQueues is set to 690 MB. You can override this by setting MaxMemInQueues by hand.
Feb 15 16:51:15 battleMini tor[855]: Feb 15 16:51:15.366 [notice] By default, Tor does not run as an exit relay. If you want to be an exit relay, set ExitRelay to 1. To suppress this message in the future, set ExitRelay to 0.
Feb 15 16:51:15 battleMini tor[855]: Configuration was valid
Feb 15 16:51:15 battleMini tor[856]: Feb 15 16:51:15.793 [notice] Tor 0.4.8.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.15, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Feb 15 16:51:15 battleMini tor[856]: Feb 15 16:51:15.794 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 15 16:51:15 battleMini tor[856]: Feb 15 16:51:15.794 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 15 16:51:15 battleMini tor[856]: Feb 15 16:51:15.794 [notice] Read configuration file "/etc/tor/torrc".
Feb 15 16:51:15 battleMini tor[856]: Feb 15 16:51:15.807 [notice] Based on detected system memory, MaxMemInQueues is set to 690 MB. You can override this by setting MaxMemInQueues by hand.
Feb 15 16:51:15 battleMini tor[856]: Feb 15 16:51:15.808 [notice] By default, Tor does not run as an exit relay. If you want to be an exit relay, set ExitRelay to 1. To suppress this message in the future, set ExitRelay to 0.
Feb 15 16:51:15 battleMini tor[856]: Feb 15 16:51:15.819 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 15 16:51:15 battleMini tor[856]: Feb 15 16:51:15.820 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Feb 15 16:51:15 battleMini tor[856]: Feb 15 16:51:15.820 [notice] Opening Control listener on 127.0.0.1:9051
Feb 15 16:51:15 battleMini tor[856]: Feb 15 16:51:15.820 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051
Feb 15 16:51:15 battleMini tor[856]: Feb 15 16:51:15.820 [notice] Opening OR listener on 0.0.0.0:9001
Feb 15 16:51:15 battleMini tor[856]: Feb 15 16:51:15.820 [notice] Opened OR listener connection (ready) on 0.0.0.0:9001
Feb 15 16:51:15 battleMini Tor[856]: We compiled with OpenSSL 300000f0: OpenSSL 3.0.15 3 Sep 2024 and we are running with OpenSSL 300000f0: 3.0.15. These two versions should be binary compatible.
Feb 15 16:51:15 battleMini Tor[856]: Tor 0.4.8.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.15, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Feb 15 16:51:15 battleMini Tor[856]: Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 15 16:51:15 battleMini Tor[856]: Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 15 16:51:15 battleMini Tor[856]: Read configuration file "/etc/tor/torrc".
Feb 15 16:51:15 battleMini Tor[856]: Based on detected system memory, MaxMemInQueues is set to 690 MB. You can override this by setting MaxMemInQueues by hand.
Feb 15 16:51:15 battleMini Tor[856]: By default, Tor does not run as an exit relay. If you want to be an exit relay, set ExitRelay to 1. To suppress this message in the future, set ExitRelay to 0.
Feb 15 16:51:15 battleMini Tor[856]: Opening Socks listener on 127.0.0.1:9050
Feb 15 16:51:15 battleMini Tor[856]: Opened Socks listener connection (ready) on 127.0.0.1:9050
Feb 15 16:51:15 battleMini Tor[856]: Opening Control listener on 127.0.0.1:9051
Feb 15 16:51:15 battleMini Tor[856]: Opened Control listener connection (ready) on 127.0.0.1:9051
Feb 15 16:51:15 battleMini Tor[856]: Opening OR listener on 0.0.0.0:9001
Feb 15 16:51:15 battleMini Tor[856]: Opened OR listener connection (ready) on 0.0.0.0:9001

Just in case Tor was upset on the network changes I’ve made. I made everything how it used to be (network wise). The Tor computer is connected to the ISP router directly and port 9001 is forwarded to it. It was not it, the problem is still there.

atari · February 16, 2025, 9:05pm

Please put the line

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

in your /etc/tor/torrc and see what the logfile says after your restart tor.

cocolinofan · February 17, 2025, 9:07pm

cocolino@battleMini:/var/log/tor $ cat notices.log 
Feb 17 19:06:55.000 [notice] Tor 0.4.8.13 opening new log file.
Feb 17 19:06:55.247 [notice] We compiled with OpenSSL 300000f0: OpenSSL 3.0.15 3 Sep 2024 and we are running with OpenSSL 300000f0: 3.0.15. These two versions should be binary compatible.
Feb 17 19:06:55.325 [notice] Tor 0.4.8.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.15, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Feb 17 19:06:55.326 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 17 19:06:55.326 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 17 19:06:55.326 [notice] Read configuration file "/etc/tor/torrc".
Feb 17 19:06:55.340 [notice] Based on detected system memory, MaxMemInQueues is set to 690 MB. You can override this by setting MaxMemInQueues by hand.
Feb 17 19:06:55.340 [notice] By default, Tor does not run as an exit relay. If you want to be an exit relay, set ExitRelay to 1. To suppress this message in the future, set ExitRelay to 0.
Feb 17 19:06:55.352 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 17 19:06:55.352 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Feb 17 19:06:55.352 [notice] Opening Control listener on 127.0.0.1:9051
Feb 17 19:06:55.352 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051
Feb 17 19:06:55.352 [notice] Opening OR listener on 0.0.0.0:9001
Feb 17 19:06:55.353 [notice] Opened OR listener connection (ready) on 0.0.0.0:9001
Feb 17 19:07:23.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Feb 17 19:07:26.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Feb 17 19:07:28.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Feb 17 19:07:37.000 [notice] Your Tor server's identity key fingerprint is 'FreeInternet 78CFF6C66B9AF5CB6ED30472ED3BC39C423F0000'
Feb 17 19:07:37.000 [notice] Your Tor server's identity key ed25519 fingerprint is 'FreeInternet i3xbtzCa1+EXalL9KSccRQxUu0V95ABcYBYSV97MHfo'
Feb 17 19:07:37.000 [notice] Bootstrapped 0% (starting): Starting
Feb 17 19:12:56.000 [notice] Tor 0.4.8.13 opening log file.
Feb 17 19:12:56.547 [notice] We compiled with OpenSSL 300000f0: OpenSSL 3.0.15 3 Sep 2024 and we are running with OpenSSL 300000f0: 3.0.15. These two versions should be binary compatible.
Feb 17 19:12:56.626 [notice] Tor 0.4.8.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.15, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Feb 17 19:12:56.626 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 17 19:12:56.626 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 17 19:12:56.627 [notice] Read configuration file "/etc/tor/torrc".
Feb 17 19:12:56.640 [notice] Based on detected system memory, MaxMemInQueues is set to 690 MB. You can override this by setting MaxMemInQueues by hand.
Feb 17 19:12:56.640 [notice] By default, Tor does not run as an exit relay. If you want to be an exit relay, set ExitRelay to 1. To suppress this message in the future, set ExitRelay to 0.
Feb 17 19:12:56.652 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 17 19:12:56.652 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Feb 17 19:12:56.652 [notice] Opening Control listener on 127.0.0.1:9051
Feb 17 19:12:56.652 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051
Feb 17 19:12:56.652 [notice] Opening OR listener on 0.0.0.0:9001
Feb 17 19:12:56.652 [notice] Opened OR listener connection (ready) on 0.0.0.0:9001
Feb 17 19:13:23.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Feb 17 19:13:25.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Feb 17 19:13:28.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Feb 17 19:13:41.000 [notice] Your Tor server's identity key fingerprint is 'FreeInternet 78CFF6C66B9AF5CB6ED30472ED3BC39C423F0000'
Feb 17 19:13:41.000 [notice] Your Tor server's identity key ed25519 fingerprint is 'FreeInternet i3xbtzCa1+EXalL9KSccRQxUu0V95ABcYBYSV97MHfo'
Feb 17 19:13:41.000 [notice] Bootstrapped 0% (starting): Starting
Feb 17 19:18:57.000 [notice] Tor 0.4.8.13 opening log file.
Feb 17 19:18:57.820 [notice] We compiled with OpenSSL 300000f0: OpenSSL 3.0.15 3 Sep 2024 and we are running with OpenSSL 300000f0: 3.0.15. These two versions should be binary compatible.
Feb 17 19:18:57.899 [notice] Tor 0.4.8.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.15, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Feb 17 19:18:57.899 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 17 19:18:57.900 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 17 19:18:57.900 [notice] Read configuration file "/etc/tor/torrc".
Feb 17 19:18:57.914 [notice] Based on detected system memory, MaxMemInQueues is set to 690 MB. You can override this by setting MaxMemInQueues by hand.
Feb 17 19:18:57.914 [notice] By default, Tor does not run as an exit relay. If you want to be an exit relay, set ExitRelay to 1. To suppress this message in the future, set ExitRelay to 0.
Feb 17 19:18:57.926 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 17 19:18:57.926 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Feb 17 19:18:57.926 [notice] Opening Control listener on 127.0.0.1:9051
Feb 17 19:18:57.926 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051
Feb 17 19:18:57.926 [notice] Opening OR listener on 0.0.0.0:9001
Feb 17 19:18:57.927 [notice] Opened OR listener connection (ready) on 0.0.0.0:9001
Feb 17 19:19:25.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Feb 17 19:19:27.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Feb 17 19:19:30.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Feb 17 19:19:36.000 [notice] Your Tor server's identity key fingerprint is 'FreeInternet 78CFF6C66B9AF5CB6ED30472ED3BC39C423F0000'
Feb 17 19:19:36.000 [notice] Your Tor server's identity key ed25519 fingerprint is 'FreeInternet i3xbtzCa1+EXalL9KSccRQxUu0V95ABcYBYSV97MHfo'
Feb 17 19:19:36.000 [notice] Bootstrapped 0% (starting): Starting
cocolino@battleMini:/var/log/tor $ date
Mon 17 Feb 19:20:19 GMT 2025
cocolino@battleMini:/var/log/tor $ sudo ps -aux | grep tor
cocolino   793  0.0  0.6  44216  6528 ?        Ssl  Feb16   0:00 /usr/libexec/xdg-permission-store
debian-+  2523  100 17.0 272124 161096 ?       Rs   19:18   1:23 /usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0
cocolino  2527  8.3  0.1   7532  1792 pts/0    S+   19:20   0:00 grep --color=auto tor

atari · February 18, 2025, 10:04am

That is odd. Guess it is time for adding Log debug file /var/log/tor/debug.log to your torrc to see what is wrong

jarl · February 18, 2025, 10:05am

Could you run sudo -u debian-tor /usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 and let it run for 15 minutes or so? Just to make sure it isn’t just the timeout of the systemd service acting up because tor isn’t starting fast enough.

cocolinofan · February 18, 2025, 6:18pm

cocolino@battleMini:~ $ sudo -u debian-tor /usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0
Feb 18 17:44:47.598 [notice] Tor 0.4.8.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.15, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Feb 18 17:44:47.598 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 18 17:44:47.601 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 18 17:44:47.602 [notice] Read configuration file "/etc/tor/torrc".
Feb 18 17:44:47.612 [notice] Based on detected system memory, MaxMemInQueues is set to 690 MB. You can override this by setting MaxMemInQueues by hand.
Feb 18 17:44:47.612 [notice] By default, Tor does not run as an exit relay. If you want to be an exit relay, set ExitRelay to 1. To suppress this message in the future, set ExitRelay to 0.
Feb 18 17:44:47.621 [notice] Opening Socks listener on /run/tor/socks
Feb 18 17:44:47.621 [warn] Bind to /run/tor/socks failed: No such file or directory.
Feb 18 17:44:47.621 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 18 17:44:47.621 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Feb 18 17:44:47.621 [notice] Opening Control listener on 127.0.0.1:9051
Feb 18 17:44:47.621 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051
Feb 18 17:44:47.622 [warn] Directory /run/tor does not exist.
Feb 18 17:44:47.622 [warn] Before Tor can create a control socket in "/run/tor/control", the directory "/run/tor" needs to exist, and to be accessible only by the user and group account that is running Tor.  (On some Unix systems, anybody who can list a socket can connect to it, so Tor is being careful.)
Feb 18 17:44:47.622 [notice] Opening OR listener on 0.0.0.0:9001
Feb 18 17:44:47.622 [notice] Opened OR listener connection (ready) on 0.0.0.0:9001
Feb 18 17:44:47.622 [notice] Closing partially-constructed Socks listener connection (ready) on 127.0.0.1:9050
Feb 18 17:44:47.622 [notice] Closing partially-constructed Control listener connection (ready) on 127.0.0.1:9051
Feb 18 17:44:47.622 [notice] Closing partially-constructed OR listener connection (ready) on 0.0.0.0:9001
Feb 18 17:44:47.622 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Feb 18 17:44:47.622 [err] Reading config failed--see warnings above.

cocolinofan · February 18, 2025, 6:18pm

There is too much text and pastebin websites won’t take it and the file is bigger then 4Mb (33.4 MiB) so I can’t uploaded it here.

jarl · February 18, 2025, 7:09pm

Seems like the tor service was still running and blocking some ports. Please stop the tor service and make sure nothing is listening on the ports needed.
Also you should create the directory /run/tor and give it the right permissions
mkdir /run/tor && chown debian-tor:debian-tor /run/tor
Then run the command again.

cocolinofan · February 19, 2025, 12:58am

cocolino@battleMini:~ $ sudo ps aux | grep tor
cocolino   796  0.0  0.6  44216  6400 ?        Ssl  20:14   0:00 /usr/libexec/xdg-permission-store
cocolino   851 16.6  0.1   7532  1792 pts/0    S+   20:15   0:00 grep --color=auto tor
cocolino@battleMini:~ $ sudo -u debian-tor /usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0
Feb 18 20:15:48.250 [notice] Tor 0.4.8.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.15, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Feb 18 20:15:48.250 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 18 20:15:48.250 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 18 20:15:48.251 [notice] Read configuration file "/etc/tor/torrc".
Feb 18 20:15:48.264 [notice] Based on detected system memory, MaxMemInQueues is set to 690 MB. You can override this by setting MaxMemInQueues by hand.
Feb 18 20:15:48.264 [notice] By default, Tor does not run as an exit relay. If you want to be an exit relay, set ExitRelay to 1. To suppress this message in the future, set ExitRelay to 0.
Feb 18 20:15:48.276 [notice] Opening Socks listener on /run/tor/socks
Feb 18 20:15:48.276 [warn] Bind to /run/tor/socks failed: No such file or directory.
Feb 18 20:15:48.276 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 18 20:15:48.276 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Feb 18 20:15:48.277 [notice] Opening Control listener on 127.0.0.1:9051
Feb 18 20:15:48.277 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051
Feb 18 20:15:48.277 [warn] Directory /run/tor does not exist.
Feb 18 20:15:48.277 [warn] Before Tor can create a control socket in "/run/tor/control", the directory "/run/tor" needs to exist, and to be accessible only by the user and group account that is running Tor.  (On some Unix systems, anybody who can list a socket can connect to it, so Tor is being careful.)
Feb 18 20:15:48.278 [notice] Opening OR listener on 0.0.0.0:9001
Feb 18 20:15:48.278 [notice] Opened OR listener connection (ready) on 0.0.0.0:9001
Feb 18 20:15:48.278 [notice] Closing partially-constructed Socks listener connection (ready) on 127.0.0.1:9050
Feb 18 20:15:48.278 [notice] Closing partially-constructed Control listener connection (ready) on 127.0.0.1:9051
Feb 18 20:15:48.279 [notice] Closing partially-constructed OR listener connection (ready) on 0.0.0.0:9001
Feb 18 20:15:48.279 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Feb 18 20:15:48.280 [err] Reading config failed--see warnings above.
cocolino@battleMini:~ $ sudo mkdir /run/tor && chown debian-tor:debian-tor /run/tor
chown: changing ownership of '/run/tor': Operation not permitted
cocolino@battleMini:~ $ sudo mkdir /run/tor
mkdir: cannot create directory ‘/run/tor’: File exists
cocolino@battleMini:~ $ sudo chown debian-tor:debian-tor /run/tor
cocolino@battleMini:~ $ sudo -u debian-tor /usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0
Feb 18 20:16:20.576 [notice] Tor 0.4.8.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.15, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Feb 18 20:16:20.577 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 18 20:16:20.577 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Feb 18 20:16:20.577 [notice] Read configuration file "/etc/tor/torrc".
Feb 18 20:16:20.591 [notice] Based on detected system memory, MaxMemInQueues is set to 690 MB. You can override this by setting MaxMemInQueues by hand.
Feb 18 20:16:20.591 [notice] By default, Tor does not run as an exit relay. If you want to be an exit relay, set ExitRelay to 1. To suppress this message in the future, set ExitRelay to 0.
Feb 18 20:16:20.603 [notice] Opening Socks listener on /run/tor/socks
Feb 18 20:16:20.604 [notice] Opened Socks listener connection (ready) on /run/tor/socks
Feb 18 20:16:20.605 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 18 20:16:20.605 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Feb 18 20:16:20.605 [notice] Opening Control listener on 127.0.0.1:9051
Feb 18 20:16:20.605 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051
Feb 18 20:16:20.606 [notice] Opening Control listener on /run/tor/control
Feb 18 20:16:20.607 [notice] Opened Control listener connection (ready) on /run/tor/control
Feb 18 20:16:20.607 [notice] Opening OR listener on 0.0.0.0:9001
Feb 18 20:16:20.607 [notice] Opened OR listener connection (ready) on 0.0.0.0:9001
Feb 18 20:16:20.608 [warn] Error setting groups to gid 123: "Operation not permitted".
Feb 18 20:16:20.608 [warn] Tor is already running as debian-tor.  You do not need the "User" option if you are already running as the user you want to be.  (If you did not set the User option in your torrc, check whether it was specified on the command line by a startup script.)
Feb 18 20:16:20.608 [notice] Closing partially-constructed Socks listener connection (ready) on /run/tor/socks
Feb 18 20:16:20.608 [notice] Closing partially-constructed Socks listener connection (ready) on 127.0.0.1:9050
Feb 18 20:16:20.608 [notice] Closing partially-constructed Control listener connection (ready) on 127.0.0.1:9051
Feb 18 20:16:20.609 [notice] Closing partially-constructed Control listener connection (ready) on /run/tor/control
Feb 18 20:16:20.609 [notice] Closing partially-constructed OR listener connection (ready) on 0.0.0.0:9001
Feb 18 20:16:20.610 [warn] Failed to parse/validate config: Problem with User value. See logs for details.
Feb 18 20:16:20.610 [err] Reading config failed--see warnings above.
cocolino@battleMini:~ $ sudo ps aux | grep tor
cocolino   796  0.0  0.6  44216  6400 ?        Ssl  20:14   0:00 /usr/libexec/xdg-permission-store
cocolino   903 14.2  0.1   7532  1792 pts/0    S+   20:17   0:00 grep --color=auto tor

cocolinofan · February 19, 2025, 12:58am

Honestly guys, I am a bit tired.
Do you guys wanna call it quits? Is not a fast relay anyway.
Thank you so much for trying to help

system · February 20, 2025, 12:58am

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