Assertion fast_memeq(md->body, "onion-key", 9) failed;
I am running Tor v0.2.4.6-alpha (git-b13c6becc892d971) running on Linux with Libevent 1.4.13-stable and OpenSSL 0.9.8o.
The system is running i686 debian linux 2.6.38.2 with some grsec patches applied.
Tor crashed with the following message in the console:
==== console [... cut... ] [notice] Opening Directory listener on 0.0.0.0:3128
src/or/microdesc.c:492 microdesc_cache_rebuild: Assertion fast_memeq(md->body, "onion-key", 9) failed; aborting. Aborted. ==== // end of console
==== /var/log/tor/log from just before: Jan 17 23:44:09.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [50 similar message(s) suppressed in last 60 seconds] Jan 17 23:45:09.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [184 similar message(s) suppressed in last 60 seconds] Jan 17 23:46:09.000 [warn] Your computer i ==== // end of /var/log/tor/log (it ends abruptly)
The log is big (17M) and dates a year or so back. Looking through it now, I discovered that it routinely complained about things such as:
Jan 04 09:04:31.000 [warn] Failing because we have 1016 connections already. Please raise your ulimit -n. [272740629 similar message(s) suppressed in last 21600 seconds] Jan 04 09:48:12.000 [warn] Cannot seed RNG -- no entropy source found. Jan 04 09:55:16.000 [warn] Couldn't open "/var/lib/tor2/state.tmp" (/var/lib/tor2/state) for writing: Too many open files Jan 04 09:55:16.000 [warn] Unable to write state to file "/var/lib/tor2/state"; will try again later
This feels like mismanagement on my part, but the console didn't say anything about it, so I never checked the logs before. It was running in a chroot and I must have forgotten to give it read permission for the chrooted /dev/{u,}random. I hope this has nothing to do with the bug, but maybe a new change request should be added to write messages like that on the console?
I am available on irc as "sadoper" if you need further information.