[ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com
Bug #1381075 reported by
Antti Kaijanmäki
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
upstart (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
We have important system and session services that we rely on being running and functional.
If such a component hits the upstart respawn limit for any reason, we should be able to get a report that something is seriously wrong.
Inspiration for this bug as per the discussion in: https:/
description: | updated |
tags: | added: rtm14 |
To post a comment you must log in.
The most appropriate way to do this would probably be to use apport to check for respawn limit messages in:
- the system log, and xsession- errors file.
- the users $HOME/.
Even at the default upstart log priority of 'message', when a job reaches the respawn limit, upstart will log a message to one of the logs above like this:
init: foo respawning too fast, stopped
So apport, or some such utility could watch for these messages using inotify and raise an informational error that would be visible on errors.u.c.