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

2014-03-28 Thread 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091783

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


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

2014-01-02 Thread Sworddragon
I think the most annoying thing is that this causes an entry in dmesg.
Wouldn't it be possible that failsafe can exit itself with 0 if it
detects that the system has booted successfully instead of waiting for a
TERM signal?

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

Title:
  init: failsafe main process killed by TERM signal

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


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

2014-01-02 Thread Sworddragon
I think the most annoying thing is that this causes an entry in dmesg.
Wouldn't it be possible that failsafe can exit itself with 0 if it
detects that the system has booted successfully instead of waiting for a
TERM signal? For example instead of sending the TERM signal Upstart
could emit an own event for this which failsafe also listens on the
stop on stanza. Or doesn't this work?

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

Title:
  init: failsafe main process killed by TERM signal

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


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

2014-01-02 Thread James Hunt
This is not a bug: the failsafe job detects if the system failed to boot
and takes appropriate action. However, in all likelihood your system
will boot as expected so the failsafe job (which is always started) is
stopped. Upstart does this by sending the TERM signal, hence the message
which can be safely ignored.

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

Title:
  init: failsafe main process killed by TERM signal

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


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

2013-12-25 Thread anatoly techtonik
I am confused and it is a bug.

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

Title:
  init: failsafe main process killed by TERM signal

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


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

2013-03-26 Thread James Hunt
'failsafe' is a job that will force the boot to proceed should that be
required.

The job will always start but in the normal case (where no problems are
detected) it will be stopped automatically using SIGTERM as shown by the
message.

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

Title:
  init: failsafe main process killed by TERM signal

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


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

2013-03-25 Thread Mohammad Shamma
I second Sworddragon's question.

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

Title:
  init: failsafe main process killed by TERM signal

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


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

2012-12-19 Thread Sworddragon
Can you give some more details why this is not a bug?

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

Title:
  init: failsafe main process killed by TERM signal

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


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

2012-12-18 Thread Karma Dorje
$  dmesg | grep kill
[   17.093010] init: failsafe main process (961) killed by TERM signal

not a bug → invalid

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

Title:
  init: failsafe main process killed by TERM signal

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2012-12-18 Thread Karma Dorje
** Changed in: upstart (Ubuntu)
   Status: New = Invalid

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

Title:
  init: failsafe main process killed by TERM signal

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs