Tor is running in a 6 minute loop

Hello,
I try to install TOR on 32 Bit Raspian “Bookworm”.
If I start by hand
sudo -u debian-tor tor -f /etc/tor/torrc --RunAsDaemon 0
everything is fine. TOR needs 4 minutes for startup and runs well.

But is I use the normal actvation
sudo systemctl enable tor.service
systemctl start tor
TOR is running in a 6 minute loop, will not startup completely.
I try to set a watchdog / timeout … but no success.

1.) The startup needs too long.
2.) After every 6 minutes something caused a restart. Maybe it’s a timeout?
Seems I need assistance.

Best reagards Jens

torrc:

Configuration file for a typical Tor user

SocksPort 0

Log debug file /var/log/tor/debug.log
RunAsDaemon 1
ControlPort 9051
HashedControlPassword xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ORPort 9001
Nickname jens723
ContactInfo js-tor@XXXXXX.de
DirPort 9030
ExitPolicy reject : # no exits allowed
ExitRelay 0

All 6 minutes:

[2a0f:e586:f:f:9491:941d:caf5:50e7]', purpose ‘general’
Jun 04 00:11:37.000 [debug] router_parse_list_from_string(): Read router ‘$03D1EF3EF2BE5145150C58ACC72519DD860E61BA~blackfox [yzKUPOD6SaTKOdSq5Wxbu3ymziKz1Wvf7i/pezejBiM] at 136.243.3.194 and [2a01:4f8:211:1d41::2]’, purpose ‘general’
Jun 04 00:11:37.000 [debug] router_parse_list_from_string(): Read router ‘$2185F7F67ED533CE4AA58C12203CC588671267C7~GeraldClintonC20287 [V1KCxr6/J0ZWw+zWTw2fpmyDTPeH95+jQHu1PVH/l2Q] at 23.92.34.110’, purpose ‘general’
Jun 04 00:11:37.000 [debug] router_parse_list_from_string(): Read router ‘$DE85FE246ED482EA07BCDCF5D769B0ED649817F7~VrijHeid2 [KMRgg/4ZPUwbpykalXI/iZG007hjj2wP/qzjYVXC110] at 94.142.244.16 and [2a02:898:218::1]’, purpose ‘general’
Jun 04 00:11:37.000 [debug] router_parse_list_from_string(): Read router ‘$EEE004ECC3D29D520403471E5B2AF1E05CA91426~ElSalvaTOR [P3GlRQ4ajUOOh5V+ZgQMiSfRCh8WhmnCwcZt3++oCQI] at 193.218.118.88 and [2a0f:e586:f:f::88]’, purpose ‘general’
Jun 04 00:11:38.000 [notice] Tor 0.4.7.16 opening log file.
Jun 04 00:11:38.366 [notice] We compiled with OpenSSL 300000b0: OpenSSL 3.0.11 19 Sep 2023 and we are running with OpenSSL 300000b0: 3.0.11. These two versions should be binary compatible.
Jun 04 00:11:38.660 [notice] Tor 0.4.7.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Jun 04 00:11:38.660 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
Jun 04 00:11:38.660 [notice] Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
Jun 04 00:11:38.660 [notice] Read configuration file “/etc/tor/torrc”.

1 Like

Hey Jens,

Can you give more information about your system, like rpi model, processor, ram?

Do the logs show anything tor related? I think you can type

$ journalctl -g tor

Can you run htop while you start tor? What do you see?

One last thing that’s maybe more important. It looks like you are running tor 0.4.7.16, which is now end of life:

Worth noting, among few minor bug fixes, directory authorities running this version [0.4.8.11] (and above) will automatically start rejecting relays running on version 0.4.7.x which is now end of life.

Can you update tor and try again?

2 Likes

Hello Tangerine,

Raspberry Phi Model B?
https://en.wikipedia.org/wiki/Raspberry_Pi
Should be well known: 1GB RAM, Arm-Cortex A7
Cortex A7: 32Bit, ARM processor.

On the computer is running Raspian 1:6.6.31 (newest, 2024, 29 May), it’s a Debian Linux.
I used the same computer for tor some years ago.

Unfortunately the original raspian TOR package was old (0.4.7.16)) and not longer supported.
Debian don’t offer armhf (32 Bit ARM) packages. So I upload
git clone https://github.com/torproject/tor
the newest tor soruce code version and compile it on the raspberry myself (version 0.4.8.11).
Because this reason the TOR version should be the newest , but not a stable version. In the description I used is written how to upload the source code, but in not written how to upload the last stable source code version.

Sorry, I’m a bloody barbarian.

!!!
But… now I see it myselv: It seems the old 0.4.7.16 version is starting, not the version I uploaded the source code.
Unfortunately I don’t deinstall the original package.
!!!

  • Start by system.d: old unsupported version: 0.4.7.16
  • Start tor by hand it’s up in only 4 minutes and seems running well. Now version 0.4.9.0-alpha-dev is displayed

