Bug ID 1987017: qat_stat process generates core.host.unknown during system upgrade or reboot

Last Modified: Jul 15, 2026

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

Fixed In:
F5OS v2.0.0, F5OS v2.0.0

Opened: Jul 16, 2025

Severity: 2-Critical

Symptoms

The qat_stat process generates a core dump file (core.host.unknown) on F5OS appliance and chassis platforms. The core dump triggers alert event 327680 in the platform log: "Core dumped on appliance. process=qat_stat, location=/var/shared/core/host/core.host.unknown.xxxxx.xxxxxxxxxx.core.gz"

Impact

Unexpected core.host.unknown files are generated and core-dump alerts are raised during upgrade or reboot operations. There is no impact to system functionality or traffic processing. The core files consume disk space and may cause confusion during troubleshooting.

Conditions

This issue occurs during system reboot or F5OS software upgrade operations. When the system sends a SIGTERM signal during these operations, the qat_stat process is terminated immediately without properly releasing tmstat rows and other resources, resulting in a core dump.

Workaround

Upgrade to F5OS version containing qat-support-pod 3.1.34 or later.

Fix Information

Added signal handlers (SIGTERM, SIGINT, SIGHUP) to the qat_stat process to enable graceful shutdown. When a termination signal is received during upgrade or reboot, qat_stat now properly releases tmstat rows and cleans up resources before exiting, preventing core dumps. Additionally, the qat_service_manager (QAT-Support-Pod) was updated to send SIGTERM instead of SIGKILL, allowing the qat_stat process time to perform cleanup before shutdown.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips