Thanks for the advice and input. I am running Hypnotoad underneath a UNIX service management application, and after quite a bit of debugging, I am not able to replicate the problem when I run Hypnotoad on its own. So perhaps this is more of a fault with the service manager. Hypnotoad is running in foreground mode, launched by the service manager. I'm sure this is not a typical configuration, but I have to work with what I have. Hotswappability has already proven an issue with the Service Manager, as during hot swap it wants to keep track of the original hypnotoad server and is unaware of the new server's pid.
I am considering writing a simple wrapper script that will launch hypnotoad - something similar to Clustericious::Command::hypnotoad. Are there any different deployment strategies that anyone can recommend for running hypnotoad / Mojo::Server::Prefork as a foreground process? On Saturday, April 4, 2015 at 4:17:46 AM UTC-5, sri wrote: > > How can I troubleshoot this further to determine: >> >> 1. Why does Hypnotoad think it still needs to kill non-existent >> processes? >> 2. Why isn't it starting new ones? >> >> > Never seen this before, but i'll gladly track it down if you can provide > an example application that would allow me to replicate the problem. > Otherwise i'm afraid you'll have to track this down yourself, somewhere in > Mojo::Server::Prefork. > > https://github.com/kraih/mojo/blob/master/lib/Mojo/Server/Prefork.pm > > -- > sebastian > -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to mojolicious+unsubscr...@googlegroups.com. To post to this group, send email to mojolicious@googlegroups.com. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
