[Tor-BSD] warnings on a freeBSB exit

[pa011]

Am 05.12.2016 um 00:51 schrieb teor:
> 
>> On 5 Dec. 2016, at 10:37, pa011 <pa011 at web.de> wrote:
>>
>> I try to get more involved with FreeBSD and currently do tests on a very small 256MB RAM vps.
>>
>> arm - freeBSD (FreeBSD 10.3-RELEASE-p11)   Tor 0.2.8.9 (recommended) 
>>
>> no firewall in place, nore on the relay or on ISP side
>>
>> tcpdump is showing traffic both way on port 9001
>>
>> telnet proofs that the port 9001 is reachable
>>
>> why do I get the warnings below so that the exit is not showing up?
>>
>> [WARN] Your server (x.x.x.x:9030) has not managed to confirm that its DirPort is reachable. Relays do not publish descriptors until their
>>   ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
>> [WARN] Your server (x.x.x.x:9001) has not managed to confirm that its ORPort is reachable. Relays do not publish descriptors until their
>>   ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
> 
> Your relay can't confirm it is reachable from the outside, so it won't
> join the tor network.
> 
> Where are you telnetting from?

I am telnetting from different source/server

> Have you tried elsewhere on the Internet?

What do you mean  - no ?

> Perhaps it's dropping connections due to low memory or file descriptors?
> You could try with 512MB, which is the minimum to run Tor. An Exit needs
> about 768MB - 1GB.

Will increase to 512MB tomorrow

have  exits running well on 512MB for months (traffic 500GB/day)


> 
> What does your relay log about its address when it first starts up?

Dec 04 19:14:46.000 [notice] Tor 0.2.8.9 opening log file.
Dec 04 19:14:46.471 [warn] OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled$
Dec 04 19:14:46.499 [notice] Tor v0.2.8.9 running on FreeBSD with Libevent 2.0.22-stable, OpenSSL 1.0.1s-freebsd and Zlib 1.2.8.
Dec 04 19:14:46.499 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Dec 04 19:14:46.499 [notice] Read configuration file "/usr/local/etc/tor/torrc".
Dec 04 19:14:46.506 [notice] Based on detected system memory, MaxMemInQueues is set to 256 MB. You can override this by setting MaxMemInQueues by hand.
Dec 04 19:14:46.507 [warn] Being a directory cache (default) with less than DIRCACHE_MIN_MB_BANDWIDTH MB of memory is not recommended and may consume most of$
Dec 04 19:14:46.509 [notice] Opening Control listener on 127.0.0.1:9051
Dec 04 19:14:46.509 [notice] Opening OR listener on 0.0.0.0:9001
Dec 04 19:14:46.509 [notice] Opening Directory listener on 0.0.0.0:9030
Dec 04 19:14:46.000 [notice] Not disabling debugger attaching for unprivileged users.
Dec 04 19:14:46.000 [notice] Parsing GEOIP IPv4 file /usr/local/share/tor/geoip.
Dec 04 19:14:46.000 [notice] Parsing GEOIP IPv6 file /usr/local/share/tor/geoip6.
Dec 04 19:14:46.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from n$
Dec 04 19:14:46.000 [notice] We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks accelerat$
Dec 04 19:14:46.000 [notice] Your Tor server's identity key fingerprint is
Dec 04 19:14:46.000 [notice] Bootstrapped 0%: Starting
Dec 04 19:14:50.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Dec 04 19:14:51.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
Dec 04 19:15:24.000 [notice] New control connection opened from 127.0.0.1.
Dec 04 19:15:38.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Dec 04 19:15:38.000 [notice] Read configuration file "/usr/local/etc/tor/torrc".
Dec 04 19:15:38.000 [warn] Being a directory cache (default) with less than DIRCACHE_MIN_MB_BANDWIDTH MB of memory is not recommended and may consume most of$
Dec 04 19:15:38.000 [notice] Tor 0.2.8.9 opening log file.
Dec 04 19:16:12.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Dec 04 19:16:12.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Dec 04 19:16:12.000 [notice] Bootstrapped 100%: Done
Dec 04 19:16:12.000 [notice] Now checking whether ORPort x.x.x.x:9001 and DirPort x.x.x.x:9030 are reachable... (this may take up to 20 minutes 

> (Please don't redact the addresses. It makes it really hard to help you.
> We need to know if they are the same or different.)
> 
> You could also try setting the Address torrc option to the IPv4 address
> of the VPS, 
sorry - what and how please ?

but that will only help if tor is guessing the wrong address
> on the VPS.
> 
>> [WARN] Being a directory cache (default) with less than DIRCACHE_MIN_MB_BANDWIDTH MB of memory is not recommended and may consume most of the available resources, consider disabling this functionality by setting the DirCache option to 0                                            
> 
> That's an unhelpful message, it's meant to read "300 MB".
> Logged as:
> https://trac.torproject.org/projects/tor/ticket/20887
> 
> T
> 
>> torrc:
>>
>> ExitRelay 1
>> RunAsDaemon 1
>> Log notice file /var/log/tor/log
>> ORPort 9001
>> ControlPort 9051
>> CookieAuthentication 0
>> HashedControlPassword xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> RelayBandwidthRate 8000 KB
>> RelayBandwidthBurst 10000 KB
>> DirPort 9030
>> CellStatistics 1
>> DirReqStatistics 1
>> EntryStatistics 1
>> ExitPortStatistics 1
>> ExtraInfoStatistics 1
>> HiddenServiceStatistics 1
>> SocksPort 0
>> SocksPolicy reject *
>> DisableDebuggerAttachment 0
>>
>>
>> Thanks for your help
>> Kind regards
>> Paul
> 
> T
>