Bug ID 1580369: MCPD thrown exception when syncing from active device to standby device.

Last Modified: Dec 05, 2024

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2

Opened: Apr 19, 2024

Severity: 3-Major

Symptoms

Config sync fails on the secondary blade and MCPD restarts. In /var/log/ltm: err mcpd[7906]: 0107134b:3: (rsync: link_stat "/config/filestore/.snapshots_d/custom_urldb_d/:Common:custom_feedlist_348871_3751" (in csync) failed: No such file or directory (2) ) errno(0) errstr(). err mcpd[7906]: 0107134b:3: (rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1518) [Receiver=3.0.9] ) errno(0) errstr(). err mcpd[7906]: 0107134b:3: (syncer /usr/bin/rsync failed! (5888) () Couldn't rsync files for mcpd. ) errno(0) errstr(). err mcpd[7906]: 0107134b:3: (rsync process failed.) errno(255) errstr(). err mcpd[7906]: 01070712:3: Caught configuration exception (0), Failed to sync files..

Impact

Config sync to the secondary blade fails and MCPD throws an exception and restarts on the secondary. The cluster primary blade has the correct custom_urldb file. This will impact incremental syncing to other peers in the device group.

Conditions

- A BIG-IP system with multiple blades and multiple slots configured for high availability - Active device has to download the custom_urldb file from a server - A config sync occurs

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips