On Thu, Aug 29, 2013 at 2:51 PM, Rob Daniels <[email protected]> wrote: > I'm having an issue with Puma, it fails when it tries to restart itself. > When this happens it kills all the Puma processes, resulting in nginx > delivering a 502 Bad Gateway to our users. I'm able to start, stop & restart > it with my /etc/init.d/puma script (it runs /usr/local/bin/run-puma), it > just has issues when it restarts itself.
So, "restarts itself"? Do you have any idea why? I've never seen any of my own Puma instances spontaneously restart. Have you looked in the system logs for anything relevant? Is there a mismatch between you-the-user-manually-starting-it and the user that the process is normally running as/restarting as? What Ruby are you running? -- Hassan Schroeder ------------------------ [email protected] http://about.me/hassanschroeder twitter: @hassan -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CACmC4yBKWmy9-O0j0NEYg9__njdyCN4By2uUuZUD97ho2X%2BaNQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
