Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#6814 closed defect (duplicate)

Requested exit point '$XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' is not known. Closing

Reported by: torland Owned by:
Priority: Medium Milestone: Tor: 0.2.4.x-final
Component: Core Tor/Tor Version: Tor: 0.2.4.2-alpha
Severity: Keywords: tor-relay
Cc: ln5 Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I upgraded today to 0.2.4.2-alpha and get warnings of the type

"Requested exit point '$XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' is not known. Closing."

'$XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' is the fingerprint of the relay.

Child Tickets

Change History (10)

comment:1 in reply to:  description Changed 7 years ago by rransom

Status: newneeds_information

Replying to torland:

I upgraded today to 0.2.4.2-alpha and get warnings of the type

"Requested exit point '$XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' is not known. Closing."

'$XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' is the fingerprint of the relay.

Is the relay with this fingerprint in the current consensus?

comment:2 Changed 7 years ago by rransom

Status: needs_informationnew

Oh, you upgraded the relay, and it is showing its own fingerprint in that log message.

comment:3 Changed 7 years ago by nickm

What version did you upgrade from? Was this working in 0.2.4.1.alpha or did you upgrade from 0.2.3.x?

comment:4 Changed 7 years ago by nickm

Cc: ln5 added
Milestone: Tor: 0.2.4.x-final

comment:5 Changed 7 years ago by torland

I upgraded from 0.2.3.20rc. The warning shows the relays own fingerprint. I don't know if it happened with 0.2.4.1.alpha.

comment:6 Changed 7 years ago by rransom

Does your relay run on a computer which thinks it has IPv6 support?

comment:7 Changed 7 years ago by torland

I don't know. ifconfig tells me that eth0 has a IPv6 address assigned. But I have not configured anything IPv6 related in tor config file. eth0 is not used by tor, only virtual interfaces of eth0.

comment:8 Changed 7 years ago by rransom

Resolution: duplicate
Status: newclosed

This is definitely just another symptom of the bug that caused #6815. (See 6815#comment:18.) Closing this ticket as a duplicate, because it was mostly handled as one.

comment:9 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:10 Changed 7 years ago by nickm

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