Bug ID 571210: Upgrade, load config, or sync might fail on large configs with large objects.

Last Modified: Dec 15, 2020

Bug Tracker

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

Known Affected Versions:
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.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
12.1.0, 11.6.1 HF1, 11.5.4 HF2

Opened: Feb 02, 2016
Severity: 3-Major
Related AskF5 Article:


Attempting to load a large config with large objects may result in the following error message: err mcpd[7366]: 01070710:3: Database error (52), Can't write blob data, attribute:implementation status:52 - EdbBlobData.cpp, line 57 Attempting to synchronize a large change may result in the following error messages and a crash of the MCPD process: err mcpd[8210]: 01071693:3: Incremental sync: Caught an exception while adding a transaction to the incremental config sync cache: unexpected exception. err mcpd[8210]: 01070734:3: Configuration error: MCPProcessor::processRequestNow: Can't write blob data, attribute:msgs status:52 err mcpd[8210]: 01070596:3: An unexpected failure has occurred, request_group destroyed while processing, exiting...


Upgrade, load config, or sync might fail, and a system crash and restart might occur.


The config must be approximately 19.75 MB (slightly less) prior to processing a large object in the config that exceeds 256 KB. Or, once config exceeds 19.75 MB and 2 MB of additional memory has been allocated, processing config objects that exceed 256 KB (the larger, the more likely to occur) lead to the error.


Stagger the load, or reduce the size of particularly large objects within a config.

Fix Information

Memory handling is improved so that large configs with large objects now successfully complete upon upgrade, load config, or sync.

Behavior Change