Bug ID 701341: If /config/BigDB.dat is empty or the file is corrupt, mcpd continuously restarts

Last Modified: Apr 20, 2022

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 16.0.0,, 16.0.1,,

Opened: Jan 10, 2018
Severity: 2-Critical
Related AskF5 Article:


If an issue causes /config/BigDB.dat to be empty or its contents become corrupted, mcpd fails to start up. System commands report errors about being unable to read DB keys. 'bigstart' outputs errors: --dbval: Unable to find variable: [security.commoncriteria]


The system fails to start up, and mcpd continually restarts. The BIG-IP system fails to process traffic while the mcpd process is restarting.


The event causing BigDB.dat to be truncated is unknown at this time.


To work around this issue, you can remove the empty or corrupted BigDB.dat file. To do so, perform the following procedure: Impact of workaround: Performing the following procedure should not have a negative impact on your system. 1. Log in to bash. 2. To remove the zero-byte or corrupted BigDB.dat file, type the following command: rm /config/BigDB.dat

Fix Information


Behavior Change