[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #24813 [- Select a component]: Our directory information is no longer up-to-date



#24813: Our directory information is no longer up-to-date
--------------------------------------+--------------------------
     Reporter:  cstest                |      Owner:  (none)
         Type:  defect                |     Status:  new
     Priority:  Medium                |  Milestone:
    Component:  - Select a component  |    Version:  Tor: 0.3.1.9
     Severity:  Normal                |   Keywords:
Actual Points:                        |  Parent ID:
       Points:                        |   Reviewer:
      Sponsor:                        |
--------------------------------------+--------------------------
 Jan 06 16:22:12.000 [notice] Received reload signal (hup). Reloading
 config and resetting internal state.
 Jan 06 16:22:12.000 [notice] Read configuration file "/etc/tor/tor2.cfg".
 Jan 06 16:22:12.000 [notice] Tor 0.3.1.9 (git-df96a13e9155c7bf) opening
 log file.
 Jan 06 16:26:09.000 [notice] Received reload signal (hup). Reloading
 config and resetting internal state.
 Jan 06 16:26:09.000 [notice] Read configuration file "/etc/tor/tor2.cfg".
 Jan 06 16:26:09.000 [notice] Tor 0.3.1.9 (git-df96a13e9155c7bf) opening
 log file.
 Jan 06 16:28:01.000 [notice] Our directory information is no longer up-to-
 date enough to build circuits: We're missing descriptors for some of our
 primary entry guards
 Jan 06 16:28:01.000 [notice] I learned some more directory information,
 but not enough to build a circuit: We're missing descriptors for some of
 our primary entry guards
 Jan 06 16:28:01.000 [warn] Requested exit point
 '$D885444EED4522249A1BD29A250E612889C451F8' is not known. Closing.
 Jan 06 16:28:11.000 [warn] Giving up launching first hop of circuit to
 rendezvous point ..........
 Jan 06 16:28:11.000 [notice] Received reload signal (hup). Reloading
 config and resetting internal state.
 Jan 06 16:28:11.000 [notice] Read configuration file "/etc/tor/tor.cfg".
 Jan 06 16:28:12.000 [notice] Tor 0.3.1.9 (git-df96a13e9155c7bf) opening
 log file.
 Jan 06 16:28:12.000 [warn] Giving up launching first hop of circuit to
 rendezvous point  ............
 Jan 06 16:28:12.000 [warn] Giving up launching first hop of circuit to
 rendezvous point  ............
 Jan 06 16:28:12.000 [warn] Giving up launching first hop of circuit to
 rendezvous point  ............
 Jan 06 16:28:12.000 [warn] Giving up launching first hop of circuit to
 rendezvous point  ............
 Jan 06 16:28:12.000 [warn] Giving up launching first hop of circuit to
 rendezvous point  ............
 Jan 06 16:28:12.000 [warn] Giving up launching first hop of circuit to
 rendezvous point  ............
 ........


 Waited for an hour for Tor to repair itself but it was just throwing
 'giving up' warning.

 Server was running 250 domains, not DDoSed, up to 200 users connected.

 The first time this problem occur couple of days on Tor instance running
 only 1 domain but it was online for days.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24813>
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