|
Hi
Just thinking out loud... are these two getting trapped in a sort of
"deadlock" - syncmaster1 multicasts, syncbackup2 picks it up,
syncmaster2 sends it back via multicast, syncbackup1 picks it up, and
so on, and so forth.
I notice that you're not setting the --syncid flag in your command
lines. Wouldn't that mean they're both using the same ID, and therefore
continually "swapping" data as described above?
--syncid syncid
Specify the syncid that the sync master daemon fills in the
SyncID header while sending multicast messages, or the sync
backup daemon uses to filter out multicast messages not matched
with the SyncID value. The valid values of syncid are 0 through
to 255. The default is 0, which means no filtering at all.
I'd try a unique syncid for syncmaster1/syncbackup2, and a separate one
for syncmaster2/syncbackup1.
Graeme
|
