Bug ID 838269: ASM cannot save sync file after MySQL corruption following forcible restart

Last Modified: Jan 20, 2023

Bug Tracker

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1

Opened: Oct 13, 2019
Severity: 3-Major

Symptoms

ASM cannot save sync file after MySQL corruption following forcible restart.

Impact

ASM cannot save sync files. This prevents saving UCS and high availability (HA) sync.

Conditions

MySQL was restarted forcibly, possibly following /var disk partition exhaustion.

Workaround

As a workaround, it may be possible to delete all files under /var/lib/mysql/PLC_ucs and restart MySQL. However, in our experience, once MySQL has been corrupted by forcible restarts and/or disk exhaustion, it is more advisable to reinstall the device from scratch and load the saved configuration.

Fix Information

None

Behavior Change