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

Another master around

Udo Hillenbrand
Hello,
we have a switch from Slave to Master.
Last entry in the Master log:
2009:03:20-10:26:51 (none) ha_daemon[3027]: id="38A1" severity="warn" sys="System" sub="ha" name="Another master around!"
2009:03:20-10:26:51 (none) ha_daemon[3027]: id="38A0" severity="info" sys="System" sub="ha" name="Node 2 changed mode: SLAVE -> MASTER"

What is 'Another master around'?


On the Slave there are following entries:
2009:03:20-10:26:50 (none) ha_daemon[3011]: id="38B0" severity="info" sys="System" sub="ha" name="Switching to Master mode"
2009:03:20-10:26:50 (none) ctsyncd: Got SIGUSR1, set status to MASTER
2009:03:20-10:26:51 (none) ha_daemon[3011]: id="38A1" severity="warn" sys="System" sub="ha" name="Another master around!"
2009:03:20-10:26:51 (none) ha_daemon[3011]: id="38C0" severity="info" sys="System" sub="ha" name="Node 1 is alive!"
2009:03:20-10:26:51 (none) ha_daemon[3011]: id="38A1" severity="warn" sys="System" sub="ha" name="Current load average 13.60 of node 1 is to high, please check you system!"
2009:03:20-10:26:51 (none) ha_daemon[3011]: id="38A0" severity="info" sys="System" sub="ha" name="Node 1 changed state: DEAD -> ACTIVE"
2009:03:20-10:26:51 (none) ha_daemon[3011]: id="38A0" severity="info" sys="System" sub="ha" name="Node 1 changed mode: SLAVE -> MASTER"


What is the error?

MFG Udo Hillenbrand


This thread was automatically locked due to age.
  • 0
    "DEAD" "Alive" "Current load average 13.60 of node 1 is to high, please check you system!"

    There are two masters when, for example, Node2 comes alive but doesn't get a heartbeat from Node1, the active master.  Node2 assumes that it's supposed to become the master.  Then, Node2 sees the heartbeat and that Node1 is master.  Then you get the "two masters" message.  The two nodes should have compared to see which one had the earliest up-time, and the "older" one shoulld become the "master."

    If this is happening often or persistently, then I would suspect the physical connection between the HA ports - cables and/or switch.  If you are not running this on Astaro appliances, then you might check to see if both the primary and backup Ethernet interfaces are confirmed to work for the heartbeat.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Cookie Information Banner