Re: [tor-relays] Relay not connecting
> According to > https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8 F65B5881B7D4C97C > the relay is back since 1-2 days, good. Exiting to port 22 might lead > to a lot of complaints ending at your ISP or yourself. Default SSH. Yes, as I said I put it back online by rebuilding my server completely. Did not know that about port 22. I used a variant of the ReducedExitPolicy which accepts port 22 according to https://gitlab.torproject.org/legacy/trac/-/wikis/doc/ReducedExitPolicy . > Did you check > https://gitlab.torproject.org/tpo/core/tor/-/issues/ for the bug you > reported? I wasn't even sure if it was a bug, if I did something wrong, or if it was related to my ISP; hence my question on the mailing list. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Relay not connecting
Hi >Sorry, but I'm going to vent a little bit. I'm not a network >specialist, so 11 days ago I sent the following email to this > mailing list asking for help because two of my Tor exit relays were > completely frozen and I was unable to put them online again. According to https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B5881B7D4C97C the relay is back since 1-2 days, good. Exiting to port 22 might lead to a lot of complaints ending at your ISP or yourself. Default SSH. >Nobody answered, not even a comment. No wait, there was one person Unfortunately that happens from time to time. Thanks for your good report. Did you check https://gitlab.torproject.org/tpo/core/tor/-/issues/ for the bug you reported? > - very active on this mailing list recently - who sent me an email >personally to tell me that I was an idiot (referring to what, I > don't know) who should kill himself. Adding furthermore that if I > didn't commit suicide within 72 hours, he would personally come to my > house and kill me with a Glock 9 mm. Fun stuff, very disturbing. Nobody should read or write something like that. Makes me sad. >Anyway, no serious answers, someone calling me an idiot: I tried to >look as best as I could at what I did wrong. Couldn't find Again, nobody should read or write such. > anything. My only available solution was to rebuild completely my > server, something I wanted to do for a while because of other > undesired quirks that were bothering me with my setup. I knew it > would take a long time - which I didn't really have - but I finally > finished my new setup yesterday. (Don't look for > 25FC41154DCB2CAE3ABD74A8DFCD5B90D2CFFD57 or the bridge, they have > been shut down for the moment.) 3B85067588C3F017D5CCF7D8F65B5881B7D4C97C is actually running >Today, I read a line from Chris Endiku-6 saying: "Thereâs > something going on for a while and I havenât seen any mentions of > it." The exact problem I mentioned! He says it goes "as early as > Dec.23"; my problem goes to Dec 18 as shown in my previous email. > Also, not mentioned in my previous email, before I renewed my setup, > my tor-ddos firewall rules (I use the ones from Endiku-6) had blocked > about 5 times more IP than usual - if that can be useful information > to anyone. Yeah, those things are the spices in our dish. Not sure yet if this is an attack. I observe it too and investigate on my end. Trying to understand the complex vector. >I still would like to know how to restart such a relay, if this > happens again in the future - other than reinstalling the entire > server, that is. Those are my questions too :) . Case by case and issue by issue. Stay save out there! -- Cheers, Felix pgpynMp81Z0qm.pgp Description: Digitale Signatur von OpenPGP ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Relay not connecting
I manage the two following exit relays: * https://metrics.torproject.org/rs.html#details/25FC41154DCB2CAE3ABD74A8DFCD5B90D2CFFD57 * https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B5881B7D4C97C They are both on the same IP and servers. A few hours ago they lost contact even though I have both Apache and I2P servers on the same machine that are reachable. The weird log messages seem to go back to Dec 18, after a restart: ``` Dec 18 07:49:47 a-n-o-n-y-m-e Tor-Alberta[904715]: Bootstrapped 100% (done): Done Dec 18 07:54:18 a-n-o-n-y-m-e Tor-Alberta[904715]: Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. Dec 18 07:57:11 a-n-o-n-y-m-e Tor-Alberta[904715]: Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [14254 similar message(s) suppressed in last 180 seconds] ``` There are a few more of these messages appearing afterward (My bandwidth is unlimited). This is the typical Heartbeat that comes afterward: ``` Dec 18 13:49:42 a-n-o-n-y-m-e Tor-Alberta[904715]: Heartbeat: Tor's uptime is 6:00 hours, with 476 circuits open. I've sent 30.87 GB and received 9.04 GB. I've received 13401 connections on IPv4 and 0 on IPv6. I've made 46754 connections with IPv4 and 0 with IPv6. Dec 18 13:49:42 a-n-o-n-y-m-e Tor-Alberta[904715]: While not bootstrapping, fetched this many bytes: 6412201 (server descriptor fetch); 1424 (server descriptor upload); 376002 (consensus network-status fetch); 57564 (microdescriptor fetch) Dec 18 13:49:42 a-n-o-n-y-m-e Tor-Alberta[904715]: Circuit handshake stats since last time: 8/8 TAP, 1356688/6457307 NTor. Dec 18 13:49:42 a-n-o-n-y-m-e Tor-Alberta[904715]: Since startup we initiated 0 and received 0 v1 connections; initiated 0 and received 0 v2 connections; initiated 0 and received 0 v3 connections; initiated 0 and received 429 v4 connections; initiated 285 and received 11137 v5 connections. Dec 18 13:49:42 a-n-o-n-y-m-e Tor-Alberta[904715]: Heartbeat: DoS mitigation since startup: 0 circuits killed with too many cells, 0 circuits rejected, 0 marked addresses, 0 marked addresses for max queue, 0 same address concurrent connections rejected, 0 connections rejected, 0 single hop clients refused, 0 INTRODUCE2 rejected. ``` Then I have this kind of message appearing: ``` Dec 18 14:13:23 a-n-o-n-y-m-e Tor-Alberta[904715]: No circuits are opened. Relaxed timeout for circuit 4487 (a Measuring circuit timeout 3-hop circuit in state doing handshakes with channel state open) to 6ms. However, it appears the circuit has timed out anyway. [4 similar message(s) suppressed in last 3300 seconds] ``` Then a few days later, this bug report: ``` Dec 21 15:18:48 a-n-o-n-y-m-e Tor-Alberta[904715]: tor_bug_occurred_(): Bug: ../src/core/or/conflux.c:567: conflux_pick_first_leg: Non-fatal assertion !(smartlist_len(cfx->legs) <= 0) failed. (on Tor 0.4.8.10 ) Dec 21 15:18:48 a-n-o-n-y-m-e Tor-Alberta[904715]: Bug: Tor 0.4.8.10: Non-fatal assertion !(smartlist_len(cfx->legs) <= 0) failed in conflux_pick_first_leg at ../src/core/or/conflux.c:567. Stack trace: (on Tor 0.4.8.10 ) Dec 21 15:18:48 a-n-o-n-y-m-e Tor-Alberta[904715]: Bug: /usr/bin/tor(log_backtrace_impl+0x5b) [0x55651f95b37b] (on Tor 0.4.8.10 ) Dec 21 15:18:48 a-n-o-n-y-m-e Tor-Alberta[904715]: Bug: /usr/bin/tor(tor_bug_occurred_+0x18a) [0x55651f97294a] (on Tor 0.4.8.10 ) Dec 21 15:18:48 a-n-o-n-y-m-e Tor-Alberta[904715]: Bug: /usr/bin/tor(conflux_decide_next_circ+0x40e) [0x55651fa12afe] (on Tor 0.4.8.10 ) Dec 21 15:18:48 a-n-o-n-y-m-e Tor-Alberta[904715]: Bug: /usr/bin/tor(circuit_get_package_window+0x75) [0x55651fa12ec5] (on Tor 0.4.8.10 ) Dec 21 15:18:48 a-n-o-n-y-m-e Tor-Alberta[904715]: Bug: /usr/bin/tor(+0x9ed63) [0x55651f908d63] (on Tor 0.4.8.10 ) Dec 21 15:18:48 a-n-o-n-y-m-e Tor-Alberta[904715]: Bug: /usr/bin/tor(connection_edge_package_raw_inbuf+0xae) [0x55651f90b80e] (on Tor 0.4.8.10 ) Dec 21 15:18:48 a-n-o-n-y-m-e Tor-Alberta[904715]: Bug: /usr/bin/tor(connection_edge_process_inbuf+0x6f) [0x55651fa2b9df] (on Tor 0.4.8.10 ) Dec 21 15:18:48 a-n-o-n-y-m-e Tor-Alberta[904715]: Bug: /usr/bin/tor(+0x1c2fb4) [0x55651fa2cfb4] (on Tor 0.4.8.10 ) Dec 21 15:18:48 a-n-o-n-y-m-e Tor-Alberta[904715]: Bug: /usr/bin/tor(+0x73ffc) [0x55651f8ddffc] (on Tor 0.4.8.10 ) Dec 21 15:18:48 a-n-o-n-y-m-e Tor-Alberta[904715]: Bug: /lib/x86_64-linux-gnu/libevent-2.1.so.7(+0x1ff58) [0x7fcee899bf58] (on Tor 0.4.8.10 ) Dec 21 15:18:48 a-n-o-n-y-m-e Tor-Alberta[904715]: Bug: /lib/x86_64-linux-gnu/libevent-2.1.so.7(event_base_loop+0x577) [0x7fcee899d8a7] (on Tor 0.4.8.10 ) Dec 21 15:18:48 a-n-o-n-y-m-e Tor-Alberta[904715]: Bug: /usr/bin/tor(do_main_loop+0x127) [0x55651f8de7c7] (on Tor 0.4.8.1