Can start, but not restart, a stopped Upstart job
Bug #430883 reported by
Anders Kaseorg
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debhelper (Ubuntu) |
Fix Released
|
Low
|
Steve Langasek | ||
upstart (Ubuntu) |
Fix Released
|
Low
|
Steve Langasek |
Bug Description
Binary package hint: upstart
I would expect ‘restart’ to behave as ‘start’ if the job is not already running, just like with old init.d scripts. However, it fails with a strange error:
root@balanced-
network-manager stop/waiting
root@balanced-
restart: Unknown instance:
root@balanced-
network-manager start/running, process 11551
This makes it difficult to transition a package with an Upstart job from ‘dh_installinit’ to ‘dh_installinit --restart-
Related branches
Changed in debhelper (Ubuntu): | |
assignee: | nobody → Scott James Remnant (scott) |
importance: | Medium → Low |
Changed in upstart (Ubuntu): | |
milestone: | none → ubuntu-8.04.4 |
milestone: | ubuntu-8.04.4 → ubuntu-9.10-beta |
Changed in debhelper (Ubuntu): | |
milestone: | none → ubuntu-9.10-beta |
Changed in upstart (Ubuntu): | |
milestone: | ubuntu-9.10-beta → none |
Changed in debhelper (Ubuntu): | |
assignee: | Scott James Remnant (scott) → nobody |
milestone: | ubuntu-9.10-beta → none |
assignee: | nobody → Scott James Remnant (scott) |
tags: | removed: ubuntu-boot |
To post a comment you must log in.
This is by design.
Upstart's "restart" command is intended to *only* atomically restart a running instance, that's because I consider it a bug that a restarting a service that is not running can start it in the old system.
This can mean that a sysadmin's desire to have a service not running is not honoured, and after an upgrade, have it started again without their consent.
Also note that in Upstart, "restart" *will not* reload the /etc/init/*.conf file - so any changes are not honoured. You have to fully stop and start the service (e.g. across a normal upgrade) to have changes in the conf file respected.