[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-relays] SIGHUP causing obfs warning/disabling

To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: [tor-relays] SIGHUP causing obfs warning/disabling
From: Geoff Down <geoffdown@xxxxxxxxxxxx>
Date: Thu, 19 Jan 2017 01:00:14 +0000
Delivered-to: archiver@xxxxxxxx
Delivery-date: Wed, 18 Jan 2017 20:00:36 -0500
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.net; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= mesmtp; bh=PM6SY6/QWNzE149dyCQ5QaILHvU=; b=H12IQtcjoahMupB8Fg02e 5fAytJxlpkqs+kqss2n7N6JlSWBLUlIRDeX0DPu4vbNL0qIv1DChbUAWB9ssMb1W FT+QBjTQA3B1Ttd9bDXOFPCZbpNqI65eMNM7OcQFlC0tNfVFxeqXIVASIVxUerqe /FZqSjswFUouOYs/wBbWAQ=
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=smtpout; bh=PM6SY6/QWNzE149dyCQ5QaILH vU=; b=MDuetrrEKWwk2MGvNfrOa/Oi0IynHYZTT6SuXh1x5OdOlG+Pd85ahKWd+ SKQcKdowNo4k3Tw3vl0YXCjpZKMmpXdv5nU8+v8BEJC2Sm9ZhC6IiaVfmZRoh4Gk lFqBe/h26rJL+sid3Qh0ds39jJ3pjIiciqPytVIsaSU9CKuIjo=
List-archive: <http://lists.torproject.org/pipermail/tor-relays/>
List-help: <mailto:tor-relays-request@lists.torproject.org?subject=help>
List-id: "support and questions about running Tor relays \(exit, non-exit, bridge\)" <tor-relays.lists.torproject.org>
List-post: <mailto:tor-relays@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=unsubscribe>
Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx
Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>

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 ?

GD

-- 
http://www.fastmail.com - mmm... Fastmail...

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Follow-Ups:
- Re: [tor-relays] SIGHUP causing obfs warning/disabling
  - From: teor

Prev by Author: Re: [tor-relays] Disparity between download and upload traffic
Next by Author: Re: [tor-relays] SIGHUP causing obfs warning/disabling
Previous by thread: [tor-relays] Good Bad ISP - update required
Next by thread: Re: [tor-relays] SIGHUP causing obfs warning/disabling
Index(es):
- Author
- Thread