High Availability Sync CARP



  • I tested my hardware with Pfsense 2.2

    I tried to use CARP.

    When I push the rules from master to slave I Received this error

    "An error code was received while attempting XMLRPC sync with username admin https://192.168.1.3:443 - Code 2: Invalid return payload: enable debugging to examine incoming payload"

    I check via ssh the log.

    tail -f /var/log/system.log

    May 16 15:17:21 118-cav-fw1 php-fpm[249]: /rc.filter_synchronize: An error code was received while attempting XMLRPC sync with username admin https://192.168.1.3:443 - Code 2: Invalid
    return payload: enable debugging to examine incoming payload

    I run via ssh the command rc.filter_synchronize

    [[b]2.2-ALPHA][admin@118-cav-fw1.118.asf.locale]/etc(23): /etc/rc.filter_synchronize

    –-SENT---
    POST /xmlrpc.php HTTP/1.0
    User-Agent: PEAR XML_RPC
    Host: 192.168.1.3
    Authorization: Basic YWRtaW46cGZzZW5zZQ==
    Content-Type: text/xml
    Content-Length: 206
    
     <methodcall><methodname>pfsense.host_firmware_version</methodname>
     <params><param>
    <value><string>pfsense</string></value></params></methodcall> 
    
    ---END---
    
    ---GOT---
    HTTP/1.0 200 OK
    Expires: Sun, 18 May 2014 17:32:48 GMT
    Cache-Control: max-age=180000
    Content-type: text/html
    Connection: close
    Date: Fri, 16 May 2014 15:32:48 GMT
    Server: lighttpd/1.4.35
    
    Warning: file_get_contents(/etc/version_kernel): failed to open stream: No such file or directory in /etc/inc/pfsense-utils.inc on line 765
    
    Warning: file_get_contents(/etc/version_base): failed to open stream: No such file or directory in /etc/inc/pfsense-utils.inc on line 766
    
    Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/pfsense-utils.inc:765) in /etc/inc/xmlrpc_server.inc on line 431
    
    Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/pfsense-utils.inc:765) in /etc/inc/xmlrpc_server.inc on line 431
    
     <methodresponse><params><param>
     <value><struct><member><name>firmware</name>
     <value><struct><member><name>version</name>
    <value><string>2.2-ALPHA</string></value></member></struct></value></member> 
    <member><name>kernel</name>
     <value><struct><member><name>version</name>
    <value></value></member></struct></value></member> 
    <member><name>base</name>
     <value><struct><member><name>version</name>
    <value></value></member></struct></value></member> 
    <member><name>platform</name>
    <value><string>pfSense</string></value></member> 
    <member><name>config_version</name>
    <value><string>10.7</string></value></member></struct></value></params></methodresponse> 
    ---END---
    

  • Rebel Alliance Developer Netgate

    I think I see a potential problem. I committed a fix, but for a fast test, try this on both (or at least the secondary):

    echo 10.0 > /etc/version_base
    echo 10.0 > /etc/version_kernel

    Then do another sync test.



  • @jimp:

    I think I see a potential problem. I committed a fix, but for a fast test, try this on both (or at least the secondary):

    echo 10.0 > /etc/version_base
    echo 10.0 > /etc/version_kernel

    Then do another sync test.

    This Solved for me, running 2 box 2.2 on Vmware workstation 10. Done only on backup box solved.

    Dummy question, need to redo after a restart ?

    Robert Jr


  • Rebel Alliance Developer Netgate

    No need to redo or reboot anything. Mostly the secondary box matters since it's the one that gets its version polled.

    Putting those files in place is fine they should stay even after an upgrade unless it's nanobsd.



  • I confirm that this solved also for me. When I push the new rules from master to slave is working now without problems.

    I just found only the little problem with the Virtual ip CARP description.

    When I create Virtual ip is ok, then when i try to modify the description I receved this message

    "
    The following input errors were detected:

    This IP address is being used by another interface or VIP."

    The only solution thant I found is delete and recreate the Virtual Ip CARP.

    thank you


Log in to reply