[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #7799 [Tor]: Tor seems to build+timeout circuits for hours when offline/idle (was: remove (or scale down a level) obnoxious "No circuits are opened. Relaxed timeout for a circuit with channel state open to 60000ms. However, it appears the circuit has timed out anyway. 0 guards are live." message)
#7799: Tor seems to build+timeout circuits for hours when offline/idle
--------------------+-------------------------------------------------------
Reporter: mr-4 | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Tor: 0.2.4.x-final
Component: Tor | Version: Tor: 0.2.4.7-alpha
Keywords: | Parent:
Points: | Actualpoints:
--------------------+-------------------------------------------------------
Old description:
> Since I've upgraded to .7-alpha I am having my log file filled with the
> above message, which is generated a couple of times a *second*!
>
> I have, so far, accumulated over 14,000 lines with this crap, which seems
> to be generated when tor was left idle (unused) overnight. I had to
> increase my log level (to "warn") in order to get rid of it temporarily,
> but that isn't good enough, since I cannot see my other (very useful)
> messages appearing at that level (notice) without having my log filled
> rapidly.
New description:
Since I've upgraded to .7-alpha I am having my log file filled with the
above message, which is generated a couple of times a *second*!
\
I have, so far, accumulated over 14,000 lines with this crap, which seems
to be generated when tor was left idle (unused) overnight. I had to
increase my log level (to "warn") in order to get rid of it temporarily,
but that isn't good enough, since I cannot see my other (very useful)
messages appearing at that level (notice) without having my log filled
rapidly.
Here's the logline from the original bug title:
"No circuits are opened. Relaxed timeout for a circuit with channel state
open to 60000ms. However, it appears the circuit has timed out anyway. 0
guards are live."
--
Comment(by mikeperry):
Hrmm.. The bug submitter seems to be hitting the rageahol a little too
hard this holiday season. A little investigation reveals a few things are
incorrect in the bug report's description.
First: The reported logline is info level, not notice. It's possible that
the notice line was *also* triggered, but that's not immediately clear
based on the situation description.
Second: I strongly suspect that Tor wasn't idle, but was actually
disconnected from the network. This is probably the real bug+repro case
here.
So the remaining question is: Does this actually happen for idle clients
as reported, or do they have to be disconnected from the network in
addition/instead?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7799#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs