[tor-bugs] #7194 [Tor]: Tor fails to build circuits hours after daemon initialization (12+ hours)

[Tor Bug Tracker & Wiki]

#7194: Tor fails to build circuits hours after daemon initialization (12+ hours)
---------------------------------+------------------------------------------
    Reporter:  cypherpunks       |        Type:  defect    
      Status:  new               |    Priority:  normal    
   Milestone:                    |   Component:  Tor       
     Version:  Tor: 0.2.3.22-rc  |    Keywords:  tor-client
      Parent:                    |      Points:            
Actualpoints:                    |  
---------------------------------+------------------------------------------

Comment(by Larkdg):

 Replying to [comment:9 cypherpunks]:
 > Replying to [comment:5 arma]:
 > > Is this repeatable? If so, does it happen when you use a vanilla torrc
 too?
 > >
 > > The logs (at that log level) don't tell me much.
 >
 > I haven't engaged in testing with a default config. I'll try to test
 those conditions over the weekend.
 >
 > I can report this much. This fail to build circuit bug was present in
 0.2.2.xx series, but rarely would appear (maybe once every 2+ weeks of
 uptime) under my torrc config. When the bug did appear, tor would fail to
 build circuits for a few hours, but would eventually recover and start
 building again.  Under 0.2.3.22-rc, usually after 12+ hours this bug
 appears, tor fails to build circuits, but never recovers. Restarting the
 daemon results in circuits building immediately, but this is a workaround.


 {{{
 Oct 25 19:54:17.000 [notice] Learned fingerprint
 449B6B579516A0C3E3E4D7C0161A6114C6719141 for bridge 95.222.71.31:443
 Oct 25 19:54:17.000 [notice] Learned fingerprint
 2A22F530A4C1F0CA01D9596E8109CD2D9BB18861 for bridge 108.0.130.119:443
 Oct 25 19:54:17.000 [notice] Learned fingerprint
 763666CD8B577176EDFD5C633CC26F6909458288 for bridge 37.235.49.14:443
 Oct 25 19:54:17.000 [notice] new bridge descriptor 'ec2bridger71690739'
 (fresh): $38CED087E64C196CFFAB9B6B09E9543015719FB6~ec2bridger71690739 at
 46.5$
 Oct 25 19:54:17.000 [notice] new bridge descriptor 'Unnamed' (fresh):
 $7E58563BF387EE4FC1AFC7E89D18930A9600E567~Unnamed at 37.247.49.206
 Oct 25 19:54:17.000 [notice] Bridge 'torbridge42' has both an IPv4 and an
 IPv6 address.  Will prefer using its IPv4 address (85.214.131.213:443).
 Oct 25 19:54:17.000 [notice] new bridge descriptor 'torbridge42' (fresh):
 $9459581B2DA5458D19790C28918CB544B3854C8A~torbridge42 at 85.214.131.213
 Oct 25 20:09:23.000 [notice] new bridge descriptor 'gp39ftk' (fresh):
 $449B6B579516A0C3E3E4D7C0161A6114C6719141~gp39ftk at 95.222.71.31
 Oct 25 20:54:28.000 [notice] Bridge 'torbridge42' has both an IPv4 and an
 IPv6 address.  Will prefer using its IPv4 address (85.214.131.213:443).
 Oct 25 20:54:28.000 [notice] new bridge descriptor 'torbridge42' (fresh):
 $9459581B2DA5458D19790C28918CB544B3854C8A~torbridge42 at 85.214.131.213
 Oct 25 21:09:21.000 [notice] new bridge descriptor 'ec2bridger71690739'
 (fresh): $38CED087E64C196CFFAB9B6B09E9543015719FB6~ec2bridger71690739 at
 46.5$
 Oct 25 21:09:22.000 [notice] new bridge descriptor 'Unnamed' (fresh):
 $7E58563BF387EE4FC1AFC7E89D18930A9600E567~Unnamed at 37.247.49.206
 Oct 25 21:39:25.000 [notice] new bridge descriptor 'gp39ftk' (fresh):
 $449B6B579516A0C3E3E4D7C0161A6114C6719141~gp39ftk at 95.222.71.31
 Oct 25 21:48:03.000 [notice] Heartbeat: Tor's uptime is 12:00 hours, with
 3 circuits open. I've sent 9.99 MB and received 43.45 MB.
 Oct 25 22:10:19.000 [notice] no known bridge descriptors running yet;
 stalling
 Oct 25 22:10:19.000 [notice] Our directory information is no longer up-to-
 date enough to build circuits: No live bridge descriptors.
 Oct 25 22:10:20.000 [notice] no known bridge descriptors running yet;
 stalling
 Oct 25 22:10:26.000 [notice] no known bridge descriptors running yet;
 stalling
 Oct 25 22:15:00.000 [notice] no known bridge descriptors running yet;
 stalling
 Oct 25 22:15:05.000 [notice] no known bridge descriptors running yet;
 stalling
 Oct 25 22:15:15.000 [notice] no known bridge descriptors running yet;
 stalling
 Oct 25 22:15:51.000 [notice] no known bridge descriptors running yet;
 stalling
 Oct 25 22:26:29.000 [notice] no known bridge descriptors running yet;
 stalling
 Oct 25 22:28:31.000 [notice] no known bridge descriptors running yet;
 stalling
 Oct 25 22:42:45.000 [notice] no known bridge descriptors running yet;
 stalling
 Oct 25 22:45:48.000 [notice] no known bridge descriptors running yet;
 stalling
 Oct 25 22:46:49.000 [notice] no known bridge descriptors running yet;
 stalling
 Oct 25 22:51:54.000 [notice] no known bridge descriptors running yet;
 stalling
 Oct 25 22:55:58.000 [notice] no known bridge descriptors running yet;
 stalling
 Oct 25 23:02:04.000 [notice] no known bridge descriptors running yet;
 stalling
 Oct 25 23:07:16.000 [notice] Interrupt: exiting cleanly.
 }}}


 I concur with 2.2.22-rc as above happening on a Debian/testing/amd64
 [vanilla torrc] and with a SIGHUP via arm-tor seemed to rebuild circuits
 again. (Will try to monitor this closer than ever before ... I don't like
 this bug! ;)

 [Selfnote: Updating bridges manually from https://bridges.torproject.org/
 in Vidalia, removing older bridges (24-48hours old) with newer givens ...
 bridge monitoring (with tor--arm) has seemed to greatly improve relaying
 under this configuration. No stalling since Oct 25th.]

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