Opened 9 years ago

Closed 5 years ago

#705 closed enhancement (wontfix)

Log more helpful status when process exits under the boss

Reported by: shane Owned by:
Priority: low Milestone: Common Outstanding Tasks
Component: ~Boss of BIND (obsolete) Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 0.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

Jeremy reported something exited with status 139.

It turns out that the status value is as follows:

a 16-bit number, whose low byte is the signal number that killed the process, and whose high byte is the exit status (if the signal number is zero); the high bit of the low byte is set if a core file was produced

That is from the Python documentation here:

http://docs.python.org/py3k/library/os.html#os.wait

So, deciphering it we see that it is < 256, which means it is a signal. The high bit is set - meaning we have core. We can remove that by subtracting 128 and discover that this is signal 11 (SEGV).

It would be nice if the boss process did this work and reported exactly what happened to the child process.

Subtickets

Change History (3)

comment:1 Changed 9 years ago by stephen

  • Milestone feature backlog item deleted

Milestone feature backlog item deleted

comment:2 Changed 6 years ago by stephen

  • Defect Severity set to N/A
  • Milestone set to Common Outstanding Tasks
  • Sub-Project set to DNS

comment:3 Changed 5 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check http://bundy-dns.de.

Closing ticket.

Note: See TracTickets for help on using tickets.