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