init.d scripts don't start properly on trusty
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| upstart (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
upstart: 1.12.1-0ubuntu1
I've built a Vagrant image using the cloud image form http://
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
| Andrew Berry (andrewberry) wrote | #1 |
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.