Another question, Every worker in my application opens child processes using subprocess.Popen() to perform some tasks. This works great, until the master mode is enabled. As soon as one of my worker's child processes terminates, the master uwsgi process detects this and tries to respawn a new worker, and warns that the died process doesn't belong to the workers list:
spawned uWSGI master process (pid: 3419) spawned uWSGI worker 1 (pid: 3431) spawned uWSGI worker 2 (pid: 3432) DAMN ! process 3429 died :( trying respawn ... worker respawning too fast !!! i have to sleep a bit... Respawned uWSGI worker (new pid: 3433) warning the died pid was not in the workers list. Probably you hit a BUG of uWSGI DAMN ! process 3433 died :( trying respawn ... Respawned uWSGI worker (new pid: 3434) warning the died pid was not in the workers list. Probably you hit a BUG of uWSGI DAMN ! process 3434 died :( trying respawn ... Respawned uWSGI worker (new pid: 3435) warning the died pid was not in the workers list. Probably you hit a BUG of uWSGI DAMN ! process 3435 died :( trying respawn ... Respawned uWSGI worker (new pid: 3436) warning the died pid was not in the workers list. Probably you hit a BUG of uWSGI DAMN ! process 3436 died :( trying respawn ... Respawned uWSGI worker (new pid: 3437) warning the died pid was not in the workers list. Probably you hit a BUG of uWSGI DAMN ! process 3437 died :( trying respawn ... Respawned uWSGI worker (new pid: 3439) warning the died pid was not in the workers list. Probably you hit a BUG of uWSGI DAMN ! process 3439 died :( trying respawn ... How to work around this? -- Jean-Baptiste Quenot _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
