On 09/07/2010 11:01 PM, Roger Hoover wrote:
> Hi Marco,
>
> This looks like a case that I missed.  I need to look more closely at why
> it's happening so see if it requires a fundamental change to way sockets are
> handled.  The current implementation doesn't close the socket when all the
> processes are stopped unless a group-level stop command was issued.  The
> idea here was to support graceful restarts.  If you have a single FCGI
> process and want to restart it, should the FCGI socket get torn down and
> recreated?  If so, there will be a small amount of time where web clients
> are getting errors while the socket is down.  I may have to change it to
> always tear down the socket when the number of processes hit zero which
> would require someone to always run at least two copies if you want graceful
> restart.
>
> I'll keep you posted on what I find out.
>
> Thanks,
>
> Roger

Hi Roger!

The idea to recycle sockets , also for allow graceful restarts is valuable.

But at the moment it seems that as you said the sockets are not turn 
down, and just looking at the exception thrown - I've not looking at the 
code yet sorry -

> 2010-09-04 10:05:53,366 INFO Creating socket tcp://127.0.0.1:10005
>> Traceback (most recent call last):

>  File "/usr/lib/python2.6/site-packages/supervisor/process.py", line
>> 694, in __init__
>>     raise ValueError('Could not create FastCGI socket %s: %s' %
>> (self.socket_manager.config(), e))
>> ValueError: Could not create FastCGI socket tcp://127.0.0.1:10005:
>> [Errno 98] Address already in use


svd is trying to re-create a socket binding it to the same tcp address:port.
It's stepping on its toes , because the tcp address is already bind!

In order to recycle it- sorry speaking again without looking at the code 
- it should not try to create a new socket or whatsoever it does that 
implies to re-create the socket !

Anyway, I've switched to use local (i.e. unix) sockets and reloading 
occurs without problems.

Thank you for your support.

-- 
Marco Vittorini Orgeas
_______________________________________________
Supervisor-users mailing list
[email protected]
http://lists.supervisord.org/mailman/listinfo/supervisor-users

Reply via email to