> One of my site's servers had a problem yesterday and the host > restarted it. During boot up Mongrel failed to start as the PID files > still existed in /log > > I didn't find out about this reboot until several hours later so the > site was down that entire time which is less than ideal. > > Does anybody know of a way around this? Is there a built in way to > force Mongrel to start and overwrite any existing PID files? > > I have the mongrel_cluster startup script setup correctly btw.
I usually write some shell script to clear out the pid files, but another way that works is to have mongrel put it's pid files in the /tmp directory which gets emptied on restart. -- Daniel Johnson Systems Administrator PLANET ARGON, LLC Ruby on Rails Development, Consulting & Hosting www.planetargon.com http://teknot.us [blog] teknotus [freenode IRC] +1 503 445 2457 +1 877 55 ARGON [toll free] +1 815 642 4068 [fax] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
