After the update synchronization HA between the master and the backup not work

Started by PIv0, July 28, 2022, 06:43:09 PM

Previous topic - Next topic
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 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."

Quote from: rsk on July 28, 2022, 07:11:23 PM
'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


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."

Quote from: franco on July 28, 2022, 08:52:01 PM
Quote from: rsk on July 28, 2022, 07:11:23 PM
'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

Quote from: franco on July 29, 2022, 09:09:12 AM
@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