The initial crash is caused by an attempt to deference a NULL jobs list before entering the main loop.
The jobs list is NULL because Upstart failed to read its configuration. Upstart failed to read its configuration because inotify was not available. This is a known issue with the edgy version of Upstart and is fixed in the feisty version; the fix is part of a significant overhaul of the config code, so not easy to backport. Inotify was not available because there were no inotify descriptors available. There were no inotify descriptors available because the limit for the root user had been reached. The limit had been reached because Upstart doesn't close its inotify descriptor, so each re-exec consumes another. This is also a known issue with the edgy version and is fixed in feisty, the fix wasn't backported because we didn't believe it to have a serious effect. Now we know there's a serious consequence, there's a simple one-line fix. -- upstart turns machines into a scene from 'Dead Rising' https://bugs.launchpad.net/bugs/141034 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
