• Somewhere between a snapshot on the 18. of november and the current snapshot today (2.2-BETA (amd64) built on Tue Nov 25 01:23:50 CST 2014), config sync stopped working for me. I'm running two pfsense in a HA setup, and the logs display:

    php-fpm[29292]: /rc.filter_synchronize: New alert found: An error code was received while attempting XMLRPC sync with username admin http://<ip of="" secondary="">:80 - Code 2: Invalid return payload: enable debugging to examine incoming payload.

    I'm using the nano version, and if I switch the active slice, and boot up from the old one (from 18. of nov), then config sync starts working again. I tested it using the "Force config sync" button on the Filter Reload page.

    Does anyone else also have this issue?</ip>

  • Rebel Alliance Developer Netgate

    What does the log on the secondary show?

    There have been a few misc issues fixed just this morning that may have affected it as well, try it again after updating to a snapshot dated after this post.


  • Thanks for the reply jimp :)

    The System - General log on the secondary doesn't display anything out of the ordinary. No messages regarding XMLRPC or config sync. Any other logs I could check?
    Will update when a new snapshot is ready.


  • @jimp:

    There have been a few misc issues fixed just this morning that may have affected it as well, try it again after updating to a snapshot dated after this post.

    I'm afraid that it didnt help. Now running "2.2-BETA (amd64) built on Fri Nov 28 08:10:11 CST 2014", same issue. My test environment doesn't have this issue, so I'm assuming it has something to do with my config. How do I enable debugging to examine incoming payload?

    Edit:

    I executed /etc/rc.filter_synchronize on the primary. Gave a whole lot of output. This is a short version:

    
    

    ---SENT---
    POST /xmlrpc.php HTTP/1.0
    User-Agent: PEAR XML_RPC
    Host: 172.30.2.134
    Authorization: Basic ***************************
    Content-Type: text/xml
    Content-Length: 428131

    <methodcall><methodname>pfsense.restore_config_section</methodname>
    <params><param>
    <value><string>*****************</string></value>

    <param>

    ...snip....

    <value><array><data></data></array></value></params></methodcall>

    ---END---

    
    

    ---GOT---

    ---END---

    
    

  • Managed to resolve this by setting up the secondary from scratch. Created all interfaces required, and then got the configuration to synchronize.