XMLRPC Sync Error "parse error. not well formed"

[GOCE]

Recive now a XMLRPC sync error and don't know how to troubleshoot it.

This is my current version:

OPNsense 20.7.7_1-amd64
FreeBSD 12.1-RELEASE-p11-HBSD
OpenSSL 1.1.1i 8 Dec 2020

I have attached the error shown in the gui.

The Output of /usr/local/etc/rc.filter_synchronize:

</params></methodCall>received >>>
<?xml version="1.0"?>
<methodResponse>
  <fault>
    <value>
      <struct>
        <member>
          <name>faultCode</name>
          <value><int>-32700</int></value>
        </member>
        <member>
          <name>faultString</name>
          <value><string>parse error. not well formed</string></value>
        </member>
      </struct>
    </value>
  </fault>
</methodResponse>
error >>>
parse error. not well formed

[GOCE]

It looks like the error happens only if I sync the firewall rules. With probably far more than 100 rules, what would be the most effective way to locate the rule casing the sync issue?

[fraenki]

It looks like the error happens only if I sync the firewall rules. With probably far more than 100 rules, what would be the most effective way to locate the rule casing the sync issue?

My config sync also stopped working.

Let's try the following:

- navigate to System: High Availability: Settings
- disable ALL "Configuration Synchronization Settings", except "Firewall Rules"
- try to synchronize the config to the backup firewall

In my case the sync works for individual items like "Firewall rules", but as soon as a number of items is enabled, the sync will fail.
I guess the sync failure is related to the size of the dataset that is being synced: if it is small enough the sync will succeed. Not sure how to debug this bug further...


Regards
- Frank

[fraenki]

Seems to be a known issue, I've just found this bug report:
https://github.com/opnsense/core/issues/4533

[GOCE]

Yeah, the bug report reads pretty much like what I have experienced.

Hope it gets fixed soon as the HA setup is now pretty much unusable.