[Bug 1301509] Re: init.d scripts don't start properly on trusty

[Andrew Berry]

A dist-upgrade right around the date of the 14.04 final release fixed
this for me. Everything has been fine since. I looked back up the
package histories for this and a few others, and didn't see anything
that said it would fix this, but I think this issue can probably be
closed.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1301509

Title:
  init.d scripts don't start properly on trusty

Status in “upstart” package in Ubuntu:
  New

Bug description:
  upstart: 1.12.1-0ubuntu1

  I've built a Vagrant image using the cloud image form http://cloud-
  images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-i386
  -vagrant-disk1.box

  For some reason, most scripts in /etc/init.d won't run on boot, even
  when the various symlinks are set up properly. An easy package to test
  with is memcached, but I've seen the same problem with redis-server as
  well as with Virtualbox's init scripts.

  I was debugging this by going through a verbose boot, and I discovered
  that if I boot to recovery, and then immediately resume a normal boot,
  the init.d scripts do run and all the services load. I'm not familiar
  enough with recovery to know how it changes what upstart runs, but at
  least it's something to debug.

  Basic steps to recreate:

  * Use vagrant to spin up the box linked above (but I'm assuming this has nothing to do with vagrant or the cloud image)
  * Run apt-get update / dist-upgrade to bring everything up to date.
  * apt-get install memcache
  * reboot
  * ps auxww | grep memcache shows nothing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1301509/+subscriptions