Upgrade 2.2.1 -> 2.2.2 no sync anymore



  • After upgrading vom 2.2.1 to 2.2.2 I can't get syncing to work again.
    The systems are configure according to https://doc.pfsense.org/index.php/CARP_Configuration_Sync_Troubleshooting

    Logs:
    Apr 20 09:47:07 php-fpm: /rc.filter_synchronize: New alert found: An error code was received while attempting Filter sync with username admin https://… - Code 2: Invalid return payload: enable debugging to examine incoming payload

    After hours of researching I am at lost about this issue. Can anyone guide me how to troubleshoot / debug this problem?

    thx
    norbert



  • Meanwhile I was able to extract the xml-rpc payload coming from the node to which the first node syncs.
    But it looks valid, then why is pfsense complaining about invalid return payload?

    
     <methodresponse><params><param>
     <value><struct><member><name>firmware</name>
     <value><struct><member><name>version</name>
    <value><string>2.2.2-RELEASE</string></value></member></struct></value></member> 
    <member><name>kernel</name>
     <value><struct><member><name>version</name>
    <value><string>10.1</string></value></member></struct></value></member> 
    <member><name>base</name>
     <value><struct><member><name>version</name>
    <value><string>10.1</string></value></member></struct></value></member> 
    <member><name>platform</name>
    <value><string>pfSense</string></value></member> 
    <member><name>config_version</name>
    <value><string>11.7</string></value></member></struct></value></params></methodresponse> 
    
     <methodresponse><params><param>
    <value><boolean>1</boolean></value></params></methodresponse> 
    
     <methodresponse><params><param>
    <value><boolean>1</boolean></value></params></methodresponse> 
    
    


  • I exported the payload into a file which revealed lines that were not displayed on the web interface in the crash report. See below for the actual payload.
    You see some error messages which come from the pfsense dns server and of course are invalid xml rpc code.
    When we disable the dns server the sync works without errors. This is a bug imho.

    Opening file /etc/inc/unbound.inc and looking at line 239 it reveals that there is a function get_dns_servers. And this function is implemented differently
    in 2.2.1 and 2.2.1. and seems to be responsible for the error.

    
     <methodresponse><params><param>
     <value><struct><member><name>firmware</name>
     <value><struct><member><name>version</name>
    <value><string>2.2.1-RELEASE</string></value></member></struct></value></member> 
    <member><name>kernel</name>
     <value><struct><member><name>version</name>
    <value><string>10.1</string></value></member></struct></value></member> 
    <member><name>base</name>
     <value><struct><member><name>version</name>
    <value><string>10.1</string></value></member></struct></value></member> 
    <member><name>platform</name>
    <value><string>pfSense</string></value></member> 
    <member><name>config_version</name>
    <value><string>11.7</string></value></member></struct></value></params></methodresponse> 
     <methodresponse><params><param>
    <value><boolean>1</boolean></value></params></methodresponse> 
    Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/unbound.inc on line 239
    
    Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/unbound.inc on line 239
    
    Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/unbound.inc:239) in /etc/inc/xmlrpc_server.inc on line 431
    
    Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/unbound.inc:239) in /etc/inc/xmlrpc_server.inc on line 431
    
     <methodresponse><params><param>
    <value><boolean>1</boolean></value></params></methodresponse> 
    
    


  • Hi,

    Check this out : https://forum.pfsense.org/index.php?topic=92437.0 and the related patch.



  • Thanks a lot for the hint Gertjan!


Log in to reply