Init reports 'failed' on boot, but starts properly

Bug #193376 reported by Bryan Haskins
2
Affects Status Importance Assigned to Milestone
clutch (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: clutch

Pretty simple issue, essentially on boot the Clutch init node will run and report that it has failed, on inspection after boot finishes, you can clearly see that the daemon has in fact started properly. Status works fine, and reports it all fine; presumably it is just an issue with the init script. My best guess being that it checks before the daemon has time to properly start.

Revision history for this message
John Dong (jdong) wrote :

Indeed, the clutch init script makes a number of assumptions about when transmission-daemon is active or not, and its status reports aren't all that great. We should use transmission-remote to query the daemon's state more explicitly.

Changed in clutch:
milestone: none → ubuntu-8.04
status: New → Confirmed
Revision history for this message
John Dong (jdong) wrote :

Built from latest initscript branch export, please test upgrades as I had to change socket location too.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package clutch - 0.4-0ubuntu5

---------------
clutch (0.4-0ubuntu5) hardy; urgency=low

  * clutch.init: Use transmission-remote to determine readiness of daemon, and
    to shut it down. (LP: #193376)
  * Also allows us to remove a lot of sleep hacks from postinst/prerm.
  * Move socket back to standard location and abolish silly symlinking

 -- John Dong <email address hidden> Sat, 01 Mar 2008 14:16:59 -0500

Changed in clutch:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.