Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 5 subscribers
  • Views 831 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

Slave sends errors after a cluster update from 9.701 to 9.703

BeEf

I recently updated from our cluster from 9.701 to 9.703. In order to have a failback I only updated one node1 (reserve ...) and updated the second node one day later. 


Everything looks fine however I regularly got the following mail from the slave:

RED server not running - restarted
--
HA Status          : HA SLAVE (node id: 1)
System Uptime      : 0 days 6 hours 58 minutes
System Load        : 0.97
System Version     : Sophos UTM 9.703-3

Please refer to the manual for detailed instructions.

 

After another reboot of the slave this has changed to:



Log Disk is filling up - please check. Current usage: 91%
--
HA Status          : HA SLAVE (node id: 1)
System Uptime      : 0 days 6 hours 40 minutes
System Load        : 0.46
System Version     : Sophos UTM 9.703-3

Please refer to the manual for detailed instructions.

The logfile of the master is below 90% and the settings for the logfiles are 



There was no issue before the update. 

I think master and slave have been switched during the process:
- Old slave was updated. Changed to the new master.
- Old master became slave was put in reserve, then updated being still be slave.

Aren't the logfiles synchronized?

What can be done to get rid of these messages?



This thread was automatically locked due to age.
Parents
  • 0

    Hallo Bernd,

    The sure way to force everything back to "normal" is to force a Factory Reset on the Slave by disabling High Availability.  Then, after re-enabling, The Master will sync everything to the Slave anew.

    If you contact Sophos Support about this and they have a "safer" solution, please come back and share it with us.

    Cheers - Bob
    PS For others that find this and want to do the disable/enable manipulation as I suggest, here are the instructions I provide to my clients:

    1. On the current Master, on the 'Configuration' tab of 'High Availability':
       a. Disable and then enable Hot-Standby
       b. Select eth3 as the Sync NIC
       c. Configure it as Node_1
       d. Enter an encryption key (I've never found a need to remember it)
       e. Select 'Enable automatic configuration of new devices'
       f. I prefer to use 'Preferred Master: None' and 'Backup interface: Internal'
    2. Power up the Slave and wait for the good news. [;)]

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0

    Hallo Bernd,

    The sure way to force everything back to "normal" is to force a Factory Reset on the Slave by disabling High Availability.  Then, after re-enabling, The Master will sync everything to the Slave anew.

    If you contact Sophos Support about this and they have a "safer" solution, please come back and share it with us.

    Cheers - Bob
    PS For others that find this and want to do the disable/enable manipulation as I suggest, here are the instructions I provide to my clients:

    1. On the current Master, on the 'Configuration' tab of 'High Availability':
       a. Disable and then enable Hot-Standby
       b. Select eth3 as the Sync NIC
       c. Configure it as Node_1
       d. Enter an encryption key (I've never found a need to remember it)
       e. Select 'Enable automatic configuration of new devices'
       f. I prefer to use 'Preferred Master: None' and 'Backup interface: Internal'
    2. Power up the Slave and wait for the good news. [;)]

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data
Unfiltered HTML