server or could it be an error with the consensus
network status document?
-Stephan
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
cting INTRODUCE1 on non-OR or non-edge
circuit 2147497125.
I updated to Tor 0.2.4.21 (git-c5a648cc6f218339) on Debian three days
ago after heartbleed. My old versions 0.2.4.x didn't show that message
before.
-Stephan
___
tor-relays mailing list
numbers. ;-)
-Stephan
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
email. If
something is seriously broken with my server (or tor) five mails will
suffice. Even if I am on vacation for a few weeks, I don't need a
reminder every 20 minutes. ;-)
-Stephan
___
tor-relays mailing list
tor-relays@lists.torproject.org
figured monit not to restart tor until at least three consecutive
TCP checks failed. Now I still get the warnings for failed checks from
time to time (maybe under high load?) but tor seems to run stable.
-Stephan
___
tor-relays mai
being overloaded is/was true,
because my non-exit relay got a similar message at that time.
Strange thing though: my relay only used about half of it's bandwidth at
the time.
-Stephan
___
tor-relays mailing list
tor-relays@lists.torproject.org