Hi,

Minor problems which I came across recently (Version: 1.1.1).

1. processes < 0
Due to a bug in config auto-generation code I ended up with
'processes = -1' which causes uwsgi to segfault during startup.

2. cheaper > processes
Due to another misconfiguration I ended up with cheaper (4) > processes
(1) and idle set to 300 seconds. Such setup was causing trouble when
respawning workers:

Thu Apr 19 12:31:48 2012 - workers have been inactive for more than 300 seconds 
(1334831508-1334831207)  
Thu Apr 19 12:31:48 2012 - cheap mode enabled: waiting for socket connection... 
 
Thu Apr 19 12:34:47 2012 - Respawned uWSGI worker 1 (new pid: 8419)  
Thu Apr 19 12:34:47 2012 - spawned uWSGI worker 2 (pid: 8420, cores: 1)  
Thu Apr 19 12:34:47 2012 - !!! uWSGI process 8420 got Segmentation Fault !!!

3. auto-procname=true
Occasionally I see weird process name in the process table eg. instead
of usual 'uWSGI master' I see eg. 'uWSGI
master                                                                          
                                                                                
                         gi.stats --zerg-server /var/run/plack/uwsgi.zerg 
--need-app --auto-procname true --ini /etc/uwsgi/uwsgi.ini'.
Not sure if it's a problem with uwsgi or some other library.
Regards,

Marcin
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to