[tor-bugs] #27228 [Core Tor/Tor]: pathbias_should_count(): Bug: Circuit X is now being counted

[Tor Bug Tracker & Wiki]

#27228: pathbias_should_count(): Bug: Circuit X is now being counted
--------------------------+-----------------------------------
 Reporter:  traumschule   |          Owner:  (none)
     Type:  defect        |         Status:  needs_information
 Priority:  Medium        |      Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |        Version:  Tor: unspecified
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+-----------------------------------

Comment (by traumschule):

 > One of related bugs you linked can happen with a Tor controller is
 launching circuits. Were you using any Tor controller
 No, neither nyx, [https://fscked.org/projects/torctl TorCtl] nor Tor
 Launcher.

 Going through todays log, the disappearance of above bug since 3:30 could
 be related to closing the OR port:
 {{{
 Aug 21 01:27:39.000 [notice] {NET} Opening OR listener on 127.0.0.1:9090
 Aug 21 01:27:39.000 [notice] {NET} Closing no-longer-configured OR
 listener on 0.0.0.0:443
 Aug 21 01:27:39.000 [notice] Tor 0.3.5.0-alpha-dev opening log file.
 Aug 21 01:27:39.000 [notice] {NET} Closing old OR listener on 0.0.0.0:443
 Aug 21 03:29:26.000 [notice] {NET} Opening Extended OR listener on
 127.0.0.1:0
 Aug 21 03:29:26.000 [notice] {NET} Extended OR listener listening on port
 40481.
 Aug 21 03:29:26.000 [notice] Tor 0.3.5.0-alpha-dev opening log file.
 Aug 21 03:45:23.000 [notice] {NET} Closing no-longer-configured Extended
 OR listener on 127.0.0.1:40481
 Aug 21 03:45:23.000 [notice] {NET} Closing no-longer-configured OR
 listener on 127.0.0.1:9090
 Aug 21 03:45:23.000 [notice] Tor 0.3.5.0-alpha-dev opening log file.
 Aug 21 03:45:23.000 [notice] {NET} Closing old Extended OR listener on
 127.0.0.1:40481
 Aug 21 03:45:23.000 [notice] {NET} Closing old OR listener on
 127.0.0.1:9090

 Aug 21 22:49:09.000 [notice] {HEARTBEAT} Heartbeat: Tor's uptime is 23:59
 hours
 Aug 21 23:07:39.000 [notice] {CIRC} Your network connection speed appears
 to have changed. Resetting timeout to 60s after 18 timeouts and 1000
 buildtimes.
 Aug 22 00:21:23.000 [notice] {GENERAL} Received reload signal (hup).
 Reloading config and resetting internal state.
 Aug 22 00:21:24.000 [notice] {CONFIG} Read configuration file
 "/usr/share/tor/tor-service-defaults-torrc".
 Aug 22 00:21:24.000 [notice] {CONFIG} Read configuration file
 "/etc/tor/torrc".
 }}}
 The last reload surprised me because I did not trigger it. Is there some
 kind of mechanism to automatically reload if torrc if it has changed?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27228#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online