[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #16697 [Tor]: set_max_file_descriptors() failures after upgrade to Tor v0.2.7.2-alpha
#16697: set_max_file_descriptors() failures after upgrade to Tor v0.2.7.2-alpha
------------------------+------------------------------------
Reporter: fk | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor | Version: Tor: 0.2.7.2-alpha
Keywords: regression | Actual Points:
Parent ID: | Points:
------------------------+------------------------------------
After upgrading Tor from v0.2.7.1-alpha to v0.2.7.2-alpha I get a new
warning message:
{{{
Jul 30 16:47:24.820 [notice] Tor 0.2.7.2-alpha (git-36c0ae6f7834af16)
opening log file.
Jul 30 16:47:24.821 [notice] {ACCT} Configured hibernation. This interval
began at 2015-07-30 07:00:00; the scheduled wake-up time was 2015-07-30
07:00:00; we expect to exhaust our quota for this interval around
2015-07-31 07:00:00; the next interval begins at 2015-07-31 07:00:00 (all
times local)
Jul 30 16:47:25.033 [warn] {CONFIG} ConnLimit must be at least 32.
Failing.
Jul 30 16:48:00.749 [notice] {CONTROL} New control connection opened from
127.0.1.5.
Jul 30 16:48:00.808 [warn] {CONFIG} ConnLimit must be at least 32.
Failing.
}}}
With the attached patch the warning is:
{{{
[warn] {CONFIG} ConnLimit must be at least 32 but is 0. Failing.
}}}
The torrcs do not contain a ConnLimit directive and adding one doesn't
seem to make a difference.
Sending SIGHUP or (re-)connecting to the ControlPort results in a new
warning.
So far I'm reproducible getting the warning on a relay and on a hidden
service but not on a pure client.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16697>
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