Last Modified: Dec 15, 2020
See more info
Known Affected Versions:
18.104.22.168, 14.0.0, 22.214.171.124, 13.1.1, 126.96.36.199, 12.1.5, 12.1.4, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168
Opened: Oct 10, 2018
Upon modifying file objects on a VIPRION chassis and synchronizing those changes to another VIPRION chassis in a device sync group, the following symptoms may occur: 1. Errors are logged to /var/log/ltm similar to the following: -- err mcpd[<#>]: 0107134b:3: (rsync: link_stat "/config/filestore/.snapshots_d/<_additional_path_to/_affected_file_object_>" (in csync) failed: No such file or directory (2) ) errno(0) errstr(). -- err mcpd[<#>]: 0107134b:3: (rsync error: some files could not be transferred (code 23) at main.c(1298) [receiver=2.6.8] syncer /usr/bin/rsync failed! (5888) () Couldn't rsync files for mcpd. ) errno(0) errstr(). -- err mcpd[<#>]: 0107134b:3: (rsync process failed.) errno(255) errstr(). -- err mcpd[<#>]: 01070712:3: Caught configuration exception (0), Failed to sync files.. 2. MCPD may restart on a secondary blade in a VIPRION chassis that is receiving the configuration sync from the chassis where the file object changes were made.
Temporary loss of functionality, including interruption in traffic, on one or more secondary blades in one or more VIPRION chassis that are receiving the configuration sync.
This can be encountered when rapidly making changes to files such as creating and then deleting them while the config sync of the file creation is still in progress.
After performing one set of file-object modifications and synchronizing those changes to the high availability (HA) group members, wait for one or more minutes to allow all changes to be synchronized to all blades in all member chassis before making and synchronizing changes to the same file-objects.