On 11/02/2015, at 9:36 PM, Paul Royik <[email protected]> wrote:
> What if I make cron to restart Apache every 5 minutes? If you look at the existing cron entry, it isn't doing a 'restart' but a 'start'. This means that if Apache is already running it will effectively leave it alone. Triggering a 'restart' would be bad as you would interrupt running requests every time. The 'start' ensures that something happens only when it isn't running already. > Will it crash server? What are consequences? No, but it is a band aid fix when you should try and work out what may have sent a signal to Apache in the first place to cause it to shutdown. It should not just shutdown itself. If you look back through the logs, if it was one of the normal expected signals which cause an orderly shutdown, as the last past of the logs before the restart suggest, Apache would have logged what the signal was so you at least know that much. if you are adamant that you didn't accidentally somehow shut it down, you might want to read up the WebFaction documentation to see if that have a system which identifies memory hungry web server instances and which tries to kill the main parent process. Usually ISPs though they just kill the memory hungry process, which means Apache would have just replaced it and your application would have kept running. The logs suggest that the Apache parent process was shutdown and not just the child process the WSGI application runs in. Graham -- You received this message because you are subscribed to the Google Groups "modwsgi" 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]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
