Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 1 reply
  • Subscribers 4 subscribers
  • Views 1365 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

9.713019 installed - HA issue: rsync: failed to connect to 198.19.250.1: Connection refused (111)

LHerzog

Upgraded from Sophos UTM 9.712-13 to 9.713-19

Sa 14.01.2023 07:17

Node 1 Master:

New Firmware Up2Dates have been installed. The current firmware version is now 9.713019.

Node 2 preserved until

Mo 16.01.2023 02:33

Node 2 Save:

New Firmware Up2Dates have been installed. The current firmware version is now 9.713019.

After Slave has been upgraded we receive mails: HA selfcheck

In HA Logs the most relevant error is: HA issue: rsync: failed to connect to 198.19.250.1: Connection refused (111)

Probably database was broken.

created support case: 06094063



This thread was automatically locked due to age.
Parents
  • +1

    Fix:

    Support provided solution to rebuild progress database:

    From the above logs we can see there might be an issue with postgres database got corrupted can you please run below command to rebuild postgres database than let us know if HA status got changed or not

Step 1: login to master node, su to root
Step 2: open a new ssh window, login to master again, su to root
Step 3: on 2nd window, enter: ha_utils ssh
Step 4: in the 2nd window, login to slave as loginuser, then su to root
Step 5: on both ssh windows, enter: killall repctl
Step 6: on both ssh windows, enter: /etc/init.d/postgresql92 rebuild
Step 7: after database rebuilds, enter on both ssh windows: repctl

Note: Database rebuild activity will cause SMTP service restart and might lose the 48-72 hrs of reporting date, no RCA (Root Caused Analysis) provided after rebuild of database request you perform the activity during downtime or after working hours

    HA synced successfully and HA is now good again.

Reply
  • +1

    Fix:

    Support provided solution to rebuild progress database:

    From the above logs we can see there might be an issue with postgres database got corrupted can you please run below command to rebuild postgres database than let us know if HA status got changed or not

Step 1: login to master node, su to root
Step 2: open a new ssh window, login to master again, su to root
Step 3: on 2nd window, enter: ha_utils ssh
Step 4: in the 2nd window, login to slave as loginuser, then su to root
Step 5: on both ssh windows, enter: killall repctl
Step 6: on both ssh windows, enter: /etc/init.d/postgresql92 rebuild
Step 7: after database rebuilds, enter on both ssh windows: repctl

Note: Database rebuild activity will cause SMTP service restart and might lose the 48-72 hrs of reporting date, no RCA (Root Caused Analysis) provided after rebuild of database request you perform the activity during downtime or after working hours

    HA synced successfully and HA is now good again.

Children
No Data
Unfiltered HTML