> > This seems to be an internal state management issue. > I have opened ticket #21810 to track it. > https://trac.torproject.org/projects/tor/ticket/21810 > > I would like to confirm tor's behaviour when this happens: > > Is there something listening on 185.92.223.3:8080? > Is it this tor process, or another tor process? > If it is this tor process, is tor still working as a relay despite the > warnings? >
For comparison, some stats while the relay server is running correctly... $ netstat -an -p tcp -f inet | grep LISTEN tcp 0 0 127.0.0.1.25 *.* LISTEN tcp 0 0 *.22 *.* LISTEN tcp 0 0 *.443 *.* LISTEN tcp 0 0 185.92.223.3.8080 *.* LISTEN tcp 0 0 *.80 *.* LISTEN $ netstat -an -p tcp -f inet | grep ESTABLISHED | wc -l 1356 $ ps aux | grep _tor _tor 75460 12.8 24.4 120976 187772 ?? S Sat11AM 60:50.02 /usr/local/bin/tor If there are more prudent tests/commands that would provide more information, please let me know! Thanks, Tyler _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays