> On 19 Jan 2017, at 12:00, Geoff Down <geoffdown@xxxxxxxxxxxx> wrote: > > Hi, > I sent a SIGHUP to the tor process after altering the torrc and got this > effect: > Jan 19 00:47:42.000 [notice] Tor 0.2.9.8 opening log file. > Jan 19 00:47:55.000 [warn] Server managed proxy encountered a method > error. (obfs3 Could not set up listener (0.0.0.0:xxxxx) for 'obfs3' > (Address already in use).) > Jan 19 00:47:55.000 [warn] Managed proxy at '/usr/bin/obfsproxy' failed > the configuration protocol and will be destroyed. > > It did it again when I restored the torrc and SIGHUPed again. Obfs3 is > still running and listening afaict: > tor 17356 0.0 0.2 49944 1736 ?? S 20Dec16 0:13.04 > /opt/local/Library/Frameworks/Python.... > Python 17356 tor 3u IPv4 0x02eb32a4 0t0 TCP *:xxxxx (LISTEN) > > Bug or !Bug ? This could be a bug in tor in pt_configure_remaining_proxies(), or it could be a bug in obfsproxy, or it could not be a bug. What are the ServerTransport* lines in your torrc, default torrc, and command-line? What are the info-level log lines around the lines you quoted? For example, do you see something like: Preparing managed proxy '%s' for restart. (If so, this could be a bug in proxy_prepare_for_restart().) Nothing changed for managed proxy '%s' after HUP: not restarting. T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
Attachment:
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays