XMLRPC Sync error. built on Sun Sep 20 01:01:05 EDT 2020

w0w

I have 2.4.5-RELEASE-p1 as backup and 2.5.0-DEVELOPMENT (amd64)
built on Sun Sep 20 19:04:20 as primary, sync DHCP Server settings is enabled, but I do not have XMLRPC Sync error and I have never got it.

Raul Ramos

I will toggle some options and check if i can enable DHCP settings for XMLRPC sync.

I will be back... I'm back.

Update, nothing solve the problem:
Tried change some settings like: delete extra range, clean network booting form and disable, disable all DHCP networks, check "Ping check", disable static ARP for mome mappings.

What i have configured: Enable (on 3 networks), range (in Lan ), DNS servers ( configured one in each net), gateway, Failover peer IP, Ping check is checked, a bunch of static mappings (do not tried delete this ones).

Raul Ramos

Cannot edit post anymore, 300s. I'm not English speaker. Take me more time to write this.

Errata: range (in Lan ) i mean -> range (in Lan i have a extra range).

w0w

Your English is OK for me
Do your CARP pfSenses using same pfSense versions? 2.5?

Raul Ramos

Yes. Same versions, except a couple minutes later. First i see if everything necessary runs fine and then update the slave (we should not use slave anymore right? whatever).

Raul Ramos

DHCPD from config with some changes

dhcpd.xml

I have no IPv6 active at this moment

w0w

I am not sure is it related but only XML parser changes were made on this week.
https://github.com/pfsense/pfsense/pull/4432
I think latest patch will be available in the next snapshot.
But may be it is something else. Try it tomorrow.

w0w

@Raul-Ramos how it is going with the latest version?

viktor_g

Please create a bugreport:
https://docs.netgate.com/pfsense/en/latest/development/bug-reports.html

Raul Ramos

@w0w nothin with built on Thu Sep 24 01:03:45 EDT 2020 on the two boxes. Speaking in boxes, this is two qemu-kvm VM pfSenses.

@viktor_g said in XMLRPC Sync error. built on Sun Sep 20 01:01:05 EDT 2020:

Please create a bugreport:
https://docs.netgate.com/pfsense/en/latest/development/bug-reports.html

Not now. This is not a deal breaker problem. I will wait for someone with the same problem.
If not, could be fun when this version go final :).

w0w

I'll try to replicate it. When I have time.

w0w

Exception calling XMLRPC method restore_config_section # Impossible to encode value '' from type 'NULL'. No analogous type in XML_RPC. @ 2020-09-25 08:33:21
Exception calling XMLRPC method restore_config_section # Impossible to encode value '' from type 'NULL'. No analogous type in XML_RPC. @ 2020-09-25 08:33:22

Just un-ticked Services/DHCPv6 Server & RA/LAN/DHCPv6 Server
"Enable DHCPv6 server on interface LAN" option.

So @Raul-Ramos you need to create a bugreport.

Raul Ramos

@w0w c'mon create a burgreport? reality?
For some reason i write "I have no IPv6 active at this moment". It smell DHCPv6 from the moment i trim the xml config and see de DHCPv6 part.

But i try check and uncheck DHCPv6 server. I have a old hurricane electric ipv6 and tested with that on the lan interface, and same happens. I think is the only interface that have some IPv6 stuff.

Sunday, i will send a bug report, maybe.

w0w

Can you re-test with 2.5.0-DEVELOPMENT (amd64)
built on Fri Sep 25 19:04:06 EDT 2020
FreeBSD 12.2-PRERELEASE or later?
For some reason ca not replicate this error anymore.

Nevermind. ~~Only 2.5 version is affected, only when on both CARP ends is 2.5, When backup firewall is 2.4.5 then no error appears.~~
To replicate the error I have updated backup firewall to 2.5 version, after that, on primary firewall I've disabled IPv6 DHCP server and then enabled it again. Every time I got two error messages like

Exception calling XMLRPC method restore_config_section # Impossible to encode value '' from type 'NULL'. No analogous type in XML_RPC. @ 2020-09-26 11:23:33
Exception calling XMLRPC method restore_config_section # Impossible to encode value '' from type 'NULL'. No analogous type in XML_RPC. @ 2020-09-26 11:23:34

After that I've downgraded backup firewall back to 2.4.5-p1. But when I re-test DHCPv6 enable/disable option, error appears again. It looks like something else triggering this error.

Raul Ramos

My LAN interface is the only one that have a IPv6 IP, a Tunnel Broker with DHCPv6 settings enabled. Disable IPv6 IP the config maintain a DHCPv6 waste. I will take off that part from a config and restore and see if without that part the XMLRPC Sync runs. Maybe is on the dhcp6c.conf file.

Raul Ramos

Cleaning dhcpv6 settings and put back, change nothing.

I have nothing. I ask someone to put a better error report, at least in the dhcp section.

Thanks for reading this problem.

Cya

w0w

@Raul-Ramos
I have found that when I save anything in config, for example modifying firewall rule, saving changes triggers this error. And yes, when DHCP settings SYNC is disabled, there is no error message.

w0w

This post is deleted!

mleighton

Disabling the Failover Peer IP in the DHCP server settings has also resolved the issue in my testing. I've created a bug report here: https://redmine.pfsense.org/issues/10955

Raul Ramos

I tried check, delete, populate so many options... i have the right missing a couple of them.

Thanks for creating the redmine.