janne.karhunen at gmail.com
Thu Oct 22 12:32:16 BST 2009
On Thu, Oct 22, 2009 at 2:07 PM, Janne Karhunen
<janne.karhunen at gmail.com> wrote:
>> Maybe init=/bin/bash, set ulimit -c to unlimited, then see if you get
>> other messages?
> It may be upstart after all goofing up the console somehow. Crash
> is due to following;
> stat64("/dev/fd", 0x7efc3978) = -1 ENOENT (No such file or directory)
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> +++ killed by SIGSEGV +++
> Kernel panic - not syncing: Attempted to kill init!
> Now if I dump the contents of /proc/self/fd (/dev/fd) just prior
> to executing upstart everything is fine. Links also properly
> point to console. Humm..
This was not 'strace -f' run, so output should be from core
upstart and not from the job (?). Is it chrooting somewhere
perhaps prior to executing the job?
More information about the upstart-devel