OPNsense Forum
Archive => 22.7 Legacy Series => Topic started by: PIv0 on July 28, 2022, 06:43:09 pm
-
Hi all!
Updated from version 22.1.10 to 22.7, first through the web interface, then through reinstallation from the CD and restoring the saved settings.
Did not help.
On the previous version, synchronization between the master device and the backup worked fine and without problems.
After the update, synchronization stopped working, when I go to the menu item "System - High Availability - Status" I get the following line:
The backup firewall is not accessible or not configured.
-
I have the same problem since the upgrade
-
I have the same issue. Running /usr/local/etc/rc.filter_synchronize debug results in 'parse error. not well formed'
Maybe this is a regression as there was a issue in the past triggered the same behavior.
-
I have exactly the same problem.
After upgrading from version 22.1.10 to 22.7 HA sync stopped working.
And the message is "The backup firewall is not accessible or not configured."
-
'parse error. not well formed'
So that's the output on the 22.1 or 22.7 system?
My guess would be 22.1?
Cheers,
Franco
-
'parse error. not well formed'
i have the message on 22.7
-
Yikes, thanks, we will look into it as soon as possible.
Cheers,
Franco
-
Here the same, HA sync was working on 22.1.10 and now after the upgrade to 22.7 I get the message:
"The backup firewall is not accessible or not configured."
-
'parse error. not well formed'
So that's the output on the 22.1 or 22.7 system?
My guess would be 22.1?
Cheers,
Franco
No, the sync was broken after upgraded both instances to 22.7. Before the upgrade XMLRPC sync was running fine.
-
@rsk I was just trying to understand if this issue appeared on 22.7 talking to 22.7 or on 22.1 talking to 22.7.
Cheers,
Franco
-
@rsk I was just trying to understand if this issue appeared on 22.7 talking to 22.7 or on 22.1 talking to 22.7.
This question appeared on 22.7 in a conversation with 22.1.
I first updated the master, and he had already lost contact with the backup, on which there was 22.1
-
Ok, so this is the client side issue on 22.7, likely because of PHP 8. My colleague is on it. :)
Cheers,
Franco
-
Should be https://github.com/opnsense/core/commit/65ceba42f3
However, this can't be patched with opnsense-patch so I'm going to post a manual package install here in a bit.
Cheers,
Franco
-
# pkg add -f https://pkg.opnsense.org/FreeBSD:13:amd64/22.7/MINT/22.7_4/OpenSSL/All/opnsense-22.7_4.pkg
Cheers,
Franco
-
# pkg add -f https://pkg.opnsense.org/FreeBSD:13:amd64/22.7/MINT/22.7_4/OpenSSL/All/opnsense-22.7_4.pkg
Thank you! Earned!
-
It's been published now as well.
Cheers,
Franco
-
Thank you. Working for me now. :)
-
Thank you for fixing this so fast. It works now.
-
I have the same problem too. Trying from the command line, I get:
# /usr/local/etc/rc.filter_synchronize
send >>>
Host: xxx.xxx.xxx.xxx
User-Agent: XML_RPC
Content-Type: text/xml
Content-Length: 117
Authorization: Basic xxxxxxxxxxxxxxxxxxxxx
<?xml version="1.0"?>
<methodCall>
<methodName>opnsense.firmware_version</methodName>
<params>
</params></methodCall>received >>>
error >>>
fetch error. remote host down?
How can I solve the issue?
-
Upgrade to the latest version.
https://forum.opnsense.org/index.php?topic=29507.msg142671#msg142671
-
I am still seeing this error. Is it still safe to attempt to apply the patch above to the latest OpnSense? Has this made its way into the main tree? Thanks.
-
I have now made it go away, probably by disabling and re-enabling some things.