<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><div>On 26 Jan 2018, at 19:55, Dark Matter <<a href="mailto:tor-relay@gmx.net">tor-relay@gmx.net</a>> wrote:<br><br></div><blockquote type="cite"><div><span>Hello,</span><br><span> </span><br><span>I'm running a tor-relay with Tor version 0.3.2.9 (stable). I had to do some daemon restarts, because of connection limit issues.</span></div></blockquote><div><br></div><div>There has been extra load on the network since December.</div><div>We are working on some relay defences:</div><div><a href="https://lists.torproject.org/pipermail/tor-relays/2018-January/014175.html">https://lists.torproject.org/pipermail/tor-relays/2018-January/014175.html</a></div><div><br></div><blockquote type="cite"><div><span>Since the last two restarts the Tor process issues a lot of warnings while bootstrapping, because it could not create a (client) circuit.</span></div></blockquote><blockquote type="cite"><div>Relay functionality is working without problems.</div></blockquote><div><br></div><div><div><span style="background-color: rgba(255, 255, 255, 0);">Your relay has probably chosen some overloaded guards.</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">The problem comes from the extra load on those machines, not your relay.</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Your relay will eventually try other guards.</span></div></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Are you sure it's not overloaded?</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">It might be worth checking the logs, inbound connections, RAM, and CPU</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">after it has been running for a few days.</span></div><div><br></div><blockquote type="cite"><div><span>Before these restarts I had no problems connecting to the tor network and creating circuits. Tor usually booted within less than a minute without warnings.</span><br><span>I found a ticket describing the same problem (although for a different Tor version) here: <a href="https://trac.torproject.org/projects/tor/ticket/24639">https://trac.torproject.org/projects/tor/ticket/24639</a>. Are there any known workarounds yet?</span><br></div></blockquote><div><br></div><div>Ignore the warning messages unless your relay is having problems.</div><div><br></div><div><div><span style="background-color: rgba(255, 255, 255, 0);">If your relay's traffic drops, or it starts using excessive CPU, RAM, or sockets,</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">there are some things you can do. You can change your tor config, or the</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">number of file descriptors, or block excessive connections from a single IP</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">using a firewall:</span></div><div><a href="https://lists.torproject.org/pipermail/tor-relays/2018-January/014100.html" style="background-color: rgba(255, 255, 255, 0);"><font color="#000000">https://lists.torproject.org/pipermail/tor-relays/2018-January/014100.html</font></a></div></div><div><br></div><blockquote type="cite"><div><span>For more detail, I'll post the last warning messages:</span><br><span> </span><br><span>Jan 25 18:31:54.000 [warn] Problem bootstrapping. Stuck at 90%: Establishing a Tor circuit. (Connection timed out; TIMEOUT; count 1503; recommendation warn; host B7047FBDE9C53C39011CA84E5CB2A8E3543066D0 at 199.249.223.60:443)</span><br><span>Jan 25 18:31:54.000 [warn] 1503 connections have failed:</span><br><span>Jan 25 18:31:54.000 [warn] 1026 connections died in state connect()ing with SSL state (No SSL object)</span><br><span>Jan 25 18:31:54.000 [warn] 392 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE</span><br><span>Jan 25 18:31:54.000 [warn] 84 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN</span><br><span>Jan 25 18:31:54.000 [warn] 1 connections died in state handshaking (TLS) with SSL state unknown state in HANDSHAKE</span><br><span> </span><br><span>Tor had to try to open a circuit for more than half an hour before finally succeeding...</span><br></div></blockquote><br><div>As long as your relay is fine, there is nothing you can do here.</div><div><br></div><div>T</div></body></html>