Bug ID 458557: When mysqld is stopped using SIGSTOP, high availability action is not taken

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP AFM, ASM, AVR, PEM, PSM(all modules)

Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Fixed In:
11.6.0

Opened: Apr 23, 2014
Severity: 3-Major
Related Article:
K15540

Symptoms

If you use SIGSTOP to stop the mysqld process, this can prevent high availability actions. This is because the monitoring process (mysqlhad) hangs when trying to connect to the mysqld server.

Impact

The configured action that should be taken when mysqld is not available is not taken by the BIG-IP high availability system.

Conditions

using SIGSTOP to stop the mysqld process

Workaround

This will only ha

Fix Information

Added a heartbeat mechanism that ensures that action is taken when the monitoring process (mysqlhad) hangs.

Behavior Change