I actually don't think that god has a problem with cleaning the pids, because the restart works successfully.
I think the problem lies in the actual checking of the pid. My log doesn't show it, but from start, checking if the process is running (via the pid) works just fine. It isn't until after the memory trigger happens, which causes a restart. Restart takes the existing pid so that mongrel knows what to restart. This restart itself works fine. The problem happens when the next processrunning check occurs -- it thinks that the process is NOT running. It then tries to start again. Start obviously fails because the pid does really still exist (it never got deleted). It sounds like somehow when the restart happens that god's memory of where the pid is is getting erased or changed, and therefore it can't find the pid anymore. Unfortunately, I am not smart enough to understand how to troubleshoot this behavior. On Jan 9, 2:26 pm, thoraxe <[email protected]> wrote: > Well, I would love to troubleshoot what god's problem is but I'm not > savvy enough to know what to look for. I'm open to suggestions. > > mongrel_cluster may surely be useful, but I think in this instance > fixing the actual problem will probably be more beneficial to the > community :) So I'm down to try! > > On Jan 9, 11:56 am, woahdae <[email protected]> wrote: > > > This topic's been mentioned elsewhere: > > >http://groups.google.com/group/god-rb/browse_thread/thread/3239f2d018... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "god.rb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/god-rb?hl=en -~----------~----~----~----~------~----~------~--~---
