On 22 Jun 2017, at 04:38, Alan tor-relay@clutterbuck.uk wrote:
thanks for running an exit.
Alan:
I've started to see my Exit node restart itself.
are you talking about tor daemon / process restarts or entire host restarts?
How often does tor restart? Does it always restart right after it is relaunched?
I guess you run a RPM based distro. I do not think that the openssl message has anything to do with the restarts. What does your syslog (/var/log/messages) say? any out-of-memory kills?
syslog says it failed but didn't give a reason.
Jun 21 03:07:01 vps110165 systemd: Reloaded Anonymizing overlay network for TCP (multi-instance master). Jun 21 03:07:01 vps110165 systemd: Reloaded Anonymizing overlay network for TCP. Jun 21 03:07:02 vps110165 systemd: tor.service: main process exited, code=exited, status=1/FAILURE Jun 21 03:07:02 vps110165 systemd: Unit tor.service entered failed state. Jun 21 03:07:02 vps110165 systemd: tor.service failed. Jun 21 03:07:03 vps110165 systemd: tor.service holdoff time over, scheduling restart. Jun 21 03:07:03 vps110165 systemd: Starting Anonymizing overlay network for TCP…
Is this also what you see when you run: systemctl status tor.service
Jun 21 03:07:03.000 [warn] Fixing permissions on directory /var/lib/tor Jun 21 03:07:03.000 [notice] We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks accelerated support for the NIST P-224 and P-256 groups. Building openssl with such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) would make ECD H much faster.
Are these the last entries in the tor log?
What do you see when you run: journalctl -xn just after tor has exited?
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------