OPNsense Forum

Archive => 15.7 Legacy Series => Topic started by: romain on August 06, 2015, 11:11:09 am

Title: Error HA XMLRPC sync not well formed
Post by: romain on August 06, 2015, 11:11:09 am

Hello,

I have this error in my console : An error occurred while attempting XMLRPC sync with username root and https://192.168.250.2:8888/xmlrpc.php parse error. not well formed

When I run the command :  /usr/local/etc/rc.filter_synchronize

I see that there is some PHP Warning and so the xml is not well formed :

Code: [Select]

Warning: Illegal string offset 'vip' in /usr/local/etc/inc/xmlrpc/legacy.inc on line 304

Warning: Invalid argument supplied for foreach() in /usr/local/etc/inc/xmlrpc/legacy.inc on line 304

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/etc/inc/xmlrpc/legacy.inc:304) in /usr/local/opnsense/contrib/IXR_Library.php on line 464

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/etc/inc/xmlrpc/legacy.inc:304) in /usr/local/opnsense/contrib/IXR_Library.php on line 465

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/etc/inc/xmlrpc/legacy.inc:304) in /usr/local/opnsense/contrib/IXR_Library.php on line 466

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/etc/inc/xmlrpc/legacy.inc:304) in /usr/local/opnsense/contrib/IXR_Library.php on line 467
<?xml version="1.0"?>
<methodResponse>
  <params>
    <param>
      <value>
      <boolean>1</boolean>
      </value>
    </param>
  </params>
</methodResponse>
error >>>
parse error. not well

I don't know where to looking for, any idea ?
Thank you

Title: Re: Error HA XMLRPC sync not well formed
Post by: AdSchellevis on August 10, 2015, 09:45:00 am

I seems to be missing a check if the element exists, it should be there, but for some reason it's not.

This commit https://github.com/opnsense/core/commit/f9dff13dd5a7456b3ab1c0ead25248d3ecc74d15 will check before doing anything with the entry. It will be in our next release.

When both machines have vips configured manually, this shouldn't happen. That could be a way to work around this issue.