So I started running puppet under unicorn, and it works, but there is a problem with shutting it down. Whenever you send a SIGINT to the master unicorn process, the worker processes are left running and listening on the socket until they time out and shut themselves down. However if you send it a SIGTERM it shuts down fine . The other interesting point is that when you send the SIGINT, the process writes out "Canceling startup", which indicates that rack never fully started. I'm guessing it's because of this that the workers don't get shut down properly.
I wrote a really simple rack app to run under unicorn, and it behaves properly with both SIGINT and SIGTERM, so this leads me to believe puppet is doing something unusual with rack. Anyone know why this is occurring? It feels like a bug in puppet, but wasn't sure if unicorn was officially supported or not. Puppet 3.1 with unicorn 4.5.0 -Patrick -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
