[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-relays] Relay out of consensus after node migration



Hi Teor,

I've restarted tor, please see attached the notice logs I've uploaded to debian's pastebin:
https://paste.debian.net/hidden/133a9cb5

Thanks & best regards.


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, 21 de September de 2018 0:46, teor <teor@xxxxxxxxxx> wrote:


On 21 Sep 2018, at 04:26, T0r-n0d3 <t0r-n0d3@xxxxxxxxxxxxxx> wrote:
I recently migrated my tor node to new hardware:
t0rnod3 5582BBEC12380E34D7DFB8C237939A0B317B205E

Copying  the /var/lib/tor/keys/ folder on the process.
Now my node do not handles circuits, nor it's shown in atlas and I see the following on the logs:
[notice] Heartbeat: It seems like we are not in the cached consensus.

What does your relay log when it uploads its descriptor to the directory
authorities?

Please restart your relay, and send us your notice-level logs via a pastebin
service.

https://paste.debian.net/ is accessible over tor, for those of us who use
Tor Browser.

T

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays