[Spread-users] INET unable to bind to port - force kill?

[George Schlossnagle]

I'll let someone else comment on restarting spread, but you shouldn't ned to
restart apache.  mod_log_spread should try to connect (once) on every
request until it succeeds.
Errors that you see after the spread daemon is restarted are likely from
children who haven't yet served a request since the time of failure.  They
will attempt to multicast (to the now dead connection), fail, log an error,
attempt to reconnect, send the same message again (and this time succeed).


George

----- Original Message -----
From: "Abe Scwartz" <sloween at hotmail.com>
To: <spread-users at lists.spread.org>
Sent: Thursday, July 26, 2001 2:44 PM
Subject: [Spread-users] INET unable to bind to port - force kill?


> All -
>
> When spread dies, I'd like to be able to kill it and restart it using
> something like daemontools. The problem is, spread seems to hold on to the
> port for a while. I've tried removing /tmp/4803 and force-killing all the
> processes, but it still holds on to the port. fuser/netstat are of little
> help.
>
> I'm using mod_log_spread, and my best guess is that they are holding the
> release of the port up even after spread has died.
>
> The end result is, when spread dies, it takes about 45 seconds to bring it
> back up - and then apache has to be restarted. I'd like to use daemontools
> to reduce this to a few seconds.
>
> Is there a more graceful way to accomplish this? Or perhaps someone has
had
> a better experience with keeping spread from dying? The process either
dies,
> or I get the dreaded 'SP multicast' error.
>
> Thanks again!
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>
>
>
> _______________________________________________
> spread-users mailing list
> spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users
>