Hello,
Happy New Year, everone! I've been chasing this down here for the last hour or so and I thought I might as well share it since others might also experience it.
I am running https://atlas.torproject.org/#search/plutonium
After running yum update this lead to a different fingerprint being generated for the same host.
Nov 29 01:09:27 Installed: tor-0.2.5.10-tor.2.rh6_5.i686
Dec 29 19:21:07 Installed: torsocks-2.0.0-2.el6.i686
Dec 29 19:21:10 Updated: tor-0.2.5.10-1.el6.i686
Then, traffic collapsed by going down from <> 8MB/sec to pretty much nothing.
I checked the logs and found permission errors. The group for Tor was changed from _tor to toranon, so the permissions were wrong after the rpm was installed.
Also, /etc/tor/torrc had this line commented :
## The directory for keeping all the keys/etc. By default, we store ## things in $HOME/.tor on Unix, and in Application Data\tor on Windows. DataDirectory /var/lib/tor
So it was defaulting to ~tor directory,
tor/tor.log-20141230:Dec 30 03:13:01.000 [warn] Default DataDirectory is "~/.tor". This expands to "/.tor", which is probably not what you want. Using "/var/tor" instead
[root@plutonium log]# rpm -qa | grep tor torsocks-2.0.0-2.el6.i686 tor-0.2.5.10-1.el6.i686 [root@plutonium log]#
Dec 29 17:56:47.000 [notice] Heartbeat: Tor's uptime is 25 days 0:00 hours, with 1885 circuits open. I've sent 6843.34 GB and received 6761.80 GB. Dec 29 17:56:47.000 [notice] Average packaged cell fullness: 97.313% Dec 29 17:56:47.000 [notice] TLS write overhead: 2% Dec 29 17:56:47.000 [notice] Circuit handshake stats since last time: 16007/16007 TAP, 49264/49264 NTor. Dec 29 20:07:10.000 [warn] Couldn't open "/var/lib/tor/cached-microdesc-consensus.tmp" (/var/lib/tor/cached-microdesc-consensus) for writing: Permission denied Dec 29 20:07:10.000 [warn] Couldn't open "/var/lib/tor/cached-microdescs.new" (/var/lib/tor/cached-microdescs.new) for writing: Permission denied Dec 29 20:07:10.000 [warn] Couldn't append to journal in /var/lib/tor/cached-microdescs.new: Permission denied Dec 29 20:07:11.000 [warn] Couldn't open "/var/lib/tor/cached-microdescs.new" (/var/lib/tor/cached-microdescs.new) for writing: Permission denied Dec 29 20:07:11.000 [warn] Couldn't append to journal in /var/lib/tor/cached-microdescs.new: Permission denied Dec 29 20:08:10.000 [warn] Couldn't open "/var/lib/tor/cached-microdescs.new" (/var/lib/tor/cached-microdescs.new) for writing: Permission denied Dec 29 20:08:10.000 [warn] Couldn't append to journal in /var/lib/tor/cached-microdescs.new: Permission denied Dec 29 20:08:10.000 [warn] Couldn't open "/var/lib/tor/cached-microdescs.new" (/var/lib/tor/cached-microdescs.new) for writing: Permission denied Dec 29 20:08:10.000 [warn] Couldn't append to journal in /var/lib/tor/cached-microdescs.new: Permission denied Dec 29 20:09:11.000 [warn] Couldn't open "/var/lib/tor/cached-microdescs.new" (/var/lib/tor/cached-microdescs.new) for writing: Permission denied Dec 29 20:09:11.000 [warn] Couldn't append to journal in /var/lib/tor/cached-microdescs.new: Permission denied Dec 29 20:09:11.000 [warn] Couldn't open "/var/lib/tor/cached-microdescs.new" (/var/lib/tor/cached-microdescs.new) for writing: Permission denied Dec 29 20:09:11.000 [warn] Couldn't append to journal in /var/lib/tor/cached-microdescs.new: Permission denied Dec 29 20:29:31.000 [warn] Couldn't open "/var/lib/tor/cached-consensus.tmp" (/var/lib/tor/cached-consensus) for writing: Permission denied Dec 29 20:29:32.000 [warn] Couldn't open "/var/lib/tor/cached-descriptors.new" (/var/lib/tor/cached-descriptors.new) for writing: Permission denied Dec 29 20:29:32.000 [warn] Unable to store router descriptor
I fixed the permissions, but I am seeing this message now that I have not seen before.
Jan 1 21:36:02 p15186978 Tor[28986]: Invalid result from curve25519 handshake: 4 Jan 1 21:36:02 p15186978 Tor[28986]: onion_skin_client_handshake failed. Jan 1 21:36:02 p15186978 Tor[28986]: circuit_finish_handshake failed. Jan 1 21:36:02 p15186978 Tor[28986]: connection_edge_process_relay_cell (at origin) failed. Jan 1 21:36:04 p15186978 Tor[28986]: Performing bandwidth self-test...done.
Should I be concerned about this message?
[root@plutonium etc]# uname -a Linux plutonium 2.6.32-431.el6.i686 #1 SMP Fri Nov 22 00:26:36 UTC 2013 i686 i686 i386 GNU/Linux [root@plutonium etc]# cat /etc/redhat-release CentOS release 6.6 (Final) [root@plutonium etc]#
Thanks,
Sascha.
tor-0.2.5.10-tor.2.rh6_5.i686 is from the Tor repo tor-0.2.5.10-1.el6.i686 is from epel
Different repos often package the same program differently. yum-plugin-priorities, manually enabling repos as needed, or placing excludes in the yum config files must be used to avoid switching between repos unexpectedly.
-Pascal
On 1/1/2015 2:58 PM, Sascha Siekmann wrote:
Hello,
Happy New Year, everone! I've been chasing this down here for the last hour or so and I thought I might as well share it since others might also experience it.
I am running https://atlas.torproject.org/#search/plutonium
After running yum update this lead to a different fingerprint being generated for the same host.
Nov 29 01:09:27 Installed: tor-0.2.5.10-tor.2.rh6_5.i686
Dec 29 19:21:07 Installed: torsocks-2.0.0-2.el6.i686
Dec 29 19:21:10 Updated: tor-0.2.5.10-1.el6.i686
Then, traffic collapsed by going down from <> 8MB/sec to pretty much nothing.
tor-relays@lists.torproject.org