Config sync error after 2.1-Release Upgrade.
-
Message:
php: rc.filter_synchronize: Config sync not being done because of missing sync IP (this is normal on secondary systems).I've now got a few boxes that upgraded from 2.0.3 to 2.1-Release that are showing this in the logs. None of the boxes have ever
been configured for CARP/HAS.Looking at the config files, I have:
<hasync><pfsyncenabled><pfsyncinterface>lan</pfsyncinterface> <pfsyncpeerip><synchronizetoip><username>admin</username> <password><synchronizeusers><synchronizecerts><synchronizerules><synchronizeschedules><synchronizealiases><synchronizenat><synchronizeipsec><synchronizeopenvpn><synchronizedhcpd><synchronizewol><synchronizestaticroutes><synchronizelb><synchronizevirtualip><synchronizetrafficshaper><synchronizetrafficshaperlimiter><synchronizetrafficshaperlayer7><synchronizednsforwarder><synchronizecaptiveportal></synchronizecaptiveportal></synchronizednsforwarder></synchronizetrafficshaperlayer7></synchronizetrafficshaperlimiter></synchronizetrafficshaper></synchronizevirtualip></synchronizelb></synchronizestaticroutes></synchronizewol></synchronizedhcpd></synchronizeopenvpn></synchronizeipsec></synchronizenat></synchronizealiases></synchronizeschedules></synchronizerules></synchronizecerts></synchronizeusers></password></synchronizetoip></pfsyncpeerip></pfsyncenabled></hasync>I'd like to get rid of these messages, I think I had a similar problem when I updated from 2.* to the snapshots, and I believe I
just got rid of that entire section of xml, and things were happy again.Is that the fix, or is there something else I can toggle there to fix it?
-
Blank out the sync username. Even if you didn't set it, on 2.0.x your browser may have auto-filled it.
