I am running two relays on debian (one on Raspian 9 and one on Debian 9) and one of them for over three months now.
Some time ago the older one started to loop at startup.
I reinstalled tor and it worked for some time only to loop again.
The last notices entry looks like this "Feb 16 19:36:14.000 [notice] Bootstrapped 0%: Starting" and the next is "Feb 16 19:42:08.000 [notice] Tor 0.2.9.14 (git-a211f886ad759cab) opening log file." then it tells about opening the listeners and parsing the GEOIP files, then my relay identity and the bootstrapped 0% entry again (left some informational entries out).
The debug log looks like it is getting descriptors and stuff correctly.
What could be the problem?
On 17 Feb 2018, at 10:44, Paul paul@roteserver.de wrote:
I am running two relays on debian (one on Raspian 9 and one on Debian 9) and one of them for over three months now.
Are you running an exit?
Please link to your relays on Relay Search.
Some time ago the older one started to loop at startup.
I reinstalled tor and it worked for some time only to loop again.
The last notices entry looks like this "Feb 16 19:36:14.000 [notice] Bootstrapped 0%: Starting" and the next is "Feb 16 19:42:08.000 [notice] Tor 0.2.9.14 (git-a211f886ad759cab) opening log file." then it tells about opening the listeners and parsing the GEOIP files, then my relay identity and the bootstrapped 0% entry again (left some informational entries out).
What is the log entry right before the relay restarts?
Please don't leave out log entries. When you do, we have to guess what the missing log entries are.
If you think the log is too long, put it in a pastebin that can be accessed using Tor Browser in high security mode.
The debug log looks like it is getting descriptors and stuff correctly.
What could be the problem?
Are you using systemd, or some other startup notification system? Your relay could be failing to notify systemd that it has started. And then systemd is restarting it.
Are there limits on RAM, file descriptors, or disk usage on your system? Your relay could be exceeding some kind of OS limit, and being terminated. And then systemd is restarting it.
I'd really need to see your logs to work out what's happening.
T
I am sorry for providing not enough info,
Both are no exits.
The error relay: A29D2A78A8A954819E220CEFBEBCE95D2FCFA54D (https://metrics.torproject.org/rs.html#details/A29D2A78A8A954819E220CEFBEBCE...)
The other one: A0B4C435650B6D86D618EFD10EDED34FD2AFF562 (https://metrics.torproject.org/rs.html#details/A0B4C435650B6D86D618EFD10EDED...)
here you can find my whole notices.log since the last reinstall: https://pastebin.com/RLTp7ZqJ
The Problem usually occures when i restart the PI after beeing shut down to long.
Tor is installed through the apt-get repository. I think it uses systemd
Am 17.02.2018 um 00:53 schrieb teor:
On 17 Feb 2018, at 10:44, Paul paul@roteserver.de wrote:
I am running two relays on debian (one on Raspian 9 and one on Debian 9) and one of them for over three months now.
Are you running an exit?
Please link to your relays on Relay Search.
Some time ago the older one started to loop at startup.
I reinstalled tor and it worked for some time only to loop again.
The last notices entry looks like this "Feb 16 19:36:14.000 [notice] Bootstrapped 0%: Starting" and the next is "Feb 16 19:42:08.000 [notice] Tor 0.2.9.14 (git-a211f886ad759cab) opening log file." then it tells about opening the listeners and parsing the GEOIP files, then my relay identity and the bootstrapped 0% entry again (left some informational entries out).
What is the log entry right before the relay restarts?
Please don't leave out log entries. When you do, we have to guess what the missing log entries are.
If you think the log is too long, put it in a pastebin that can be accessed using Tor Browser in high security mode.
The debug log looks like it is getting descriptors and stuff correctly.
What could be the problem?
Are you using systemd, or some other startup notification system? Your relay could be failing to notify systemd that it has started. And then systemd is restarting it.
Are there limits on RAM, file descriptors, or disk usage on your system? Your relay could be exceeding some kind of OS limit, and being terminated. And then systemd is restarting it.
I'd really need to see your logs to work out what's happening.
T
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 17 Feb 2018, at 11:41, Paul paul@roteserver.de wrote:
…
Both are no exits.
The error relay: A29D2A78A8A954819E220CEFBEBCE95D2FCFA54D (https://metrics.torproject.org/rs.html#details/A29D2A78A8A954819E220CEFBEBCE...)
The other one: A0B4C435650B6D86D618EFD10EDED34FD2AFF562 (https://metrics.torproject.org/rs.html#details/A0B4C435650B6D86D618EFD10EDED...)
here you can find my whole notices.log since the last reinstall: https://pastebin.com/RLTp7ZqJ
The Problem usually occures when i restart the PI after beeing shut down to long.
It is harder for tor to bootstrap when it is reinstalled, or when it has been off for a while, because it needs to download more data.
Tor is installed through the apt-get repository. I think it uses systemd
...
What could be the problem?
Are you using systemd, or some other startup notification system? Your relay could be failing to notify systemd that it has started. And then systemd is restarting it.
It looks like Tor never bootstraps, so systemd restarts it. You can confirm by checking your systemd logs.
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.
T
A big Part from my systemd daemon.log which maybe already shows the issue.
Thanks for your fast responses btw. Am 17.02.2018 um 01:53 schrieb teor:
On 17 Feb 2018, at 11:41, Paul <paul@roteserver.de mailto:paul@roteserver.de> wrote:
…
Both are no exits.
The error relay: A29D2A78A8A954819E220CEFBEBCE95D2FCFA54D (https://metrics.torproject.org/rs.html#details/A29D2A78A8A954819E220CEFBEBCE...)
The other one: A0B4C435650B6D86D618EFD10EDED34FD2AFF562 (https://metrics.torproject.org/rs.html#details/A0B4C435650B6D86D618EFD10EDED...)
here you can find my whole notices.log since the last reinstall: https://pastebin.com/RLTp7ZqJ
The Problem usually occures when i restart the PI after beeing shut down to long.
It is harder for tor to bootstrap when it is reinstalled, or when it has been off for a while, because it needs to download more data.
Tor is installed through the apt-get repository. I think it uses systemd
...
What could be the problem?
Are you using systemd, or some other startup notification system? Your relay could be failing to notify systemd that it has started. And then systemd is restarting it.
It looks like Tor never bootstraps, so systemd restarts it. You can confirm by checking your systemd logs.
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.
T
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi,
On 17 Feb 2018, at 12:26, Paul paul@roteserver.de wrote:
A big Part from my systemd daemon.log which maybe already shows the issue.
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
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.
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 <paul@roteserver.de mailto:paul@roteserver.de> wrote:
A big Part from my systemd daemon.log which maybe already shows the issue.
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
On 17 Feb 2018, at 14:03, Paul paul@roteserver.de wrote:
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.
You might want to check your log options.
Your last logs said you were logging at more than notice.
However it seems like the relay is working now.
Could it be working now because there is minimized load due to the new keys?
Yes. Your router probably can't deal with that many connections.
What should i do to reduce the load?
Only run one relay behind that router.
Decrease max bandwith
Use: MaxAdvertisedBandwidth 1 MBytes
can i somehow decrease max connections?
How many connections do both your relays have open when they fail? Use "netstat"to find out. You can not run a good relay with less than 7000 connections. Each relay needs to be able to connect to every other relay.
T
tor-relays@lists.torproject.org
-
Paul -
teor