Thats the difference I was locking for, seems an installation problem.
Maybe it’s a good idea to do it again from the beginning…
Thank you for your help. Hopefully I will get it now.

Jens

···

journalctl -g tor

Jun 06 20:44:54 raspberrypi systemd[1]: Starting tor@default.service - Anonymizing overlay network for TCP…
Jun 06 20:44:54 raspberrypi tor[1899]: Jun 06 20:44:54.883 [notice] Tor 0.4.7.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Jun 06 20:44:54 raspberrypi tor[1899]: Jun 06 20:44:54.887 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Jun 06 20:44:54 raspberrypi tor[1899]: Jun 06 20:44:54.888 [notice] Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
Jun 06 20:44:54 raspberrypi tor[1899]: Jun 06 20:44:54.889 [notice] Read configuration file “/etc/tor/torrc”.
Jun 06 20:44:55 raspberrypi tor[1900]: Jun 06 20:44:55.482 [notice] Tor 0.4.7.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Jun 06 20:44:55 raspberrypi tor[1900]: Jun 06 20:44:55.482 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Jun 06 20:44:55 raspberrypi tor[1900]: Jun 06 20:44:55.482 [notice] Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
Jun 06 20:44:55 raspberrypi tor[1900]: Jun 06 20:44:55.483 [notice] Read configuration file “/etc/tor/torrc”.
Jun 06 20:44:55 raspberrypi tor[1900]: Jun 06 20:44:55.511 [notice] Opening Directory listener on 0.0.0.0:9030
Jun 06 20:44:55 raspberrypi tor[1900]: Jun 06 20:44:55.511 [notice] Opened Directory listener connection (ready) on 0.0.0.0:9030
Jun 06 20:48:30 raspberrypi dbus-daemon[868]: [session uid=1000 pid=868] Activating via systemd: service name=‘org.freedesktop.impl.portal.PermissionStore’ unit=‘xdg-permission-store.service’ requested by ':>
Jun 06 20:48:30 raspberrypi systemd[835]: Starting xdg-permission-store.service - sandboxed app permission store…
Jun 06 20:48:30 raspberrypi dbus-daemon[868]: [session uid=1000 pid=868] Successfully activated service ‘org.freedesktop.impl.portal.PermissionStore’
Jun 06 20:48:30 raspberrypi systemd[835]: Started xdg-permission-store.service - sandboxed app permission store.
Jun 06 20:49:55 raspberrypi systemd[1]: tor@default.service: start operation timed out. Terminating.
Jun 06 20:49:55 raspberrypi systemd[1]: tor@default.service: Failed with result ‘timeout’.
Jun 06 20:49:55 raspberrypi systemd[1]: Failed to start tor@default.service - Anonymizing overlay network for TCP.
Jun 06 20:49:55 raspberrypi systemd[1]: tor@default.service: Consumed 4min 59.975s CPU time.
Jun 06 20:49:55 raspberrypi systemd[1]: tor@default.service: Scheduled restart job, restart counter is at 23.
Jun 06 20:49:55 raspberrypi systemd[1]: Stopped tor@default.service - Anonymizing overlay network for TCP.
Jun 06 20:49:55 raspberrypi systemd[1]: tor@default.service: Consumed 4min 59.975s CPU time.
Jun 06 20:49:55 raspberrypi systemd[1]: Starting tor@default.service - Anonymizing overlay network for TCP…
Jun 06 20:49:55 raspberrypi tor[2021]: Jun 06 20:49:55.871 [notice] Tor 0.4.7.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Jun 06 20:49:55 raspberrypi tor[2021]: Jun 06 20:49:55.871 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Jun 06 20:49:55 raspberrypi tor[2021]: Jun 06 20:49:55.872 [notice] Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
Jun 06 20:49:55 raspberrypi tor[2021]: Jun 06 20:49:55.872 [notice] Read configuration file “/etc/tor/torrc”.
Jun 06 20:49:56 raspberrypi tor[2022]: Jun 06 20:49:56.497 [notice] Tor 0.4.7.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Jun 06 20:49:56 raspberrypi tor[2022]: Jun 06 20:49:56.502 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Jun 06 20:49:56 raspberrypi tor[2022]: Jun 06 20:49:56.504 [notice] Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
Jun 06 20:49:56 raspberrypi tor[2022]: Jun 06 20:49:56.506 [notice] Read configuration file “/etc/tor/torrc”.
Jun 06 20:49:56 raspberrypi tor[2022]: Jun 06 20:49:56.545 [notice] Opening Directory listener on 0.0.0.0:9030
Jun 06 20:49:56 raspberrypi tor[2022]: Jun 06 20:49:56.546 [notice] Opened Directory listener connection (ready) on 0.0.0.0:9030
Jun 06 20:54:56 raspberrypi systemd[1]: tor@default.service: start operation timed out. Terminating.
Jun 06 20:54:56 raspberrypi systemd[1]: tor@default.service: Failed with result ‘timeout’.
Jun 06 20:54:56 raspberrypi systemd[1]: Failed to start tor@default.service - Anonymizing overlay network for TCP.
Jun 06 20:54:56 raspberrypi systemd[1]: tor@default.service: Consumed 5min 329ms CPU time.
Jun 06 20:54:56 raspberrypi systemd[1]: tor@default.service: Scheduled restart job, restart counter is at 24.
Jun 06 20:54:56 raspberrypi systemd[1]: Stopped tor@default.service - Anonymizing overlay network for TCP.
Jun 06 20:54:56 raspberrypi systemd[1]: tor@default.service: Consumed 5min 329ms CPU time.
Jun 06 20:54:56 raspberrypi systemd[1]: Starting tor@default.service - Anonymizing overlay network for TCP…
Jun 06 20:54:56 raspberrypi tor[2040]: Jun 06 20:54:56.878 [notice] Tor 0.4.7.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Jun 06 20:54:56 raspberrypi tor[2040]: Jun 06 20:54:56.878 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Jun 06 20:54:56 raspberrypi tor[2040]: Jun 06 20:54:56.879 [notice] Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
Jun 06 20:54:56 raspberrypi tor[2040]: Jun 06 20:54:56.879 [notice] Read configuration file “/etc/tor/torrc”.
Jun 06 20:54:57 raspberrypi tor[2041]: Jun 06 20:54:57.528 [notice] Tor 0.4.7.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Jun 06 20:54:57 raspberrypi tor[2041]: Jun 06 20:54:57.529 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Jun 06 20:54:57 raspberrypi tor[2041]: Jun 06 20:54:57.529 [notice] Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
Jun 06 20:54:57 raspberrypi tor[2041]: Jun 06 20:54:57.529 [notice] Read configuration file “/etc/tor/torrc”.
Jun 06 20:54:57 raspberrypi tor[2041]: Jun 06 20:54:57.561 [notice] Opening Directory listener on 0.0.0.0:9030
Jun 06 20:54:57 raspberrypi tor[2041]: Jun 06 20:54:57.561 [notice] Opened Directory listener connection (ready) on 0.0.0.0:9030
lines 38300-38354/38354 (END)

