Bug ID 636182: Cannot update_indexes error during load sys config

Last Modified: Aug 04, 2022

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 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,,,,,,, 14.1.5,, 15.0.0, 15.0.1,,,,

Opened: Dec 29, 2016
Severity: 3-Major


In some cases, loading a saved configuration onto a device will fail with the error: "01070710:3: Cannot update_indexes/checkpoint DB object, class:devicegroup_device status:13"


The 'tmsh load sys config file myFile merge' command fails with an error as such, [root@aumy00vipr01:REBOOT REQUIRED:Standalone] tmp # tmsh load sys config file test-myvip1 merge Loading configuration... /shared/tmp/test-myvip1 There were warnings: Since drop limit is less than detection limit, packets dropped below the detection limit rate will not be logged. 01070710:3: Cannot update_indexes/checkpoint DB object, class:devicegroup_device status:13 - EdbCfgObj.cpp, line 127 Unexpected Error: Loading configuration process failed.


The error occurs when loading a saved configuration file (SCF or UCS) for a device in a Device Service Cluster, where the CM Device Name locally differs from that which is in the archive (SCF file or UCS archive).


Prior to loading the saved UCS file, run the tmsh command to rename the local CM device name to match that which is in the SCF file: tmsh mv cm device <current_name> <new_name> For example, "tmsh mv cm device bigip1.local bigip1.siterequest.com" Or load the default config: "tmsh load sys config defaults"

Fix Information


Behavior Change