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

Re: [tor-relays] SIGHUP causing obfs warning/disabling

To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-relays] SIGHUP causing obfs warning/disabling
From: Geoff Down <geoffdown@xxxxxxxxxxxx>
Date: Thu, 19 Jan 2017 02:46:49 +0000
Delivered-to: archiver@xxxxxxxx
Delivery-date: Wed, 18 Jan 2017 21:51:27 -0500
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=ndyEEe+Kuchd3IGJxwr1Ie9O94 Q=; b=ejeF1iVcmw1IQZPSF6tIF5RhBC07iA+qWFnSHlQlp149RdFsdA1rvaKp/b dyehOjcmitPDV3YyPq/VVQ+NwqVLLvW70Jn2gJy6GUwfbxb3twq5UZqnW8LE8rAf 3rr1H3QTcvXxzYuE+12KQJCfiGTILvptb6DmjHgKRQ5mbM+WA=
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=smtpout; bh=nd yEEe+Kuchd3IGJxwr1Ie9O94Q=; b=ILAeoDGadeaa2MMNVOvTSamNMgul1PO2sI 1HLvL2ck//WH9ODzQcxkbp7IYbHKEceoLWlUTdMvqFSa6bd84pcyAYbkzzZWbe8C qLcpVpxxU91nfCMxHZmmadsKypE5E8530+fYHqHU09RJxjhzx/esgL1WaGJ02bO/ M+EE7LcRE=
In-reply-to: <7A905E99-CF76-4F2F-A1E3-F09E46F5BBA2@gmail.com>
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>
References: <1484787614.3930943.852312456.2D8DF2BA@webmail.messagingengine.com> <F3D937BD-0295-4FE1-92C9-DBDAA5590C76@gmail.com> <1484793036.3948622.852368280.1FA113A5@webmail.messagingengine.com> <7A905E99-CF76-4F2F-A1E3-F09E46F5BBA2@gmail.com>
Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx
Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>

On Thu, Jan 19, 2017, at 02:33 AM, teor wrote:
> 
> > On 19 Jan 2017, at 13:30, Geoff Down <geoffdown@xxxxxxxxxxxx> wrote:

> > Then a HUP produced the same sequence (but a different PID), with no
> > sign of the lines you mention above regarding 'restart'.
> > The original obsfproxy process 17356 is still in the same state.
> 
> Is this error reproducible once the process 17356 is killed?

 In that case, after sending a HUP the transport was registered with no
 problem, just the normal messages to that effect.
After sending *another* HUP, I did indeed get
 Nothing changed for managed proxy '/usr/bin/obfsproxy' after HUP: not
 restarting

Where does that leave us? Cosmic rays?

-- 
http://www.fastmail.com - Choose from over 50 domains or use your own

_______________________________________________
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

References:
- [tor-relays] SIGHUP causing obfs warning/disabling
  - From: Geoff Down
- Re: [tor-relays] SIGHUP causing obfs warning/disabling
  - From: teor
- Re: [tor-relays] SIGHUP causing obfs warning/disabling
  - From: Geoff Down
- Re: [tor-relays] SIGHUP causing obfs warning/disabling
  - From: teor

Prev by Author: [tor-relays] Exit filtering Necto3 93.115.95.204
Next by Author: Re: [tor-relays] exitnodes blocking services
Previous by thread: Re: [tor-relays] SIGHUP causing obfs warning/disabling
Next by thread: Re: [tor-relays] SIGHUP causing obfs warning/disabling
Index(es):
- Author
- Thread