I would like to confirm tor's behaviour when this happens:
Is there something listening on 185.92.223.3:8080?
No, there doesn't seem to be:
$ netstat -an -p tcp -f inet | grep LISTEN tcp 0 0 *.443 *.* LISTEN tcp 0 0 127.0.0.1.25 *.* LISTEN tcp 0 0 *.22 *.* LISTEN tcp 0 0 *.80 *.* LISTEN
A port scan of the server shows the tor port as closed...
$ nmap -sT tcj.me
Starting Nmap 7.01 ( https://nmap.org ) at 2017-04-01 09:59 CDT Nmap scan report for tcj.me (185.92.223.3) Host is up (0.15s latency). Not shown: 996 filtered ports PORT STATE SERVICE 22/tcp open ssh 80/tcp open http 443/tcp open https 8080/tcp closed http-proxy
Nmap done: 1 IP address (1 host up) scanned in 11.10 seconds
Is it this tor process, or another tor process?
Only have the one process running still...
$ ps aux | grep tor _tor 45694 0.0 23.1 111008 177576 ?? S Mon10AM 626:59.32 /usr/local/bin/tor
If it is this tor process, is tor still working as a relay despite the warnings?
I would have to say no. Using a program called pftop, I usually see Up States of 1000+ when the relay is going strong, right now I see 13. There is also no traffic on the server right now. However, I do show a single established connection on the tor port 8080, but I'm pretty sure its completely stagnant.
$ netstat -an -p tcp -f inet | grep ESTABLISHED tcp 0 0 185.92.223.3.8080 188.166.41.46.42469 ESTABLISHED tcp 0 0 185.92.223.3.35786 176.10.104.243.443 ESTABLISHED tcp 0 0 185.92.223.3.43470 80.127.107.179.443 ESTABLISHED tcp 0 36 185.92.223.3.22 204.112.151.27.51843 ESTABLISHED tcp 0 0 185.92.223.3.9593 62.210.92.11.9001 ESTABLISHED tcp 0 0 185.92.223.3.19380 185.30.166.37.6667 ESTABLISHED
I would be willing to try any patches you may have!
Thanks,
Tyler