• Icon: Incident report Incident report
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • None
    • Support backlog

      When Zabbix has multiple nodes, all nodes except one are stopped. Then last node (active one) died or killed using sigkill, no way to reset current cluster status. Have to wait failover delay period:
      Old node:

       213:20240607:173444.500 starting HA manager
           7:20240607:173444.508 cannot start server: found active duplicate "f272e683cf93" node
         213:20240607:173444.508 HA manager has been stopped
      

      New node:

        237:20240607:173612.095 starting HA manager
         237:20240607:173612.107 HA manager started in standby mode
           7:20240607:173612.107 "a9fd50ba4fc7" node started in "standby" mode
      

            zabbix.dev Zabbix Development Team
            dotneft Alexey Pustovalov
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: