Bug ID 689294: Continuous logging of 'save sys config' messages after loading UCS file

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.0.0, 11.6.3, 11.6.2, 11.6.1

Opened: Oct 18, 2017
Severity: 3-Major

Symptoms

Continuous logging of 'save sys config' messages after loading UCS file. Messages might appear similar to the following: notice clusterd[7205]: 013a0006:5: mcpd tells us that config is being saved; incrementing this blade's revision and saving cluster config.

Impact

There are errors loading the UCS file, and mcp fails to start properly. The system continuously logs messages in /var/log/ltm, and /var/log/restjavad.0.log.

Conditions

Loading a UCS file. Note: This issue occurred as a result of a discrepancy in user info between MCP and restjavad. It is fixed with the refactoring of authentication, which was released beginning in with v13.0.0.

Workaround

You can use the following procedure to work around this issue. 1) Take .UCS of the device. 2) Take Qkview of the device from command line using 'qkview -s0'. 3) Force device offline. (Note: To ensure the device does not become active, use the processes described in K15122: Overview of the Force Offline option :: https://support.f5.com/csp/article/K15122, in the section: Setting Minimum Blades Up on VIPRION systems or vCMP guests.) 4) Disable autosync for the device group (Note: To prevent unwanted changes from overwriting the config on the active device, use the processes described in BIG-IP Device Service Clustering: Administration Managing Configuration Synchronization :: https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/big-ip-device-service-clustering-administration-14-1-0/05.html, in the section: Enabling and disabling automatic sync.) 5) Run the following command: bigstart stop restjavad 6) To verify the message is no longer logging, run the following command: tail -f /var/log/ltm (Press Ctrl+C to stop the command from running.) 7) Run the following command: rm -rf /var/config/rest 8) Run the following command: bigstart start restjavad 9) To verify the message has not returned, run the following command: tail -f /var/log/ltm (Press Ctrl+C to stop the command from running.) 10) Re-enable autosync (Note: For processes to do so, see BIG-IP Device Service Clustering: Administration Managing Configuration Synchronization :: https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/big-ip-device-service-clustering-administration-14-1-0/05.html, in the section: Enabling and disabling automatic sync.) 11) Bring device back online. (Note: To do so, use the processes described in K15122: Overview of the Force Offline option :: https://support.f5.com/csp/article/K15122, in the section: Setting Minimum Blades Up on VIPRION systems or vCMP guests.) This should resolve the restjavad issue that causes the config save loop.

Fix Information

None

Behavior Change