Skip to main content ↑ ↓
Topic: [SOLVED] tor daemon won't start after recent udpate (Read 628 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[SOLVED] tor daemon won't start after recent udpate

Hi all. I recently ran an update and after rebooting my system, I noticed the tor daemon won't start, throwing an error message:

Code: [Select]
tor: symbol lookup error: tor: undefined symbol: evutil_secure_secure_rng_add_bytes

I have tried looking up how to resolve this issue, but most posts regarding this issue are over 5 years old and I don't want to downgrade any packages that I don't need to.

Here are the related update logs from /var/log/pacman.log

Code: [Select]
[2022-11-01T15:15:41-0700] [PACMAN] Running 'pacman -Syu'
[2022-11-01T15:15:41-0700] [PACMAN] synchronizing package lists
[2022-11-01T15:16:01-0700] [PACMAN] starting full system upgrade
[2022-11-01T15:16:37-0700] [ALPM] transaction started
[2022-11-01T15:16:37-0700] [ALPM] upgraded libsysprof-capture (3.44.0-2 -> 3.46.0-1)
[2022-11-01T15:16:37-0700] [ALPM] upgraded readline (8.2.0-1 -> 8.2.001-1)
[2022-11-01T15:16:37-0700] [ALPM] upgraded adwaita-icon-theme (42.0+r1+gc144c3d75-1 -> 43-1)
[2022-11-01T15:16:37-0700] [ALPM] upgraded libcloudproviders (0.3.1-2 -> 0.3.1+r8+g3a229ee-1)
[2022-11-01T15:16:37-0700] [ALPM] upgraded libevent (2.1.12-1 -> 2.1.12-2)
[2022-11-01T15:16:37-0700] [ALPM] upgraded libidn2 (2.3.3-1 -> 2.3.4-1)
[2022-11-01T15:16:37-0700] [ALPM] upgraded gsettings-desktop-schemas (42.0-1 -> 43.0-1)
[2022-11-01T15:16:37-0700] [ALPM] upgraded gcr (3.41.1-2 -> 3.41.1-3)
[2022-11-01T15:16:37-0700] [ALPM] installed geocode-glib-common (3.26.4-2)
[2022-11-01T15:16:37-0700] [ALPM] upgraded geocode-glib (3.26.4-1 -> 3.26.4-2)
[2022-11-01T15:16:37-0700] [ALPM] upgraded graphviz (6.0.2-1 -> 7.0.0-1)
[2022-11-01T15:16:37-0700] [ALPM] upgraded highway (1.0.1-1 -> 1.0.2-1)
[2022-11-01T15:16:37-0700] [ALPM] upgraded irssi (1.4.2-2 -> 1.4.3-1)
[2022-11-01T15:16:38-0700] [ALPM] upgraded lib32-libgpg-error (1.45-1 -> 1.46-1)
[2022-11-01T15:16:38-0700] [ALPM] upgraded lib32-libidn2 (2.3.3-1 -> 2.3.4-1)
[2022-11-01T15:16:38-0700] [ALPM] upgraded lib32-libpciaccess (0.16-1 -> 0.17-1)
[2022-11-01T15:16:38-0700] [ALPM] upgraded lib32-libxau (1.0.9-2 -> 1.0.10-1)
[2022-11-01T15:16:38-0700] [ALPM] upgraded lib32-libxext (1.3.4-2 -> 1.3.5-1)
[2022-11-01T15:16:38-0700] [ALPM] upgraded lib32-libxshmfence (1.3-2 -> 1.3.1-1)
[2022-11-01T15:16:38-0700] [ALPM] upgraded lib32-libxxf86vm (1.1.4-3 -> 1.1.5-1)
[2022-11-01T15:16:38-0700] [ALPM] upgraded lib32-sqlite (3.39.3-1 -> 3.39.4-1)
[2022-11-01T15:16:38-0700] [ALPM] upgraded libgovirt (2:0.3.8-1 -> 2:0.3.9-1)
[2022-11-01T15:16:38-0700] [ALPM] upgraded libmspack (1:0.10.1alpha-3.1 -> 1:0.10.1alpha-4)
[2022-11-01T15:16:38-0700] [ALPM] upgraded libosinfo (1.10.0-1 -> 1.10.0-2)
[2022-11-01T15:16:38-0700] [ALPM] upgraded ntfs-3g (2022.5.17-1 -> 2022.10.3-1)
[2022-11-01T15:16:38-0700] [ALPM] upgraded phodav (2.5-2 -> 3.0-1)
[2022-11-01T15:16:38-0700] [ALPM] warning: directory permissions differ on /etc/polkit-1/rules.d/
filesystem: 750  package: 700
[2022-11-01T15:16:38-0700] [ALPM] warning: directory permissions differ on /usr/share/polkit-1/rules.d/
filesystem: 750  package: 755
[2022-11-01T15:16:38-0700] [ALPM] upgraded polkit (121-1 -> 122-1)
[2022-11-01T15:16:38-0700] [ALPM] upgraded protobuf (21.7-1 -> 21.9-1)
[2022-11-01T15:16:38-0700] [ALPM] upgraded python-protobuf (21.7-1 -> 21.9-1)
[2022-11-01T15:16:38-0700] [ALPM] upgraded spice-gtk (0.41-3 -> 0.41-4.1)
[2022-11-01T15:16:38-0700] [ALPM] upgraded virt-viewer (11.0-1 -> 11.0-2)
[2022-11-01T15:16:38-0700] [ALPM] upgraded yelp-tools (42.0-1 -> 42.1-1)
[2022-11-01T15:16:38-0700] [ALPM] transaction completed
[2022-11-01T15:16:38-0700] [ALPM] running '20-sysusers.hook'...
[2022-11-01T15:16:38-0700] [ALPM] running '30-update-mime-database.hook'...
[2022-11-01T15:16:38-0700] [ALPM] running 'detect-old-perl-modules.hook'...
[2022-11-01T15:16:38-0700] [ALPM-SCRIPTLET] error: No package owns /usr/lib/perl5/5.34
[2022-11-01T15:16:39-0700] [ALPM-SCRIPTLET] WARNING: 2 file(s) in /usr/lib/perl5/5.34 are not tracked by pacman and need to be rebuilt.
[2022-11-01T15:16:39-0700] [ALPM-SCRIPTLET]  -> These were most likely installed directly by cpan or a similar tool.
[2022-11-01T15:16:39-0700] [ALPM-SCRIPTLET]     Run the following command to get a list of these files:
[2022-11-01T15:16:39-0700] [ALPM-SCRIPTLET]     LC_ALL=C find "/usr/lib/perl5/5.34" -type f -exec pacman -Qqo {} + |& sed -n 's/^error: No package owns \(.*\)$/\1/p'
[2022-11-01T15:16:39-0700] [ALPM] running 'glib-compile-schemas.hook'...
[2022-11-01T15:16:39-0700] [ALPM] running 'gtk-update-icon-cache.hook'...
[2022-11-01T15:16:39-0700] [ALPM] running 'mandb-update.hook'...
[2022-11-01T15:16:49-0700] [ALPM] running 'texinfo-install.hook'...
[2022-11-01T15:16:49-0700] [ALPM] running 'update-desktop-database.hook'...

