Thanks. How in torrc to configure no ipv6? Thanks. --Keifer
On Sat, Feb 17, 2024, 4:42 PM Keifer Bly <keifer....@gmail.com> wrote: > Hi, > > So my relay at > > > https://metrics.torproject.org/rs.html#details/79E3B585803DE805CCBC00C1EF36B1E74372861D > > > Goes offline at sporadic times. Upon checking the tor log file, there does > not appear to be anything written causing tor to crash: > > > Feb 18 00:36:34.000 [notice] Tor 0.4.8.10 opening new log file. > Feb 18 00:36:34.630 [notice] We compiled with OpenSSL 101010ef: OpenSSL > 1.1.1n 15 Mar 2022 and we are running with OpenSSL 101010ef: 1.1.1n. These > two versions should be binary compatible. > Feb 18 00:36:34.634 [notice] Tor 0.4.8.10 running on Linux with Libevent > 2.1.8-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma 5.2.4, Libzstd 1.3.8 and > Glibc 2.28 as libc. > Feb 18 00:36:34.634 [notice] Tor can't help you if you use it wrong! Learn > how to be safe at https://support.torproject.org/faq/staying-anonymous/ > Feb 18 00:36:34.636 [notice] Read configuration file "/etc/tor/torrc". > Feb 18 00:36:34.637 [notice] Based on detected system memory, > MaxMemInQueues is set to 1462 MB. You can override this by setting > MaxMemInQueues by hand. > Feb 18 00:36:34.640 [notice] Opening OR listener on 0.0.0.0:9001 > Feb 18 00:36:34.640 [notice] Opened OR listener connection (ready) on > 0.0.0.0:9001 > Feb 18 00:36:34.640 [notice] Opening OR listener on [::]:9001 > Feb 18 00:36:34.640 [notice] Opened OR listener connection (ready) on > [::]:9001 > Feb 18 00:36:34.640 [notice] Opening Directory listener on 0.0.0.0:9030 > Feb 18 00:36:34.640 [notice] Opened Directory listener connection (ready) > on 0.0.0.0:9030 > Feb 18 00:36:35.000 [notice] Configured to measure directory request > statistics, but no GeoIP database found. Please specify a GeoIP database > using the GeoIPFile option. > Feb 18 00:36:35.000 [warn] You are running Tor as root. You don't need to, > and you probably shouldn't. > Feb 18 00:36:35.000 [notice] Your Tor server's identity key fingerprint is > 'udeserveprivacy 79E3B585803DE805CCBC00C1EF36B1E74372861D' > Feb 18 00:36:35.000 [notice] Your Tor server's identity key ed25519 > fingerprint is 'udeserveprivacy b7n+DkH5IsJHJexEqilhQ5tC0LRd9Td888RZpYkxEvc' > Feb 18 00:36:35.000 [notice] Bootstrapped 0% (starting): Starting > Feb 18 00:36:49.000 [notice] Starting with guard context "default" > Feb 18 00:36:50.000 [notice] Unable to find IPv6 address for ORPort 9001. > You might want to specify IPv4Only to it or set an explicit address or set > Address. > Feb 18 00:36:50.000 [notice] Bootstrapped 5% (conn): Connecting to a relay > Feb 18 00:36:50.000 [notice] Bootstrapped 10% (conn_done): Connected to a > relay > > Unless the old file is being overwritten when tor restarts. But is there a > known problem with OVH that causes this? > > Thanks. > > Oddly there is no definite time when this happens, sometimes the relay > operates no problem for weeks on end and then it happens, other times it > only makes it a day or two. > --Keifer >
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
