Wells, Bradford | 8 Sep 19:11 2011

mount point already configured. skip. error

I have a python application running under uWSGI 0.9.9.1 under emperor mode.  The application fails to respond after its config file is touched to trigger an application reload. 

If I touch a config file I get the following in the logs:

touch emperor.ini
Wed Sep  7 22:40:56 2011 - received message 1 from emperor
...gracefully killing workers...
Gracefully killing worker 1 (pid: 3224)...
Respawned uWSGI worker 1 (new pid: 3250)
added /var/www/ERP/Application/ to pythonpath.
mountpoint  already configured. skip.

<request from browser>

DAMN ! worker 1 (pid: 3250) died :( trying respawn ...
Respawned uWSGI worker 1 (new pid: 3251)
added /var/www/ERP/Application/ to pythonpath.
mountpoint  already configured. skip.


The config setup is available at https://gist.github.com/1202034

Thanks. 
_______________________________________________
uWSGI mailing list
uWSGI@...
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
Roberto De Ioris | 8 Sep 19:09 2011
Picon

Re: mount point already configured. skip. error


> I have a python application running under uWSGI 0.9.9.1 under emperor
> mode.  The application fails to respond after its config file is touched
> to trigger an application reload.
>
> If I touch a config file I get the following in the logs:
>
> touch emperor.ini
> Wed Sep  7 22:40:56 2011 - received message 1 from emperor
> ...gracefully killing workers...
> Gracefully killing worker 1 (pid: 3224)...
> Respawned uWSGI worker 1 (new pid: 3250)
> added /var/www/ERP/Application/ to pythonpath.
> mountpoint  already configured. skip.
>
> <request from browser>
>
> DAMN ! worker 1 (pid: 3250) died :( trying respawn ...
> Respawned uWSGI worker 1 (new pid: 3251)
> added /var/www/ERP/Application/ to pythonpath.
> mountpoint  already configured. skip.
>
>
> The config setup is available at https://gist.github.com/1202034
>
>

Do not daemonize in emperor mode.

Use logto instead of daemonize

--

-- 
Roberto De Ioris
http://unbit.it
Wells, Bradford | 8 Sep 19:29 2011

Re: mount point already configured. skip. error

Switching to logto did not resolve the issue. With further experimentation I've found that removing lazy mode does, but that opens a separate problem for me. 

I have a python application running under uWSGI 0.9.9.1 under emperor
mode.  The application fails to respond after its config file is touched
to trigger an application reload.

If I touch a config file I get the following in the logs:

touch emperor.ini
Wed Sep  7 22:40:56 2011 - received message 1 from emperor
...gracefully killing workers...
Gracefully killing worker 1 (pid: 3224)...
Respawned uWSGI worker 1 (new pid: 3250)
added /var/www/ERP/Application/ to pythonpath.
mountpoint  already configured. skip.

<request from browser>

DAMN ! worker 1 (pid: 3250) died :( trying respawn ...
Respawned uWSGI worker 1 (new pid: 3251)
added /var/www/ERP/Application/ to pythonpath.
mountpoint  already configured. skip.


The config setup is available at https://gist.github.com/1202034



Do not daemonize in emperor mode.

Use logto instead of daemonize


--
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
uWSGI-FfzAktRlpg7/cILp9QSAqw@public.gmane.org
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


_______________________________________________
uWSGI mailing list
uWSGI@...
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
Roberto De Ioris | 8 Sep 19:36 2011
Picon

Re: mount point already configured. skip. error


> Switching to logto did not resolve the issue. With further experimentation
> I've found that removing lazy mode does, but that opens a separate problem
> for me.
>
> I have a python application running under uWSGI 0.9.9.1 under emperor
> mode.  The application fails to respond after its config file is touched
> to trigger an application reload.
>
> If I touch a config file I get the following in the logs:
>
> touch emperor.ini
> Wed Sep  7 22:40:56 2011 - received message 1 from emperor
> ...gracefully killing workers...
> Gracefully killing worker 1 (pid: 3224)...
> Respawned uWSGI worker 1 (new pid: 3250)
> added /var/www/ERP/Application/ to pythonpath.
> mountpoint  already configured. skip.
>
> <request from browser>
>
> DAMN ! worker 1 (pid: 3250) died :( trying respawn ...
> Respawned uWSGI worker 1 (new pid: 3251)
> added /var/www/ERP/Application/ to pythonpath.
> mountpoint  already configured. skip.
>
>
> The config setup is available at https://gist.github.com/1202034
>
>
>
> Do not daemonize in emperor mode.
>
> Use logto instead of daemonize
>
>

This could be related to bug #43 (alreayd fixed in tip).

Can you try the current mercurial tip ?

--

-- 
Roberto De Ioris
http://unbit.it
Wells, Bradford | 8 Sep 19:50 2011

Re: mount point already configured. skip. error

>> Switching to logto did not resolve the issue. With further experimentation
>> I've found that removing lazy mode does, but that opens a separate problem
>> for me.
>> 
>> I have a python application running under uWSGI 0.9.9.1 under emperor
>> mode.  The application fails to respond after its config file is touched
>> to trigger an application reload.
>> 
>> If I touch a config file I get the following in the logs:
>> 
>> touch emperor.ini
>> Wed Sep  7 22:40:56 2011 - received message 1 from emperor
>> ...gracefully killing workers...
>> Gracefully killing worker 1 (pid: 3224)...
>> Respawned uWSGI worker 1 (new pid: 3250)
>> added /var/www/ERP/Application/ to pythonpath.
>> mountpoint  already configured. skip.
>> 
>> <request from browser>
>> 
>> DAMN ! worker 1 (pid: 3250) died :( trying respawn ...
>> Respawned uWSGI worker 1 (new pid: 3251)
>> added /var/www/ERP/Application/ to pythonpath.
>> mountpoint  already configured. skip.
>> 
>> 
>> The config setup is available at https://gist.github.com/1202034
>> 
>> 
>> 
>> Do not daemonize in emperor mode.
>> 
>> Use logto instead of daemonize
>> 
>> 
> 
> This could be related to bug #43 (alreayd fixed in tip).
> 
> Can you try the current mercurial tip ?
> 
> 
> -- 
> Roberto De Ioris
> http://unbit.it
> _______________________________________________
> uWSGI mailing list
> uWSGI@...
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

That fixed the issue. Thanks!
Damjan | 8 Sep 22:22 2011
Picon

Re: [ANNOUNCE] uWSGI 0.9.9

> - UWSGI_APPID for better multiapp hosting
>
> http://projects.unbit.it/uwsgi/wiki/uWSGIVars

I don't quite get how this is used? what happens with the WSGI 
application?

--

-- 
дамјан
_______________________________________________
uWSGI mailing list
uWSGI <at> lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Gmane