Using kill signal SIGPWR results in system crash

Reported by Christian Kampka on 2012-09-12
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
upstart
Medium
James Hunt

Bug Description

When using the kill signal stanza to issue a SIGPWR signal ('kill signal 30') to stop a service, it causes the system to crash.

Attached you'll find an upstart script to reproduce the problem.
After calling `stop upstart-pwr`, the system immediately becomes unresponsive, leaving only blinking keyboard lights.
No useful log entries can be found in any of the usual places. Please feel free to ask for any useful information you feel I can provide.

Christian Kampka (kampka) wrote :
James Hunt (jamesodhunt) on 2012-09-12
Changed in upstart:
status: New → Confirmed
assignee: nobody → James Hunt (jamesodhunt)
importance: Undecided → High
James Hunt (jamesodhunt) wrote :

Hi Christian - thank you for reporting this issue. I can see what is causing the issue.

For now, you can work around the problem easily by specifying the signal name:

  kill signal SIGPWR

Changed in upstart:
importance: High → Medium
Christian Kampka (kampka) wrote :

James,

thanks, works like a charm and has the advantage of running on precise without backporting.

James Hunt (jamesodhunt) on 2012-10-22
Changed in upstart:
status: Confirmed → Fix Committed
Dimitri John Ledkov (xnox) wrote :

revno: 1381
committer: James Hunt <email address hidden>
branch nick: upstart
timestamp: Mon 2012-10-22 14:54:50 +0100
message:
  * init/parse_job.c: stanza_kill(): Actually save parsed
    value to avoid crash if kill signal given as a numeric
    (LP: #1049820).
  * init/tests/test_parse_job.c: test_stanza_kill(): New test:
    "with signal and single numeric argument".
  * init/Makefile.am: test_job_process must now be linked to the
  * 'util'
    library for pty helper functionality.
  * init/tests/test_job_process.c:
    - Compiler appeasement.
    - Conditionally run tests in a pty for build environments such as
      modern versions of sbuild(1) that do not provide a controlling
      terminal (sbuild) (LP: #888910).

Changed in upstart:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers