> Hi there, > > I actually have 2 issues with "attach-daemon" that I couldn't find any > satisfying solution anywhere. > > I have 2 blocking python script, one is django-socketio > SocketIOServer.serve_forever(), another is a quite custom ZMQ worker, both > listening to the same signals to terminate: > > http://pastebin.com/i3xuyNyQ > > They work and shutdown perfectly fine under normal circumstances. However: > > 1) django-socketio serve_forever() spawns well but uWSGI is not able to > spawn this ZMQ async server at all. I get the "Bye bye!" message in logs > right after "Async worker is up", where uWSGI stopping daemon on a reload > something or when I kill it manually. I have no clue why it doesn't spawn > it until the moment it dies.. > > 2) uWSGI is able to kill gracefully these daemons only on reload. Whatever > the signal it sends, my daemons do terminate correctly if it is a > "reload". > But there is no success if I "restart" or "stop" uwsgi server. There is no > bloody signal comes in so they simply go zombie and of course causing > trouble when uwsgi tries to re-spawn another daemons. > > I will be very happy if you guys give me some help out here. It's been > weeks that I'm quite tired of managing 2 simple daemons manually. I tried > with the uWSGI versions 1.9.14 and 2.0. > > Cheers, > Roy. > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
the behaviour you describe is a bit strange, can you try using github code and configuring a single daemon with attach-daemon2 (so you have control over signals to send) http://uwsgi-docs.readthedocs.org/en/latest/AttachingDaemons.html#attach-daemon2 when the first daemon works well try adding the second one, so we have more context to investigate on -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
