High availability looping in audit logs

[paperman]

Hi, first post - sory for small knowledge about a topic.
I have a simple zabbix server with only 2 hosts. My server as one and hAp router from mikrotik as second one.
The mikrotik router is configure so it is communicating using SNMPv2 and it is working splendently, providing me with enough information to live a happy live . The tempate used is simply generic by SNMP (erlier it was set to mikrotik by snmp - but it didnt provide anouth information)

Now the issue started when I tried to add a new host with the same simple configuration. It was CCR1036-8G-2S+ and for it I used template with the same name and provided me with most information that I need but then zabbix server gave me a notiification:

Zabbix server is not running: the information displayd may not be current.

So I dug into it and find out in audit logs that it is spamming some updates: ( only two actually )

024-03-22 19:10:42	System		High availability node	0	Update	xxxxxxxxxxxxxxxxxxxxxxxxxx	hanode.status: 1 => 3
2024-03-22 19:10:32	System		High availability node	0	Update	xxxxxxxxxxxxxxxxxxxxxxxxxx	hanode.status: 3 => 1

I tried to find what item is cousing this and I figured only that it might be the template that I used but it is not sure to be true. Can someone explain what is going on ?
why the high availability status is updating every two seconds to mannually stopped and then to active ?

Kind thanks for every answer

[paperman]

Hi, I figured it out. I just went into file with logs and the thing was obvious then. The thing was that my zabbix server didn't have enough ChaseSize, so I've gone tnto the zabbix_server.conf to change it:

- StartPollers=250
- StartPollersUnreachable=280
- CasheSize= 64M

this is configuration that I use for now because this one ccr has on its own 11000 items in it so zabbix couldn't take it and it wanted to go on another zabbix_server node (or instance) to provide more power but when there isin't one it just switch from on to off on High Availability mode.

Happy to help if someone sees this

Jonasz

[paperman]

Hi, I figured it out. I just went into file with logs and the thing was obvious then. The thing was that my zabbix server didn't have enough ChaseSize, so I've gone tnto the zabbix_server.conf to change it:

- StartPollers=250
- StartPollersUnreachable=280
- CasheSize= 64M

this is configuration that I use for now because this one ccr has on its own 11000 items in it so zabbix couldn't take it and it wanted to go on another zabbix_server node (or instance) to provide more power but when there isin't one it just switch from on to off on High Availability mode.

Happy to help if someone sees this

Jonasz