Hi Matt,
this is non fatal and as you can see by the most recent log entries, you could ignore it - anyway, some contributor warned about this occurring with more recent tor builds since the way tor probes for listening sockets has changed / it now always binds to all IPv4 & IPv6 addresses and then does reachability checks for each?
It was something along the lines of that.
What if you manually specify your listening IP addresses and port like I do:
ORPort 37.157.195.83:38619 ORPort [2a02:2b88:2:1::3239:0]:38619
This should satisfy tor, at least it does on 0.4.4.6 which is the newest version available through the official ArchLinux repositories, not sure about 0.4.5.x branch which states the following in it's change log:
This release series introduces significant improvements in relay (IPv6) address discovery.
That would be much safer and cleaner than tor trying to guess which addresses it's supposed to bind to anyway :-)
Thank you for running a relay!
Best Regards, William
2021-03-01 12:49 GMT, William Kane ttallink@googlemail.com:
Hi Matt,
this is non fatal and as you can see by the most recent log entries, you could ignore it - anyway, some contributor warned about this occurring with more recent tor builds since the way tor probes for listening sockets has changed / it now always binds to all IPv4 and IPv6 addresses an does reachability checks for each?
It was something along the lines of that.
What if you manually specify your listening IP addresses and port like I do:
ORPort 37.157.195.83:38619 ORPort [2a02:2b88:2:1::3239:0]:38619
This should satisfy tor, at least it does on 0.4.4.6 which is the newest version available through the official ArchLinux repositories, not sure about 0.4.5.x branch which states the following in it's changelog:
This release series introduces significant improvements in relay (IPv6) address discovery.
That would be much safer and cleaner than tor trying to guess which addresses it's supposed to bind to anyway :-)
Hope I helped, William
2021-02-28 15:28 GMT, tor tor@kevinandmatt.com:
Hi All, This popped up today after running successfully for about a week. -matt
x 09:32:50 [NOTICE] Self-testing indicates your ORPort *.*.*.*:443 is reachable from the outside. Excellent. Publishing server descriptor. x 09:32:50 [NOTICE] Now checking whether IPv4 ORPort *.*.*.* :443 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) x 09:32:26 [NOTICE] External address seen and suggested by a directory authority: *.*.*.* x 09:30:52 [NOTICE] Bootstrapped 100% (done): Done x 09:30:52 [NOTICE] Bootstrapped 95% (circuit_create): Establishing a Tor circuit x 09:30:52 [NOTICE] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits x 09:30:52 [NOTICE] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits x 09:30:52 [NOTICE] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits x 09:30:52 [NOTICE] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits x 09:30:52 [NOTICE] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits x 09:30:51 [NOTICE] Bootstrapped 68% (loading_descriptors): Loading relay descriptors x 09:30:51 [NOTICE] Bootstrapped 63% (loading_descriptors): Loading relay descriptors x 09:30:51 [NOTICE] Bootstrapped 55% (loading_descriptors): Loading relay descriptors x 09:30:50 [NOTICE] Bootstrapped 50% (loading_descriptors): Loading relay descriptors x 09:30:50 [NOTICE] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors x 09:30:50 [NOTICE] Bootstrapped 15% (handshake_done): Handshake with a relay done x 09:30:50 [NOTICE] Bootstrapped 14% (handshake): Handshaking with a relay x 09:30:50 [WARN] Bug: /usr/lib/aarch64-linux-gnu/libevent-2.1.so.6(+0x21a10) [0xffff8575ba10] (on Tor 0.4.5.6 ) x 09:30:50 [WARN] Bug: /usr/bin/tor(+0x81854) [0xaaaae3745854] (on Tor 0.4.5.6 ) x 09:30:50 [WARN] Bug: /usr/bin/tor(+0x21419c) [0xaaaae38d819c] (on Tor 0.4.5.6 ) x 09:30:50 [WARN] Bug: /usr/bin/tor(consider_publishable_server+0x5c) [0xaaaae377099c] (on Tor 0.4.5.6 ) x 09:30:50 [WARN] Bug: /usr/bin/tor(router_rebuild_descriptor+0x90) [0xaaaae3770588] (on Tor 0.4.5.6 ) x 09:30:50 [WARN] Bug: /usr/bin/tor(router_build_fresh_descriptor+0x44) [0xaaaae377016c] (on Tor 0.4.5.6 ) x 09:30:50 [WARN] Bug: /usr/bin/tor(+0xabaa0) [0xaaaae376faa0] (on Tor 0.4.5.6 ) x 09:30:50 [WARN] Bug: /usr/bin/tor(relay_addr_learn_from_dirauth+0x1a8) [0xaaaae38d6bb0] (on Tor 0.4.5.6 ) x 09:30:50 [WARN] Bug: /usr/bin/tor(tor_bug_occurred_+0x164) [0xaaaae37c15dc] (on Tor 0.4.5.6 ) x 09:30:50 [WARN] Bug: /usr/bin/tor(log_backtrace_impl+0x68) [0xaaaae37b5fc0] (on Tor 0.4.5.6 ) x 09:30:50 [WARN] Bug: Tor 0.4.5.6: Non-fatal assertion !(!ei) failed in relay_addr_learn_from_dirauth at ../src/feature/relay/relay_find_addr.c:235. Stack trace: (on Tor 0.4.5.6 ) x 09:30:50 [WARN] tor_bug_occurred_(): Bug: ../src/feature/relay/relay_find_addr.c:235: relay_addr_learn_from_dirauth: Non-fatal assertion !(!ei) failed. (on Tor 0.4.5.6 ) x 09:30:50 [NOTICE] Unable to find IPv4 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. x 09:30:50 [NOTICE] Opened Control listener connection (ready) on /run/tor/control qj 09:30:50 [NOTICE] Opening Control listener on /run/tor/control