May 21 01:27:28 raspberrypi systemd[1]: tor@default.service: Failed with result ‘timeout’.
May 21 01:27:28 raspberrypi systemd[1]: Failed to start tor@default.service - Anonymizing overlay network for TCP.
May 21 01:27:28 raspberrypi systemd[1]: tor@default.service: Consumed 6min 756ms CPU time.
May 21 01:27:28 raspberrypi systemd[1]: tor@default.service: Scheduled restart job, restart counter is at 3.
May 21 01:27:28 raspberrypi systemd[1]: Stopped tor@default.service - Anonymizing overlay network for TCP.
May 21 01:27:28 raspberrypi systemd[1]: tor@default.service: Consumed 6min 756ms CPU time.
May 21 01:27:28 raspberrypi systemd[1]: Starting tor@default.service - Anonymizing overlay network for TCP…
May 21 01:27:29 raspberrypi tor[6629]: May 21 01:27:29.335 [notice] Tor 0.4.7.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
May 21 01:27:29 raspberrypi tor[6629]: May 21 01:27:29.335 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
May 21 01:27:29 raspberrypi tor[6629]: May 21 01:27:29.337 [notice] Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
May 21 01:27:29 raspberrypi tor[6629]: May 21 01:27:29.341 [notice] Read configuration file “/etc/tor/torrc”.

Sorry, I have no idea how to upload a longer logging in this forum.
This “kill” happen exactly all 6 minutes. Operation timeout…

htop
In the first line is written
debian -tor 100%CPU 1.6% Mem
/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0

I’m not sure was the meaning of 100%, the Cortex hat 4 processors.
In the torrc is writen RunaAsdaemon 1. But the call seems =0 - I’m confused.

Best regards Jens

Am 06.06.2024 um 11:56 schrieb Tangerine via Tor Project Forum <noreply@forum.torproject.org>:

| Tangerine
June 6 |

  • | - |

Hey Jens,

Can you give more information about your system, like rpi model, processor, ram?

Do the logs show anything tor related? I think you can type

$ journalctl -g tor

Can you run htop while you start tor? What do you see?

One last thing that’s maybe more important. It looks like you are running tor 0.4.7.16, which is now end of life:

Worth noting, among few minor bug fixes, directory authorities running this version [0.4.8.11] (and above) will automatically start rejecting relays running on version 0.4.7.x which is now end of life.

Can you update tor and try again?


Rufe das Thema auf oder antworte auf diese E-Mail, um zu antworten.

Um diese E-Mails abzubestellen, klicke hier.

2 Likes

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