Opened 12 years ago

Last modified 7 years ago

#481 closed defect (Duplicate)

Tor server complains about too less directory information, even if we are a server

Reported by: Athaba Owned by: nickm
Priority: Low Milestone: 0.2.0.x-final
Component: Core Tor/Tor Version: 0.1.2.14
Severity: Keywords:
Cc: Athaba, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Tor server complains about too less directory information to build a circuit, even if we are a server.
It is possible that you over read real problems because of this.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (10)

comment:1 Changed 12 years ago by nickm

I don't understand what the issue is. When Tor has fewer than a given number of networkstatus statements and
server descriptors, it complains about not having enough directory information. Servers need to build circuits
too, and they need the same directory information as everybody else to do it.

comment:2 Changed 12 years ago by Athaba

Hmm.. I reported this on the IRC channel and they said it's normal, because the server doesn't need full circuits and I should report it here.

comment:3 Changed 12 years ago by weasel

When Tor is run as a server only without ever being used as a client users have reported
they see the 'we downloaded some dir information, but not enough to build circuits' log
entries regularly after a while.

My guess is this is because if we do not build circuits we stop fetching dir info after a
while to save load on the dirservers etc. Now if we - for whatever reason - get or fetch
a new descriptors (could it even be our own?) we produce the above mentioned log message.
This probably only happenes to servers without DirPort set.

comment:4 Changed 12 years ago by keb

Here is some supporting log info from a Tor 0.2.0.6-alpha process which is running as client-only:

Sep 03 21:29:33.897 [notice] Tried for 120 seconds to get a connection to [scrubbed]:6667. Giving up. (waiting for rendezvous desc)
Sep 06 17:43:12.599 [notice] Our directory information is no longer up-to-date enough to build circuits.
Sep 06 18:07:37.719 [notice] I learned some more directory information, but not enough to build a circuit.
...(lots of same message spread unevenly over the day)
Sep 07 11:12:29.854 [notice] We now have enough directory information to build circuits.
Sep 11 20:28:17.224 [notice] Our directory information is no longer up-to-date enough to build circuits.
Sep 11 20:50:50.677 [notice] I learned some more directory information, but not enough to build a circuit.
...(lots of same message. i could not connect to irc so i restarted the Tor process)
Sep 11 21:52:50.284 [notice] Interrupt: exiting cleanly.
Sep 11 21:52:52.499 [notice] Tor 0.2.0.6-alpha (r11277) opening log file.
Sep 11 21:53:08.041 [notice] We now have enough directory information to build circuits.
Sep 11 21:53:09.498 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.

comment:5 Changed 12 years ago by keb

oops meant to add observation that
Tor reliably gathers enough directory info within seconds of starting,
but when left running for a while its directory info decays to unusable state.

comment:6 Changed 12 years ago by nickm

We fixed some bugs that might have caused this, but this could also be an instance of 447.

Also, the messages about not having enough directory info are better now, but they could be better still.

comment:7 Changed 12 years ago by nickm

Closing as likely partially fixed, and likely duplicate of 447.

comment:9 Changed 12 years ago by nickm

flyspray2trac: bug closed.

comment:8 Changed 12 years ago by nickm

We fixed some bugs that might have caused this, but this could also be an instance of 447.

Also, the messages about not having enough directory info are better now, but they could be better still.

comment:9 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.