[chef] Upstart not working after chef-install

[Russell Bateman < >]

I have this cookbook of MongoDB recipes that's working pretty well, but suffers from an upstart problem. The node gets properly configured and upstart called,

The basic question is why does my MongoDB upstart stuff not work? My use of upstart mechanisms is identical to what comes out of the MongoDB package and compares identically to that in other MongoDB community recipes. (Well, to my eyes anyway.)

Particulars (just in case):
- all Ubuntu 12.04 (LTS)
- Chef server (11.x, more or less latest)
- replica nodes db01-03 running Chef client (11.x, more or less latest)

At the end of my chef-client run, all looks good to me, but as you see below...

1. upstart says the service isn't running (mongodb stop/waiting)
2. upstart will not start the service from the command line (mongodb stop/waiting)
3. if I run start-stop-daemon as in /etc/init/mongodb.conf (upstart script), it does launch the daemon
4. but, upstart still says the service isn't running (mongodb stop/waiting)
5. processor status says it is running
   
6. if I bounce the host, the service isn't running until I do this all by hand again
   

Below is a short scrape of the above. Can anyone tell me what I've screwed up?

[2013-10-03T18:33:59+00:00] INFO: template[/data/mongodb/mongodb.conf] sending restart action to service[mongodb] (immediate)
  * service[mongodb] action restart[2013-10-03T18:33:59+00:00] INFO: Processing service[mongodb] action restart (mongodb::replica line 23)
[2013-10-03T18:33:59+00:00] INFO: service[mongodb] restarted

    - restart service service[mongodb]

  * service[mongodb] action enable[2013-10-03T18:33:59+00:00] INFO: Processing service[mongodb] action enable (mongodb::replica line 42)
 (up to date)
  * service[mongodb] action start[2013-10-03T18:33:59+00:00] INFO: Processing service[mongodb] action start (mongodb::replica line 42)
[2013-10-03T18:33:59+00:00] INFO: service[mongodb] started

    - start service service[mongodb]

[2013-10-03T18:33:59+00:00] INFO: Chef Run complete in 5.902176274 seconds
[2013-10-03T18:33:59+00:00] INFO: Running report handlers
[2013-10-03T18:33:59+00:00] INFO: Report handlers complete
Chef Client finished, 7 resources updated
:~# service mongodb status
mongodb stop/waiting
:~# service mongodb start
mongodb stop/waiting
:~# cat /etc/init/mongodb.conf
description "Keeps MongoDB running between boots"
limit nofile 20000 20000
kill timeout 300         # wait 300s between SIGTERM and SIGKILL.
start on runlevel [2345]
stop on runlevel [06]
expect fork
script
  ENABLE_MONGODB="yes"
  PIDFILE=/var/run/mongodb.pid
  if [ -f /etc/default/mongodb ]; then . /etc/default/mongodb; fi
  if [ "x$ENABLE_MONGODB" = "xyes" ]; then
    exec start-stop-daemon --start --quiet --chuid mongodb -m --pidfile $PIDFILE \
        --exec /usr/bin/mongod -- --config /data/mongodb/mongodb.conf
  fi
end script
:~# PIDFILE=/var/run/mongodb.pid
:~# exec start-stop-daemon --start --chuid mongodb -m --pidfile $PIDFILE --exec /usr/bin/mongod -- --config /data/mongodb/mongodb.conf
about to fork child process, waiting until server is ready for connections.
forked process: 3969
all output going to: /data/mongodb/mongodb.log
child process started successfully, parent exiting
:~$ service mongodb status
mongodb stop/waiting
:~$ ps -ef | grep [m]ongo
mongodb  3969   1  0 18:35 ?   00:00:00 /usr/bin/mongod --config /data/mongodb/mongodb.conf