Hello,
I have setup a tor exit but it seems like that is shutsdown after x hours. I can not find anything in the logs. Anyone knows how this might happen?
Regards,
Neelix fingerprint: 32A6 5D7A 955C 546C 0E9B F559 EB09 D028 36A3 79E
On Fri, Feb 01, 2019 at 07:11:51AM +0100, Neelix wrote:
I have setup a tor exit but it seems like that is shutsdown after x hours. I can not find anything in the logs. Anyone knows how this might happen?
Have you even found Tor's log file (if there is any)? What OS/distro are you using? Are you using your distro's package management system's Tor package?
In case you did find Tor's log file, can you find a line in it that looks like this?:
[notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
On 2/1/19 10:39 AM, Jonathan Marquardt wrote:
On Fri, Feb 01, 2019 at 07:11:51AM +0100, Neelix wrote:
I have setup a tor exit but it seems like that is shutsdown after x hours. I can not find anything in the logs. Anyone knows how this might happen?
Have you even found Tor's log file (if there is any)? What OS/distro are you using? Are you using your distro's package management system's Tor package?
In case you did find Tor's log file, can you find a line in it that looks like this?:
[notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Yes I have that line. There isn't anything special in the log files. I'm running Debian 8 im using the distros Tor package.
On Fri, Feb 01, 2019 at 11:13:43AM +0100, Neelix wrote:
Yes I have that line. There isn't anything special in the log files. I'm running Debian 8 im using the distros Tor package.
OK. By "shutdown", you mean that the Tor service terminated, right? Or do you mean that the entire machine actually shut down?
On 2/1/19 11:25 AM, Jonathan Marquardt wrote:
On Fri, Feb 01, 2019 at 11:13:43AM +0100, Neelix wrote:
Yes I have that line. There isn't anything special in the log files. I'm running Debian 8 im using the distros Tor package.
OK. By "shutdown", you mean that the Tor service terminated, right? Or do you mean that the entire machine actually shut down?
The entire machine shuts down. Very strange.
On Fri, Feb 01, 2019 at 11:29:25AM +0100, Neelix wrote:
The entire machine shuts down. Very strange.
Then I'd doubt that it even has anything to do with Tor. Have a look at /var/log/syslog and see if there's anything there that might be helpful.
On 2/1/19 11:31 AM, Jonathan Marquardt wrote:
On Fri, Feb 01, 2019 at 11:29:25AM +0100, Neelix wrote:
The entire machine shuts down. Very strange.
Then I'd doubt that it even has anything to do with Tor. Have a look at /var/log/syslog and see if there's anything there that might be helpful.
Thats why I was thinking but the server worked fine before I was running tor. As you can see there are no strange things int he syslog. The server went down after 23:36:41
Jan 31 23:34:40 tor tor[1064]: Jan 31 23:34:40.550 [notice] Opening OR listener on 0.0.0.0:9001 Jan 31 23:34:40 tor tor[1064]: Jan 31 23:34:40.550 [notice] Opened OR listener on 0.0.0.0:9001 Jan 31 23:34:40 tor tor[1064]: Jan 31 23:34:40.551 [notice] Opening OR listener on [2a06:1700:0:b::44cb:d9]:9050 Jan 31 23:34:40 tor tor[1064]: Jan 31 23:34:40.551 [notice] Opened OR listener on [2a06:1700:0:b::44cb:d9]:9050 Jan 31 23:34:40 tor tor[1064]: Jan 31 23:34:40.551 [notice] Opening Directory listener on 0.0.0.0:80 Jan 31 23:34:40 tor tor[1064]: Jan 31 23:34:40.552 [notice] Opened Directory listener on 0.0.0.0:80 Jan 31 23:34:54 tor systemd[1]: Started Anonymizing overlay network for TCP. Jan 31 23:36:40 tor systemd[1]: Starting Cleanup of Temporary Directories... Jan 31 23:36:41 tor systemd[1]: Started Cleanup of Temporary Directories.
Feb 1 08:00:55 tor rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="525" x-info="http://www.rsyslog.com"] start <----- Me booting up the server after i found out it was down again Feb 1 08:00:55 tor rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Regards,
Neelix
fingerprint: 32A6 5D7A 955C 546C 0E9B F559 EB09 D028 36A3 79E0 xmpp: neelix@yourdata.forsale
On Fri, Feb 01, 2019 at 11:29:25AM +0100, Neelix wrote:
The entire machine shuts down. Very strange.
Two possibilities to explore:
(1) The machine is more fragile than you think, and the CPU load from the Tor process pushed it over the edge, so one of its automatic hardware sensors shut it off to protect it.
(2) Some admin on your local network noticed a bunch of weird traffic, or even just a bunch of traffic, and thought they were helping by turning it off.
--Roger
On 2/1/19 11:48 AM, Roger Dingledine wrote:
On Fri, Feb 01, 2019 at 11:29:25AM +0100, Neelix wrote:
The entire machine shuts down. Very strange.
Two possibilities to explore:
(1) The machine is more fragile than you think, and the CPU load from the Tor process pushed it over the edge, so one of its automatic hardware sensors shut it off to protect it.
(2) Some admin on your local network noticed a bunch of weird traffic, or even just a bunch of traffic, and thought they were helping by turning it off.
--Roger
Ah! This might be the problem. Tor is almost using 100% of the CPU. Is there a way to reduce the CPU usage? Or should I upgrade the server?
For what it's worth, I previously had similar behaviour.
It turned out it was against the host's AUP (I hadn't spotted it in there), and when they detected it they automatically shut the system off (it was an OpenVZ slice so fairly easy for them to monitor).
On Fri, Feb 1, 2019 at 11:02 AM Neelix neelix@privacy.farm wrote:
On 2/1/19 11:48 AM, Roger Dingledine wrote:
On Fri, Feb 01, 2019 at 11:29:25AM +0100, Neelix wrote:
The entire machine shuts down. Very strange.
Two possibilities to explore:
(1) The machine is more fragile than you think, and the CPU load from the Tor process pushed it over the edge, so one of its automatic hardware sensors shut it off to protect it.
(2) Some admin on your local network noticed a bunch of weird traffic, or even just a bunch of traffic, and thought they were helping by turning it off.
--Roger
Ah! This might be the problem. Tor is almost using 100% of the CPU. Is there a way to reduce the CPU usage? Or should I upgrade the server?
-- Regards,
Neelix
fingerprint: 32A6 5D7A 955C 546C 0E9B F559 EB09 D028 36A3 79E0 xmpp: neelix@yourdata.forsale
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Its allowed by the host. So that can't be the problem.
On 2/1/19 12:06 PM, Ben Tasker wrote:
sly had similar behaviour.
It turned out it was against the host's AUP (I hadn't spotted it in there), and when th
On Feb 1, 2019, at 03:01, Neelix neelix@privacy.farm wrote:
Ah! This might be the problem. Tor is almost using 100% of the CPU. Is there a way to reduce the CPU usage? Or should I upgrade the server?
I would immediately suspect an overheating CPU. If the CPU cooler fan is defective, or if the heatsink compound is dried out, then the machine can shut down precipitously with no log entries.
If you can open it up, make sure that the CPU heatsink fan spins freely and that the heatsink isn't clogged up with dust.
If you can't open it (or are just naturally voyeuristic), on a debian-like distro you can follow these instructions to monitor the CPU temp:
https://askubuntu.com/questions/15832/how-do-i-get-the-cpu-temperature
--Ron
tor-relays@lists.torproject.org
-
Ben Tasker -
Jonathan Marquardt -
Neelix -
Roger Dingledine -
ronqtorrelays＠risley.net