Hmm, unfortunately I only have the last 7 days of syslog -- so I can not see
what the problem was on the 15th Oct.

Is there anything in the report than can help you? If not, might make sense
to close it out.

I'll increase the syslog log retention to 1 month.

Anand

On Mon, Oct 26, 2009 at 11:05 AM, Scott James Remnant
<[email protected]>wrote:

> On Mon, 2009-10-26 at 10:40 +0000, Anand Kumria wrote:
>
> > Is there any way to identify the particular process that init/upstart
> > invoked that cause this to occur?
> >
> Yes, Upstart should report an ordinary "failed to start" for this
> process - you'll find a message in syslog with the actual error.
>
> Scott
> --
> Have you ever, ever felt like this?
> Had strange things happen?  Are you going round the twist?
>
> --
> assert failure: Unhandled error from job_process_spawn (or similar)
> https://bugs.launchpad.net/bugs/451917
> You received this bug notification because you are a direct subscriber
> of the bug.
>
>

-- 
assert failure: Unhandled error from job_process_spawn (or similar)
https://bugs.launchpad.net/bugs/451917
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to