Opened 6 years ago

Closed 5 years ago

#9333 closed defect (worksforme)

Illegal nickname "PPriv@last-listed" in family line

Reported by: cypherpunks Owned by: mikeperry
Priority: Medium Milestone: Tor: 0.2.5.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: 024-backport microdescriptor
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I'm using the current(?) version of the Tor Browser bundle (version 2.3.25-10 I think; how do I find out which version I am running?) on GNU/Linux.

After a system crash (failing to shut down properly - laptop battery ran out) while tor browser was running, I was unable to restart Tor browser again after reboot. I got two error messages from vidalia; one saying that vidalia was unable to connect to the control port, the other saying that the tor process had exited immediately after launch. The last line in the tor logfile was a warning:

[Warning] Illegal nickname "PPriv@last-listed" in family line

Grepping through the Data/Tor/ directory, I found such a line in the cached-microdescs file. After deleting this file I was able to launch tor browser again.

Tor browser/vidalia should recover from this kind of error automatically, without manual user intervention.

Child Tickets

Change History (4)

comment:1 Changed 6 years ago by rransom

Component: TorBrowserButtonTor

comment:2 Changed 6 years ago by nickm

Keywords: 045-backport microdescriptor added
Milestone: Tor: 0.2.5.x-final
Summary: Tor browser fails to launch after crashIllegal nickname "PPriv@last-listed" in family line

comment:3 Changed 6 years ago by nickm

Keywords: 024-backport added; 045-backport removed

I *think* this might be one of the things we fixed with the microdescriptor fixes in 0.2.4. But we should look harder at that in 0.2.5, and make this error recoverable.

comment:4 Changed 5 years ago by nickm

Resolution: worksforme
Status: newclosed

This is either fixed in 0.2.4, is some variant of the "recover from bad microdescs file" bug. Closing this ticket. Please reopen if it's reproducible.

Note: See TracTickets for help on using tickets.