Re: [tor-relays] assign_to_cpuworker failed. Ignoring.

[Vinícius Zavam <egypcio@xxxxxxxxxxxxxx>]

2016-11-01 12:03 GMT-03:00, teor <teor2345@xxxxxxxxx>:
>
>> On 2 Nov. 2016, at 01:56, Felix <zwiebel@xxxxxxxxxxxxxxxx> wrote:
>> ...
>>
>> My log says:
>> Oct 19 01:04:52.527 [notice] Read configuration file
>> "/usr/local/etc/tor/torrc".
>> Oct 19 01:04:52.566 [notice] Opening OR listener on 0.0.0.0:1234
>> for
>> ORPort 443 NoListen
>> ORPort 1234 NoAdvertise
>> My Tor finds 0.0.0.0 and looks further out ...
>>
>> I see yours telling:
>> Oct 31 22:48:44.752 [notice] Opening OR listener on a.b.c.d:9021
>>
>> Hm. Can you please share your torrc line for the "ORPort
>> [address:]PORT|auto [flags]" directive? Can you give an example which is
>> your a.b.c.d, is it the external or a local (lo#) and how do you set
>> NoListen/NoAdvertise ? I want to avoid Tor guessing the ip.
>
> To set the public IPv4 address in your descriptor, use Address:
> Address IPv4
> Otherwise, Tor will guess your address.
>
> To set the public IPv6 address in your descriptor, use the first IPv6
> ORPort:
> ORPort [IPv6]:Port
> Otherwise, Tor will not advertise your IPv6 address.
>
> To set an ORPort on an address that's on the host, use:
> ORPort IP:Port
>
> To set a public ORPort on an address that's on a middlebox, use:
> ORPort IP:Port NoListen
>
> To set a private ORPort on an address that's not public, use:
> ORPort IP:Port NoAdvertise
>

hey felix,
teor was faster than me and I think he was able to clarify your needs.

I would like to add just small notes ...

use "OutboundBindAddress". it can be configured twice, one time for
your v4 address, and the other one for your v6 (if you need/have it).
the tor(1) manpage can give you more details about it.

you can also use "ORPort" and "DirPort" to: 1) pass IPv4Only and/or
IPv6Only to these options too. DirPort only supports v4, so don't
bother forcing it there, and 2) if you want to run Tor with
unprivileged user and use low (well know) ports, like 21, 80, 22, 110,
443, usw.

it might not be related to your issue, but looks to be a good
practice: as you told that you run around 7 relays, please list your
relays' fingerprints on "MyFamily". good to see you are not running
your ports with default values too! :>

I hope that we could give you hints on how to solve your issue, and
will be happy to hear that you was able to close your ticket. for your
next issues related to any BSD system, please CC the torbsd ml too
(http://lists.nycbug.org/mailman/listinfo/tor-bsd)... but do not stop
posting to the official tor-dev@, or tor-relay@ ml and using Tor's
trac.

PS: the relay keeps running w/o any unexpected warning msg...

# grep -i -E '(warn|jump|cpu)' /var/log/tor/notice.log_r0289
Oct 31 22:48:44.633 [notice] Tor can't help you if you use it wrong!
Learn how to be safe at
https://www.torproject.org/download/download#warning

# tail -n3 /var/log/tor/notice.log_r0289
Nov 01 13:51:24.000 [notice] Heartbeat: Tor's uptime is 15:00 hours,
with 18 circuits open. I've sent 252.31 MB and received 262.24 MB.
Nov 01 13:51:24.000 [notice] Circuit handshake stats since last time:
41/41 TAP, 193/193 NTor.
Nov 01 13:51:24.000 [notice] Since startup, we have initiated 0 v1
connections, 0 v2 connections, 0 v3 connections, and 2163 v4
connections; and received 0 v1 connections, 113 v2 connections, 102 v3
connections, and 3438 v4 connections.


MFG,

-- 
Vinícius Zavam
keybase.io/egypcio/key.asc
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays