I moved the older keys to my working delay and had to generate new one in the faulty one.
Here you can find my info.log file i did not have one beforehand, so i can not compare it. However it seems like the relay is working now. https://pastebin.com/iC5Rutq8 Could it be working now because there is minimized load due to the new keys? What should i do to reduce the load? Decrease max bandwith or can i somehow decrease max connections? Am 17.02.2018 um 03:03 schrieb teor: > Hi, > > On 17 Feb 2018, at 12:26, Paul <p...@roteserver.de > <mailto:p...@roteserver.de>> wrote: > >> A big Part from my systemd daemon.log which maybe already shows the >> issue. >> >> https://pastebin.com/yS9ZAwH4 >> > This is what is happening: > >>> Tor never bootstraps, so systemd restarts it. >>> You can confirm by checking your systemd logs. > > Please check your network connection: > >>> Is your network connection fast and reliable enough? >>> >>> Tor needs a lot of connections. >>> Does your pi support 6000 simultaneous connections? >>> Does your router support 12,000 simultaneous connections? >>> Most home routers don't. > >>>>> I'd really need to see your logs to work out what's happening. >>> >>> I need to see what happens between log lines like this: >>> >>> Feb 16 23:37:49.000 [notice] Bootstrapped 0%: Starting >>> Feb 16 23:43:45.000 [notice] Tor 0.2.9.14 (git-a211f886ad759cab) >>> opening log file. > > I still need to see copies of the info-level logs between these lines. > > T > > > _______________________________________________ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
