Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    Code 2: Invalid return payload: enable debugging to examine incoming payload

    2.1 Snapshot Feedback and Problems - RETIRED
    1
    1
    1820
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      Tom Hall last edited by

      Hi,

      I have two pfsense boxes set up with latest 2.1-beta0.
      These two share a few addresses with CARP and sync their config.

      As soon as I change any configuration in the primary server I receive the message "Code 2: Invalid return payload: enable debugging to examine incoming payload"

      It seems that the config actually was syncronized ok. If I backup the config on the primary and secondary servers and compare these files, they are the same except for things that you could expect to differ, like ipaddress on the interfaces etc.

      I fired up tcpdump and examined the sync traffic and found that the server does not return any xml, just the text "waiting for pfsync…"
      I searched for this message in the secondary server and found it in just one place, /etc/inc/interfaces.inc.

      If I comment out this echo line and two more, the error will not show up anymore, but still there are no xml returned to the master.

      Does someone else experience this problems?
      Is it a problem with my setup/settings or could it be considered a bug?

      /T

      1 Reply Last reply Reply Quote 0
      • First post
        Last post