High Availability Sync - XMLRPC Errors After Update



  • Hello,

    I have just upgraded a master and a backup pfsenses from version 2.2.6 to the latest version 2.4.2. These are two virtual machines.
    I have HA Proxy, OSPF, Open-VM-Tools and squid packages installed. Working fine.

    When I change something on the Master, I see the changes being reflected to the Backup pfsense. But I still get this error:

    Exception calling XMLRPC method filter_configure # String could not be parsed as XML @ 2017-12-01 18:38:53

    I connected to both pfsenses via SSH couple of times and used the option 16  "Restart PHP-FPM" But if I change something after that, the same errors are keep coming.

    I've also received the following long error notice after receiving the above error a few times. I never received this error again. I keep getting the one on above.

    I have one IP Alias configured under Firewall/Virtual IPs, and 11-12 CARPs. The IP Alias type VIP has one of the CARP as Interface. I tried this because in the past I read in here that this might stop the error. 2.2.X versions never had the chronic XMLRPC errors. I used to use option 16 and I wasn't seeing them for a year.

    Any idea how to resolve this problem? I just don't know what approach will take me to the bottom of this to understand the real root cause.

    The Long Error:
    Exception calling XMLRPC method filter_configure # Received non-200 HTTP Code: 502. Response body:<html>
    <head><title>502 Bad Gateway</title></head>
    <body bgcolor="white">
    <center><h1>502 Bad Gateway</h1></center>
    <hr><center>nginx</center>
    </body>
    </html>
    @ 2017-12-01 18:28:54
    Exception calling XMLRPC method filter_configure # Received non-200 HTTP Code: 502. Response body:<html>
    <head><title>502 Bad Gateway</title></head>
    <body bgcolor="white">
    <center><h1>502 Bad Gateway</h1></center>
    <hr><center>nginx</center>
    </body>
    </html>
    @ 2017-12-01 18:28:55
    Exception calling XMLRPC method filter_configure # Received non-200 HTTP Code: 502. Response body:<html>
    <head><title>502 Bad Gateway</title></head>
    <body bgcolor="white">
    <center><h1>502 Bad Gateway</h1></center>
    <hr><center>nginx</center>
    </body>
    </html>
    @ 2017-12-01 18:28:56



  • I have just attached the amount of the errors. I get them for any config saving. This worries me a lot.

    ![Sync XMLRPC Errors.JPG](/public/imported_attachments/1/Sync XMLRPC Errors.JPG)
    ![Sync XMLRPC Errors.JPG_thumb](/public/imported_attachments/1/Sync XMLRPC Errors.JPG_thumb)


Log in to reply