Opened 10 years ago

Closed 9 years ago

Last modified 7 years ago

#1172 closed defect (fixed)

ORPort found reachable, but I have no routerinfo

Reported by: stars Owned by:
Priority: High Milestone:
Component: Core Tor/Tor Version: 0.2.2.6-alpha
Severity: Keywords:
Cc: stars, Sebastian, nickm, dun, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by nickm)

Hello,

Today i update the git version on master branch : commit d086c9a7f73ce5b9b7cf4add07fa7d071b829081
Merge: 9e6225a 28b29e0

and a bug are signaled on my log about the "router_or:port"

déc. 12 17:00:28.456 [Warning] router_orport_found_reachable(): Bug: ORPort found reachable, but I have no routerinfo yet. Failing to inform controller of success.

libevent: 2.03 alpha Repository UUID: ce677c24-8c1a-0410-9497-a30ef3a96221
Revision: 1557

libc6: 2.10.1 (ubuntu15) (amd64)

OS: kubuntu karmic 9.10 on x86 64 ,Linux moon 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux

vidalia: 2.7svn Repository UUID: 819a2799-b909-0410-be78-af92f3896072
Revision: 4177

[Automatically added by flyspray2trac: Operating System: Other Linux]

Child Tickets

Change History (13)

comment:1 Changed 10 years ago by stars

same bug error on : 0.2.2.7alpha commit 3b4b6009a0020fb55fcb6464cc448e244680f9c8
Merge: 2309d0c aec4aea from git : Tor v0.2.2.7-alpha (git-3b4b6009a0020fb5). (Running on Linux x86_64)

janv. 24 20:05:51.443 [Warning] router_orport_found_reachable(): Bug: ORPort found reachable, but I have no routerinfo yet. Failing to inform controller of success.

comment:2 Changed 10 years ago by dun

I had the same error with 0.2.2.8-alpha (git-ff88bc7db8edeb29)

In my case it was due to a misconfiguration in /etc/hosts on my server.
The host I used in torrc did resolve to 127.0.0.2 which caused a "[info] resolve_my_address(): Address '0trace.de' resolves to private IP address '127.0.0.2'"

Well, at least tor starts up correctly without any warning after I edited my hosts file and removed 0trace from there.

Hope this helps,

MK

comment:3 Changed 10 years ago by arma

did you have your tor running for a while, then you restarted it, and then

the warning showed up?

dun> yes

so it happens when we find ourselves reachable before we have done any
directory fetches to give us hints about our external ip address

comment:4 Changed 10 years ago by arma

I think many instances of this bug were due to bug 1269.

Leaving open since my comment above indicates a bug that we should investigate
and maybe fix, even if it rarely triggers by itself.

comment:5 Changed 9 years ago by nickm

Description: modified (diff)
Milestone: Tor: 0.2.3.x-final

comment:6 Changed 9 years ago by keb

Confirm the message occurs with tor 0.2.2.19-alpha every time i launch, immediately after this message:
[notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.

There is an existing data directory.

debian 5.0.7, libevent 1.4.13, openssl 0.9.8g, no controller.

ubuntu 10.10, libevent 2.0.8-rc, openssl 0.9.8o, vidalia connection open before message.

notes from OFTC-#tor 2010-12-16:
(arma) i've seen that message on and off. i thought maybe we'd resolved it.
...
(arma) i tracked down the bug a while ago, but i guess i didn't do anything
(arma) it is harmless

comment:7 Changed 9 years ago by keb

update: have not encountered that message in versions 0.2.2.20-alpha and higher

comment:8 Changed 9 years ago by Sebastian

See #2677 for a report of this happening with 0.2.1.30

comment:9 Changed 9 years ago by arma

And #2745 for a report of it happening with 0.2.2.23-alpha.

comment:10 Changed 9 years ago by arma

Milestone: Tor: 0.2.3.x-finalTor: 0.2.1.x-final
Priority: minormajor
Status: newneeds_review

"so it happens when we find ourselves reachable before we have done any directory fetches to give us hints about our external ip address" was spot on.

There's a fix in my bug1172 branch.

Retargetting to 0.2.1.x since this is an actual bug that affects relays that use a controller.

comment:11 Changed 9 years ago by nickm

Resolution: Nonefixed
Status: needs_reviewclosed

Hrm. Looks okay. Merging

comment:12 Changed 7 years ago by nickm

Component: Tor RelayTor

comment:13 Changed 7 years ago by nickm

Milestone: Tor: 0.2.1.x-final

Milestone Tor: 0.2.1.x-final deleted

Note: See TracTickets for help on using tickets.