[tor-relays] Relay - Conflicting data (Atlas != log)

[Mark Jamsek]

I am trying to run a restricted exit relay on FreeBSD 9.2-RELEASE in a 
jail. I tested it out a couple days ago on an old(er) box, and 
everything worked fine: 
https://atlas.torproject.org/#details/A5CA10E554124289C1B42B4CCA68F0CACFE503DC

Decided to get it running on a fresher rig, all appears well according 
to system data:

$ tail notices.log
Dec 02 15:49:31.000 [notice] Bootstrapped 90%: Establishing a Tor circuit.
Dec 02 15:49:34.000 [notice] Tor has successfully opened a circuit. 
Looks like client functionality is working.
Dec 02 15:49:34.000 [notice] Bootstrapped 100%: Done.
Dec 02 15:49:34.000 [notice] Now checking whether ORPort 
110.146.133.98:9001 and DirPort 110.146.133.98:9030 are
reachable... (this may take up to 20 minutes --
look for log messages indicating success)
Dec 02 15:49:40.000 [notice] Self-testing indicates your ORPort is 
reachable from the outside. Excellent. Publishing server
descriptor.
Dec 02 15:49:59.000 [notice] Performing bandwidth self-test...done.
Dec 02 15:50:33.000 [notice] Self-testing indicates your DirPort is 
reachable from the outside. Excellent.
Dec 02 15:50:33.000 [notice] Not advertising DirPort (Reason: 
AccountingMax enabled)
Dec 02 15:51:50.000 [notice] Your DNS provider gave an answer for 
"rmus4fklislhf", which is not supposed to exist.
Apparently they are hijacking DNS failures. Trying to correct for this. 
We've noticed 1 possibly bad address so far.
Dec 02 21:49:39.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 
0 circuits open. I've sent 946 kB and received 7.09 MB.

$ ps -aux |grep tor
USER	 PID	%CPU %MEM VSZ	RSS   TT  STAT STARTED TIME    COMMAND
torrelay 86844  0.0  12.1 60532 52796 ??  IJ   3:49PM  0:33.50 tor 
--RunAsDaemon 1

Apart from the DNS hijacking entry(?), Tor is apparently up and running. 
However, according to Atlas, it is not: 
https://atlas.torproject.org/#details/EE16D7A4FBCF6494FEE75C856D76782295CB9DC4
(forgot to backup tor key; hence, the different print)

Not sure what to think or do. Is it advertised on Atlas as false due to 
this entry: [notice] Not advertising DirPort (Reason: AccountingMax enabled)

Or is one of the two sources (system or Atlas) wrongly reporting? Thank you.

-- 
01101101 01100001 01110010 01101011