Opened 13 years ago

Last modified 7 years ago

#349 closed defect (Fixed)

getinfo network-status sometimes returns an incomplete list

Reported by: edmanm Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: edmanm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Sometimes Tor's response to a "getinfo network-status" does not appear to include all known OR identities.
Some servers may not be included in the returned list, even though Tor has built circuits through them. Sometimes
the returned list is entirely empty, even though Tor has built circuits and displayed its happy "Tor has
successfully opened a circuit" message.

Here is an example:

getinfo network-status
250-network-status=autonomynodev2=$EFE988B0EF6A708F5BB6A843AC507604D0C38239 KB=$C938A72F7E0333CEF5AA7C0B45FC74EF4E02F55D HaschMichMaedc
hen=$F9D4EC6EAC081C3F26BF703932B07BB1B161F22F histor2=$3276923C1617879D3246133BD37111A661461382 hppie=$BBEB4939DF13BAC358DF49608C3B760A
A6047EAB $D8632EAE2A5CA7BA147AB5489D43B5E2E80C37D7 $02FF7F59145E4917321739947585C757B22B4008 $1783E1CD818BB74FB20FE46E7317FBC26D13172E
$519C8B8E1A51F3D2593B6675A9768D83F9F041CB $999C4E1F995A0714E7D64E8A6CD09AC4490E72D6
250 OK
getinfo circuit-status
7 BUILT freetux4ever,enterprise,utcluj
5 BUILT freetux4ever,spinell,waabbeel
4 BUILT myrandomnode,spinell,Tonga
3 BUILT myrandomnode,l3cht3rn3t,idbsgetyrubdgretyrw
250 OK

Tor returned a list of ten servers and has currently built four circuits using nine distinct servers. Doing a
"getinfo desc/id/<keyid>" for each of the non-Named servers above told me they have the following nicknames:


We see that the set of servers returned by "getinfo network-status" and the set of servers through which we
have built circuits are even disjoint, in this case.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (2)

comment:1 Changed 13 years ago by nickm

flyspray2trac: bug closed.
Fixed in r3384

comment:2 Changed 7 years ago by nickm

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