# Mephisto + Mongrel\_cluster 503 Service Temporarily Unavailab **URL:** \ **Category:** Deployment\ **Created:** [February 11, 2007, 6:38am UTC](https://www.ruby-forum.com/t/mephisto-mongrel-cluster-503-service-temporarily-unavailab/85196 "2007-02-11T06:38:32Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![boboroshi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/b5e925/32.png) [@boboroshi](https://www.ruby-forum.com/u/boboroshi)\ **Post date:** [February 11, 2007, 6:38am UTC](https://www.ruby-forum.com/t/mephisto-mongrel-cluster-503-service-temporarily-unavailab/85196/1 "2007-02-11T06:38:32Z")
I had Mephisto running deployed via capistrano per Coda Hale’s instructions on a FreeBSD server and everything was running swimmingly until the power went out at my house and when the server came back up, the cached pages are fine, but the /admin section generates Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. This happens at 80 (apache) and 8080 (the cluster itself). However, if I cd into the current directory in the capistrano deploy and have mongrel\_rails start, I can access the app on 3000. So no worky: [http://www.boboroshi.com/admin](http://www.boboroshi.com/admin) [http://www.boboroshi.com:8080/admin](http://www.boboroshi.com:8080/admin) Worky: [http://www.boboroshi.com:3000/admin](http://www.boboroshi.com:3000/admin) I’ve upgraded all gems, etc. ANy thoughts? Thanks in advance. -J John A. boboroshi [www.meticulous.com](http://www.meticulous.com) [www.boboroshi.com](http://www.boboroshi.com) ---
**Author:** ![boboroshi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/b5e925/32.png) [@boboroshi](https://www.ruby-forum.com/u/boboroshi)\ **Post date:** [February 11, 2007, 2:49pm UTC](https://www.ruby-forum.com/t/mephisto-mongrel-cluster-503-service-temporarily-unavailab/85196/2 "2007-02-11T14:49:17Z")
On 2/11/07, boboroshi [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > This happens at 80 (apache) and 8080 (the cluster itself). However, if > I cd into the current directory in the capistrano deploy and have > mongrel\_rails start, I can access the app on 3000. Looks like your cluster ins’t set to automatically start when the system goes up… (init.d script?) have you tried mongrel\_rails cluster::start in your app directory? > -J > > John A. > boboroshi > [www.meticulous.com](http://www.meticulous.com) > [www.boboroshi.com](http://www.boboroshi.com) > > > ## – Luis L. Multimedia systems Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ---
**Author:** ![boboroshi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/b5e925/32.png) [@boboroshi](https://www.ruby-forum.com/u/boboroshi)\ **Post date:** [February 11, 2007, 3:39pm UTC](https://www.ruby-forum.com/t/mephisto-mongrel-cluster-503-service-temporarily-unavailab/85196/3 "2007-02-11T15:39:21Z")
Luis - Tried that. FreeBSD doesn’t have an etc/init.d directed. it has an inetd.conf where you add one line files. Running the command says the PID is already going $ mongrel\_rails cluster::start Starting 3 Mongrel servers… \*\* !!! PID file log/mongrel.8000.pid already exists. Mongrel could be running already. Check your log/mongrel.log for errors. \*\* !!! Exiting with error. You must stop mongrel and clear the .pid before I’ll attempt a start. mongrel\_rails start -d -e production -p 8000 -a 127.0.0.1 -P log/ mongrel.8000.pid -c /home/jathayde/boboroshi/current (one for each cluster node occurs) mongrel\_rails cluster::restart retarts the server with no command line feedback but the 503 response persists. I also tried to cap restart and cap deploy, neither of which kicks the system back up. The static pages are still being served from the cache, but that’s it. ---
**Author:** ![boboroshi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/b5e925/32.png) [@boboroshi](https://www.ruby-forum.com/u/boboroshi)\ **Post date:** [February 11, 2007, 7:52pm UTC](https://www.ruby-forum.com/t/mephisto-mongrel-cluster-503-service-temporarily-unavailab/85196/4 "2007-02-11T19:52:39Z")
Either do a restart or manually delete the .pid. When the power goes out, mongrel doesn’t exit cleanly, and so that is why a .pid would be left and things not working. I had a similar problem before. Regards, Sean ---
**Author:** ![boboroshi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/b5e925/32.png) [@boboroshi](https://www.ruby-forum.com/u/boboroshi)\ **Post date:** [February 11, 2007, 10:44pm UTC](https://www.ruby-forum.com/t/mephisto-mongrel-cluster-503-service-temporarily-unavailab/85196/5 "2007-02-11T22:44:52Z")
On 2/11/07, Sean [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Either do a restart or manually delete the .pid. When the power goes > out, mongrel doesn’t exit cleanly, and so that is why a .pid would be > left and things not working. I had a similar problem before. If memory don’t trick me, latest mongrel\_cluster check if the actual process in the pid file exist, and if not, delete the file and spawn again. Anyway, something related to these issues was commited in the latest version of mongrel and mongrel\_cluster. ## – Luis L. Multimedia systems Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ---
**Author:** ![boboroshi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/b5e925/32.png) [@boboroshi](https://www.ruby-forum.com/u/boboroshi)\ **Post date:** [February 12, 2007, 4:44am UTC](https://www.ruby-forum.com/t/mephisto-mongrel-cluster-503-service-temporarily-unavailab/85196/6 "2007-02-12T04:44:14Z")
Thanks Sean and Luis. Deleting the PID files in log did the trick.