[Bug 1091783] Re: init: failsafe main process killed by TERM signal

[Volker Siegel]

I understand that the process reporting the line is working just fine;
But I think that, in itself, showing the message in the log is a bug;
It is bound to be very distracting when reading the log after something went wrong, trying to spot suspicious messages.

Without background, I read it as saying that the init process tells me that some  important ("main") process was killed,
even though it should be failsafe.
Now, reading the comments above, it actually tells me that boot went fine.

I think it can be solved by changing the message to be less ambiguous
and ideally to indicate it's not indicating failure of anything.

Just looking at the message, it seems to be used in other places too -
so it would be impossible to just replace the whole text cleanly. But it
could be good enough to make minor changes only, ie making more clear
that it's not the main process that is failsafe::

Original: 
"init: failsafe main process killed by TERM signal"

proposed change:
"init: job "failsafe" - main process killed by TERM signal"
or
"init: "failsafe": main process killed by TERM signal"

Could a change like this work for the general message in other cases
too?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1091783

Title:
  Confusing log message "init: failsafe main process (...) killed by
  TERM signal"

Status in “upstart” package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 13.04 dev with upstart 1.6.1-1ubuntu1. On booting my
  system I'm seeing in /var/log/kern.log the line "Dec 18 18:17:46
  ubuntu kernel: <12>[   19.939989] init: failsafe main process (1033)
  killed by TERM signal".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1091783/+subscriptions