Bug ID 1188857: EPSEC RPM database is corrupted

Last Modified: Mar 26, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Opened: Nov 11, 2022
Severity: 3-Major


Unable to access the GUI after rebooting the device. In the SSH/console, following message is displayed in the LTM logs: Failed to reset strict operations; disconnecting from mcpd.


The MCPD fails to fully load and the device fails to come up and cannot pass traffic. An internal timer might cause the installation to be aborted and all daemons to be restarted through bigstart restart. Traffic is disrupted while TMM restarts.


- APM provisioned. - Previous EPSEC packages which were deleted from the system from earlier BIG-IP versions are erroneously attempting to install upon boot due to a corrupt APM RPM database.


You can recover by rebuilding the APM specific RPM database: 1. Delete the existing database # rm -rf /var/apm/lib/rpm 2. Refresh the database using the EPSEC bash script # epsec -f refresh???

Fix Information


Behavior Change