Take the 2-minute tour ×

update: /lib/init/upstart-job has been replaced with the MongoDB init script.

For some reason, /etc/init.d/mysql start|stop|restart|status (/etc/init.d/mysql is simply a symlink to /lib/init/upstart-job) is affecting my MongoDB install, not my MySQL install. service start|stop|restart|status mysql works as you'd expect.

An example:

root@score:~# /etc/init.d/mysql status
 * Checking status of database MongoDB

What could cause this, and how can I fix it?


share|improve this question
Please can you post the contents of /etc/init.d/mysql? –  fahadsadah Oct 12 '10 at 16:01
/etc/init.d/mysql is a symlink to /lib/init/upstart-job. –  ceejayoz Oct 12 '10 at 17:00
@Jorge Castro Done. –  ceejayoz Oct 13 '10 at 15:46
You should also try status mysql. –  JanC Oct 13 '10 at 19:22
Oh, and check the contents of /etc/init/mysql and (if that exists) /etc/init/mongodb –  JanC Oct 13 '10 at 19:24

1 Answer 1

up vote 3 down vote accepted

The correct contents of /lib/init/upstart-job for lucid or maverick are http://paste.ubuntu.com/517673/ Please triple-check that it is a regular file before editing this, and not a symlink (in case the symlink in in the wrong direction). Since this file is used for starting many core services, you do not want to have it broken further, and should check carefully before rebooting. At this stage, I'm not sure how it could have the different contents unless there was some manual intervention to change it. The package in maverick appears to contain the correct symlink.

share|improve this answer
Thanks! Will award the bounty in 20 hours when it lets me. I'm using MongoDB's package repo for this. Very odd - I'm about 99% sure I didn't do anything manually to do this. –  ceejayoz Oct 21 '10 at 21:05
I'll have to check that one out - I was looking at the mongodb packages in lucid & maverick & hadn't spotted a problem in the postinst or other packaging there –  ajmitch Oct 21 '10 at 21:07

Your Answer


