[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #20963 [Core Tor/Tor]: [notice] The Tor Directory Consensus has changed how many circuits we must track to detect network failures from 0 to 20.
#20963: [notice] The Tor Directory Consensus has changed how many circuits we must
track to detect network failures from 0 to 20.
------------------------------+--------------------------
Reporter: arma | Owner:
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Core Tor/Tor | Version: Tor: 0.2.8.9
Severity: Normal | Keywords:
Actual Points: | Parent ID:
Points: | Reviewer:
Sponsor: |
------------------------------+--------------------------
Running Tor 0.2.8.9 under Yawning's sandboxed-tor-browser, I got this
strange log message:
{{{
2016/12/13 15:48:04 tor: Dec 13 20:48:04.000 [notice] The Tor Directory
Consensus has changed how many circuits we must track to detect network
failures from 0 to 20.
}}}
I haven't seen it before. Also, my system ran out of disk space for a
while before this notice came up.
A) I don't think the consensus changed its parameter here, so it's weird
that my Tor thinks it did. 20 is the default:
{{{
or.h:#define CBT_DEFAULT_RECENT_CIRCUITS 20
}}}
So where did 0 come from?
B) If "A" remains a mystery, we should make sure there isn't some
underlying bug where for example Tor starts ignoring things in the
consensus after an event like
{{{
2016/12/13 13:48:04 tor: Dec 13 18:48:04.000 [warn] Error writing to
"/home/amnesia/tor/data/cached-microdesc-consensus": No space left on
device
}}}
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20963>
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