On Sun, Dec 10, 2017 at 9:45 PM, teor teor2345@gmail.com wrote:
On 11 Dec 2017, at 02:17, Aneesh Dogra lionaneesh@gmail.com wrote:
Hello Everyone,
I run a tor exit relay named "rippedlion". I was out for vacation past
few days and saw I had a 2 day downtime. I had a look at the logs and apparently /var/lib/tor got detected to be owned as <unknown>? How do I prevent this in future?
Snippet from notices.log:
Dec 08 06:54:57.000 [warn] Tried to establish rendezvous on non-OR
circuit with purpose Acting as rendevous (pending)
Dec 08 06:56:25.000 [warn] Tried to establish rendezvous on non-OR
circuit with purpose Acting as rendevous (pending)
Dec 08 07:00:21.000 [warn] /var/lib/tor is not owned by this user (root,
- but by <unknown> (112). Perhaps you are running Tor as the wrong user?
Dec 08 07:00:21.000 [err] Can't create/check datadirectory /var/lib/tor Dec 08 07:00:21.000 [err] Unable to update Ed25519 keys! Exiting.
tor thought it was running as root when it logged that message. Are you sure your tor process doesn't run as root? Do you have a User option in your torrc or torrc-defaults file? Does it correspond to user id 112?
Yes I *was* running tor as root and after the downtime changed it to a low
privileged user.
PS: I am now running tor; as a low privledged user that only has access
to /var/lib/tor and /var/log/tor.
I'm not sure what you mean here - have you changed the user that tor runs as since the downtime?
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
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays