Operational Defect Database
BugZero found this defect 432 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 1188857
EPSEC RPM database is corrupted
Last update date:
5/16/2024
Affected products:
BIG-IP
BIG-IP APM
Affected releases:
14.1.5.3
14.1.5.4
14.1.5.6
15.1.8.1
15.1.8.2
15.1.9
15.1.9.1
15.1.10
15.1.10.2
15.1.10.3
15.1.10.4
16.1.3.4
Fixed releases:
No fixed releases provided.
Description:
Symptoms ... You are unable to access the GUI after rebooting the device. ... In the SSH/console, the following message is displayed in the LTM logs: Failed to reset strict operations; disconnecting from mcpd. ... Impact ... 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
