On Thu, May 16, 2019 at 06:56:10PM +0000, findmei wrote:
May 15 14:42:13.000 [warn] Unable to stat resolver configuration in '/etc/resolv.conf': Permission denied
This one is weird and unexpected. Your relay can't do any dns resolves of its own if it can't read that file. For a non-exit relay (which you appear to be), that's not so bad.
As for why that might happen, my first thought is some sort of apparmor permissions that intercept the file access attempt and block it.
May 15 14:49:13.000 [warn] HTTP status 307 ("Temporary Redirect") was unexpected while uploading descriptor to server '86.59.21.38:80'. Possibly the server is misconfigured?
This one is most likely something on your network trying to attack or censor or intercept your outgoing traffic. Maybe there is something that calls itself antivirus, or firewall, or web cleaner, or something like that? Or maybe your ISP or your country does something like that 'for' you automatically?
I try to chmod 777 /etc/resolv.conf for this warning " /etc/resolv.conf': Permission denied".But it didnt work it.And then i searched it on google for "HTTP status 307 ("Temporary Redirect")" .But i didn't find solution.Any suggestions?
/var/log/tor/notices.log => https://paste.ubuntu.com/p/JsPGdgFJyT/
A possible reason why the relay wasn't listed as Running was that there were three different relays running at that IP address in the past day, and Tor tries to limit to at most two relays per IP address.
Anyway, it looks like it is now listed.
--Roger