-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi,
My relay is running on Raspberry OS so the updates are a little late for some packages, so my relay is running on obsolote version 0.3.5.15, I installed Tor from source and tor --version gives me Tor version 0.4.6.10.
Tor is running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Glibc 2.28 as libc.
Tor compiled with GCC version 8.3.0but tor@default.service is still running on 0.3.5.15 (I have restarted the service multiple times)...
Regards,
Daniel Nikoloski
Sent with ProtonMail Secure Email.
On Thursday, February 10, 2022 9:19:03 AM CET Dan via tor-relays wrote:
My relay is running on Raspberry OS so the updates are a little late for some packages, so my relay is running on obsolote version 0.3.5.15, I installed Tor from source and tor --version gives me Tor version 0.4.6.10.
Tor is running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Glibc 2.28 as libc.
Tor compiled with GCC version 8.3.0but tor@default.service is still running on 0.3.5.15 (I have restarted the service multiple times)...
If you previously installed tor with your package management system, then you now have 2x tor, once default '/usr/bin/tor' and once compiled yourself '/usr/ local/bin/tor' or somewhere. Did you uninstall the 'default' (installed with apt) tor daemon first?
Remove removes the application, but leaves the system configuration files, purge also deletes system configuration files and your tor keys! apt remove tor apt purge tor
Reminder, don't forget the autostart scripts after compiling.
Hi Daniel,
On 2/10/22 09:19, Dan via tor-relays wrote: [..]
Tor compiled with GCC version 8.3.0but tor@default.service is still running on 0.3.5.15 (I have restarted the service multiple times)...
Please show us the output of 'systemctl cat tor@defailt.service' and 'which tor'.
I assume you need to adjust the path in your unit file.
-- Martin
tor-relays@lists.torproject.org