Opened 13 years ago

Last modified 8 years ago

#403 closed defect (Fixed)

0.1.2.x warns about non-named servers out of the blue

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


Mar 11 18:19:50.085 [warn] You specified a server "BlueStar88b" by name, but thi
s name is not registered, so it could be used by any server, not just the one yo
u meant. To make sure you get the same server in the future, refer to it by key,

as "$F5B9ABFAB2C44E790AAFC5344B9F00FBDF6DC36E".

Problem is, I didn't ever mention it by name. I only have info level logs, but
they don't help at all. I was probably browsing at the time.

I guess something still refers to something by nickname, internally. I'll try
to collect more info as time goes by.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (7)

comment:1 Changed 13 years ago by nickm

might you have been running a hidden service?

comment:2 Changed 13 years ago by arma

I don't think so. I was running Vidalia which was running my Tor, using a
~/.vidalia/torrc of

ControlPort 9051
Log info file /tmp/tori-vidalia
Log notice stdout
Log notice file /tmp/vid-log
SafeLogging 0

and that's it.

comment:3 Changed 13 years ago by arma

Matt points out that this is probably an instance of bug 529: it was Vidalia
that was requesting the lookup. I didn't see any of these between bug 403 and
bug 529 though, so I'm guessing the old version of the bug is mostly gone.

comment:4 Changed 13 years ago by nickm

I wouldn't be too sure; the likeliest cause of bug 529 can still appear in 0.1.2.x.

comment:5 Changed 13 years ago by nickm

Though if it _was_ vidalia, that would explain the mysteriousness of the lookup. I'm going to call this fixed.

comment:6 Changed 13 years ago by nickm

flyspray2trac: bug closed.

comment:7 Changed 8 years ago by nickm

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