> Hi,
> I see many entries like this -
> [pid: 3167|app: 0|req: 4/5] 192.168.2.3 () {46 vars in 820 bytes} [Wed Nov
> 27 14:38:04 2013] GET /everest3/connections/mycxns.load/recommended =>
> generated 985 bytes in 62 msecs (HTTP/1.1 200) 6 headers in 309 bytes (1
> switches on core 0)
> worker 4 killed successfully (pid: 3162)
> Respawned uWSGI worker 4 (new pid: 3171)
> mapping worker 4 to CPUs: 0
>
> Why are workers getting killed like this?
> My parameters are -
> socket = /var/www/web2py/logs/%n.socket
> pythonpath = /var/www/web2py/
> mount = /=wsgihandler:application
> processes = 4
> master = true
> harakiri = 90
> reload-mercy = 80
> cpu-affinity = 1
> stats = /tmp/%n.stats.socket
> max-requests = 2000
> limit-as = 512
> reload-on-as = 256
> reload-on-rss = 192here you ar telling uWSGI to kill workers using more than 192M of RSS memory, whenever a worker hit the limit it is recycled. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
