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

changed milestone to %Tor: 0.2.4.x-final

added component::core tor/tor milestone::Tor: 0.2.4.x-final priority::medium reporter::torland resolution::duplicate status::closed tor-relay type::defect version::tor 0.2.4.2-alpha labels

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?

Trac:
Status: new to needs_information

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

Trac:
Status: needs_information to new

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

Trac:
Milestone: N/A to Tor: 0.2.4.x-final
Cc: N/A to ln5

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.

Trac:
Username: torland

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

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.

Trac:
Username: torland

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

Trac:
Resolution: N/A to duplicate
Status: new to closed

Trac:
Keywords: N/A deleted, tor-relay added

Trac:
Component: Tor Relay to Tor

closed

mentioned in issue #6815 (moved)

moved to tpo/core/tor#6814 (closed)

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

Child items ...

Activity