upstart produces no boot log for bricked machines

Bug #430715 reported by David Favor
This bug report is a duplicate of:  Bug #328881: init: support logging of job output. Edit Remove
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: upstart

Karmic packages installed over the past few days produce many boot errors which fail to be logged anywhere.

There are many threads relating to upstart requiring the upstart-logd compat package to provide boot and shutdown logging.

These logs are essential for debugging boot and shutdown problems.

Maybe these logs can be shut off in final releases.

Both these logs should be turned on during development otherwise developers are reduced to multiple reboots trying to quickly write down errors as they flash across the screen.

Whoever is maintaining upstart will serve us all by auto installing the required packages and turning on logging for both boot and shutdown during Karmic development.

Please post an update about how to manually enable boot and shutdown logging so current boot problems causing bricked machines after last few days of Karmic package updates can be identified and fixed before tomorrow's next Alpha release.

David Favor (davidfavor)
summary: - upstart produces no boot log
+ upstart produces no boot log for bricked machines
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.