# Mysql / mongrel do not start after reboot

**URL:** <https://www.ruby-forum.com/t/mysql-mongrel-do-not-start-after-reboot/92716>\
**Category:** Deployment\
**Created:** [April 23, 2007, 12:02pm UTC](https://www.ruby-forum.com/t/mysql-mongrel-do-not-start-after-reboot/92716 "2007-04-23T12:02:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ehudros](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/3ec8ea/32.png) [@ehudros](https://www.ruby-forum.com/u/ehudros)\
**Post date:** [April 23, 2007, 12:02pm UTC](https://www.ruby-forum.com/t/mysql-mongrel-do-not-start-after-reboot/92716/1 "2007-04-23T12:02:29Z")

</div>

Hi everyone,  
I have a working ubuntu server deployed using capistrano and deprec.  
after the initial installation everything worked fine - but after  
rebooting only the apache server (httpd) started and mysql/mongrel were  
down. It seems that in rc2.d everything is set up find (there are  
symlinks to mysql and mongrel\_cluster, and when I call them manually  
they start up alright) but they are not executed.

also, I see the is ps -ef “init [2]” is still running. The last time I  
actually worked on a unix server is 4 years ago, and I can’t remember if  
that means initialization is still running (and stuck) or that it jsut  
stays up this way.

can anyone please help? this is really annoying! 🙂

Thanks,  
Ehud

---

<div class="post-metadata">

**Author:** ![ehudros](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/3ec8ea/32.png) [@ehudros](https://www.ruby-forum.com/u/ehudros)\
**Post date:** [April 25, 2007, 9:42pm UTC](https://www.ruby-forum.com/t/mysql-mongrel-do-not-start-after-reboot/92716/2 "2007-04-25T21:42:20Z")

</div>

Hi Ehud,

to the best of my knowledge, the recommendation on the list has been  
to use monitoring utilities like monit to make sure instances get  
restarted.

hope this helps,  
Oliver

2007/4/23, Ehud R. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid):

---

<div class="post-metadata">

**Author:** ![ehudros](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/3ec8ea/32.png) [@ehudros](https://www.ruby-forum.com/u/ehudros)\
**Post date:** [April 25, 2007, 10:59pm UTC](https://www.ruby-forum.com/t/mysql-mongrel-do-not-start-after-reboot/92716/3 "2007-04-25T22:59:31Z")

</div>

On 4/25/07, Oliver B. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> to the best of my knowledge, the recommendation on the list has been  
> to use monitoring utilities like monit to make sure instances get  
> restarted.

Yup. If the only thing in the /etc/inittab is monit, and then every  
other service is listed in monit configuration (with appropriate  
start/stop commands), then monit will start everything on boot.

The main benefit of this approach is that you don’t write the same  
command in two different places, and startup of services happens in  
the same way on boot and on failure. Monit is also much smarter about  
service state, it can deal with zombie processes, RAM or file  
descriptor leaks, endless loops etc.

The drawback is that init restarts crashed services immediately,  
whereas monit does it on the next monitoring cycle (which may easily  
be a minute away).

–  
Alex