If anyone has any idea about how to troubleshoot this issue, I'd greatly appreciate the help. And thanks for taking a look.

EDIT: I found this recent related post over at the arch forums, apparently libevent might be related to this: https://bbs.archlinux32.org/viewtopic.php?id=3259

I thought I might just be able to downgrade libevent, but it seems there is no older version in the system repos? Again, any help/insight would be appreciated.

Re: tor daemon won't start after recent udpate

Reply #1 –
Hi, I too have the exact same problem.

There are two temporary solutions I see to this.

The one that I am currently using involves using the tor browser itself, just let it connect and then find out on what IP and port it's listening on using the command ss -alnp | grep tor and then route whatever you want through it.

The second solution is to download the source code to the tor daemon itself, compile and install it locally to /usr/local, although since this problem is related to an external library, I don't know if this solution will produce the exact same error and I haven't tried it out.

Re: tor daemon won't start after recent udpate

Reply #2 –
UPDATE: so I tried the second solution mentioned in the above post and it worked without a problem, you can run the /usr/local tor daemon like this for now until the one in the repos gets fixed.

Also remember to change the command that the service file of your chosen init uses to launch the tor daemon and change it, example for OpenRC:
Code: [Select]
command=/usr/bin/tor ----> command=/usr/local/bin/tor

Re: tor daemon won't start after recent udpate

Reply #3 –
Quote from: Lancia – on
UPDATE: so I tried the second solution mentioned in the above post and it worked without a problem, you can run the /usr/local tor daemon like this for now until the one in the repos gets fixed.

Also remember to change the command that the service file of you chosen init uses to launch the tor daemon and change it, example for OpenRC:
Code: [Select]
command=/usr/bin/tor ----> command=/usr/local/bin/tor


Thank you. I will be doing this until this is addressed upstream. I really appreciate your insight here.

Re: tor daemon won't start after recent udpate

Reply #5 –
I kicked off a rebuild of tor. I'm not really sure how this symbol went missing since libevent hasn't updated its version in a long time.
 

Re: tor daemon won't start after recent udpate

Reply #6 –
Quote from: Dudemanguy – on
I kicked off a rebuild of tor. I'm not really sure how this symbol went missing since libevent hasn't updated its version in a long time.

Yes, I noticed I didn't have a previous version of libevent cached in my usual /var/cache/pacman/pkg directory. Thanks for issuing the rebuild, I just installed it and it's working as expected.

I appreciate all the help as per usual! Thanks!