Caught configuration exception (0), Can't find monitor rule

Hey Michael J, have you thought about simply creating a sync-only device group and then enabling the APM policy sync feature? As long as you are trying to sync to five or fewer group members and network communication between the members is reliable, this should just work.

 

I would look at my pool configurations, and make sure that there aren't any custom monitors specified at either the pool or member level, where the monitors don't exist locally. You might be running into " target="_blank">this issue.

 

I've tried that. That's what got me into this predicament to begin with :).

I've created the sync-only group (had to specify Automatic Sync and Full Sync before I could even select the group from the Policy sync list). Once I tried to sync, it would say Sync Initiated for the device I was syncing from, and Not Available for the other devices sync status.

In the logs, on the original device, I see the error message The requested Policy Sync Status (/Common/[RestOfObjectName]) was not found.

On the other device I get a bunch of log entries:

 

(rsync: link_stat "/.snapshots_d/policy_sync_d/:Common:POLICYSYNC_AAA_TEST:AAA_TEST_psd_data_168879_1" (in cmi) failed: No such file or directory (2) ) errno(0) errstr().
(rsync: link_stat "/.snapshots_d/policy_sync_d/:Common:POLICYSYNC_AAA_TEST:AAA_TEST_psd_file_168883_1" (in cmi) failed: No such file or directory (2) rsync: link_stat "/.snapshots_d/policy_sync_d/:Common:POLICYSYNC_AAA_TEST:AAA_TEST_psd_list_168881_1" (in cmi) failed: No such file or directory (2) ) errno(0) errstr().
(rsync error: some files could not be transferred (code 23) at main.c(1298) [receiver=2.6.8] ) errno(0) errstr().
(syncer /usr/bin/rsync failed! (5888) () Couldn't rsync files for mcpd. ) errno(0) errstr().
(rsync process failed.) errno(255) errstr().
Loading keys from the file.
Caught configuration exception (0), Failed to sync files..
Remote transaction for device group /Common/POLICY_SYNC_GROUP to commit id 355 6081167190376551560 /Common/[DeviceNameHere] 0 failed with error 01070712:3: Caught configuration exception (0), Failed to sync files...
(rsync: link_stat "/.snapshots_d/policy_sync_d/:Common:POLICYSYNC_AAA_TEST:AAA_TEST_psd_data_168879_1" (in cmi) failed: No such file or directory (2) ) errno(0) errstr().
(rsync: link_stat "/.snapshots_d/policy_sync_d/:Common:POLICYSYNC_AAA_TEST:AAA_TEST_psd_file_168883_1" (in cmi) failed: No such file or directory (2) rsync: link_stat "/.snapshots_d/policy_sync_d/:Common:POLICYSYNC_AAA_TEST:AAA_TEST_psd_list_168881_1" (in cmi) failed: No such file or directory (2) 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().
(rsync process failed.) errno(255) errstr().
Loading keys from the file.
Caught configuration exception (0), Failed to sync files..
Remote transaction for device group /Common/POLICY_SYNC_GROUP to commit id 356 6081167199119309638 /Common/[DeviceNameHere] 1 failed with error 01070712:3: Caught configuration exception (0), Failed to sync files...
Loading keys from the file.
Sync of device group /Common/POLICY_SYNC_GROUP to commit id 359 6081167465374670520 /Common/[DeviceNameHere] 2 from device /Common/[DeviceNameHere] complete.
Sync of device group /Common/POLICY_SYNC_GROUP to commit id 359 6081167465374670520 /Common/[DeviceNameHere] 2 from device  complete.

 

We are running different minor version on these boxes. One is running BIG-IP 11.5.0 Build 4.26.245 Engineering Hotfix HF4 and the other is running BIG-IP 11.5.0 Build 2.0.231 Hotfix HF2. Only other thing is after I added both devices to the group, the status in the top left says Awaiting Initial Sync. I haven't seen in the docs that I need to do anything with this before the policy sync will work, so I haven't tried (that, and I don't want to overwrite any config other than the policies on my other device)

Try the following to correct the issue:

 

1) Reloaded the configuration by executing command

 

tmsh load sys config

If the issue is not resoloved

 

2) Restarted the tmm by executing command

 

bigstart restart tmm

If the issue is still not resoloved

 

3) Reboot the F5 should resolve the issue.

 

Issue is still not resolved open F5 support case.

 

• Syed