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

Re: Server node stalls on unsuccessful socks listener change

To: or-talk@xxxxxxxxxxxxx
Subject: Re: Server node stalls on unsuccessful socks listener change
From: coderman <coderman@xxxxxxxxx>
Date: Tue, 21 Aug 2007 16:24:14 -0700
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Tue, 21 Aug 2007 19:24:23 -0400
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Edh9rRtTXkyovt+pbRR3Y5KpoP6wYnyujDqfBm+EsWhE8IOxtxtzHTdNbf7clejE1l/VYIZcC9z+XhAD9Tmj1E3SxwmtZs4ObLMQb8JjD4YJ16y01LEOz8xLTCFpTHVt3HWY35FgkquR+PbND126nwK2iysIUZrOFiUVFoFckbw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lh8lct1Le0wbTBdYXOrgwaZAHe9dgg3UHVVOmWu1DqTlRkwqQz/WXJS2UTLrMLpneC4MCHETGF4AVE2Y3f7MYkYY4IdyQQQ/VJKlp849w8TM5SW34e2MVrYiP9UBXkOTHnhJctKa+0XxEnvYuTZd4Bq5Lt282oWCeX8NDozOSRs=
In-reply-to: <4ef5fec60708211542y765e9d1cu8eac3bbe93a2aa74@xxxxxxxxxxxxxx>
References: <1187679771.6136.35.camel@mkraus-laptop> <4ef5fec60708210254q58ed226cw770910ef59e0b5a3@xxxxxxxxxxxxxx> <4ef5fec60708211542y765e9d1cu8eac3bbe93a2aa74@xxxxxxxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx

On 8/21/07, coderman <coderman@xxxxxxxxx> wrote:
> ... i did not set a ORListenAddress.  when i
> changed this and tried to reload the config the server died.

this appears to be a linux'ism and applies only when going from an
unspecified bind (0.0.0.0) to a specified bind to an address on the
host.  changing specified bind addresses works as expected.

i'm not sure what the correct workaround is for this; i can't seem to
find any good documentation on this behavior and how to avoid it.
SO_REUSEADDR is getting set but apparently behaves "weirdly" on
sockets with unspecified binds.

perhaps some on list has dealt with this before...

best regards,

Follow-Ups:
- Re: Server node stalls on unsuccessful socks listener change
  - From: coderman

References:
- Server node stalls on unsuccessful socks listener change
  - From: BlueStar88
- Re: Server node stalls on unsuccessful socks listener change
  - From: coderman
- Re: Server node stalls on unsuccessful socks listener change
  - From: coderman

Prev by Author: Re: Server node stalls on unsuccessful socks listener change
Next by Author: Re: Server node stalls on unsuccessful socks listener change
Previous by thread: Re: Server node stalls on unsuccessful socks listener change
Next by thread: Re: Server node stalls on unsuccessful socks listener change
Index(es):
- Author
- Thread