Bug ID 1365977: Container daemons running as PID 1 cannot be cored on-demand

Last Modified: Oct 29, 2024

Affected Product(s):
F5OS F5OS-A, F5OS-C(all modules)

Known Affected Versions:
F5OS-A 1.3.2, F5OS-A 1.5.0, F5OS-A 1.5.1, F5OS-A 1.5.2

Fixed In:
F5OS-A 1.8.0

Opened: Oct 03, 2023

Severity: 3-Major

Symptoms

- kill -QUIT (or any other core-producing signal) to a container process running as PID 1 does not cause a core file. - Actual runtime errors do generate cores as expected.

Impact

Not possible to force a core file for diagnostic purposes.

Conditions

Containers that run their services directly as PID 1.

Workaround

None

Fix Information

Containers that were running directly as PID 1 have been modified to use a minimal "init" process to catch and forward signals to the real service process. The command: "docker exec {containername} kill -QUIT 1" can be used to core a daemon running as a child of /dev/init. More complicated containers that have multiple processes running under 'bash' script may need to use "docker exec {containername} kill -ABRT -1" Note that if the "docker kill" or "docker stop" commands are used instead of "docker exec", the container will not restart, resulting in an inoperative system.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips