Hi everyone
We are facing some instability issues with Zabbix Agent 2 (7.0.12) after migrating the server to 7.0.13
On some Windows Server 2022 hosts running Zabbix Agent 2 (7.0.12), we are seeing issues where the service just dies and won’t restart, even if the service is set to automatically restart. When looking at the log (Level 4) all we can see that might be related is:
"lowering the plugin ZabbixSync capacity to hard limit 1 as the configured capacity 1000 exceeds limits"
We tried what’s recommended in this thread with no luck, it’s still happening:
Interestingly, two of these 2022 servers were provisioned at the same time from the same VMware template, yet only one is affected by this problem (same installer, same config). Overall, it seems to affect only a very small percentage of our Windows Server 2022 hosts, and mostly seems isolated to this OS. We had sparse, similar issues with a couple of other servers running Windows Server 2003 (Zabbix Agent 5.4.12) and Windows Server 2008 R2 (Zabbix Agent 7.0.3) but to be honest, we just shrugged it off as a legacy OS problem.
Since we need to keep everything monitored anyway, and as a troubleshooting method, we switched back to Zabbix Agent 7.0.12 and the problem disappeared.
Has anyone else had or currently have this problem and any insight?
Here’s our configuration
Zabbix Web/Server
Zabbix 7.0.13
2 servers in Native HA
Ubuntu 22.04
6 CPU / 8GB RAM
Zabbix Database
Single server
PostgreSQL 17.5 + TimescaleDB 2.17.2
Ubuntu 24.04
12 CPU / 32GB RAM
Thanks!
We are facing some instability issues with Zabbix Agent 2 (7.0.12) after migrating the server to 7.0.13
On some Windows Server 2022 hosts running Zabbix Agent 2 (7.0.12), we are seeing issues where the service just dies and won’t restart, even if the service is set to automatically restart. When looking at the log (Level 4) all we can see that might be related is:
"lowering the plugin ZabbixSync capacity to hard limit 1 as the configured capacity 1000 exceeds limits"
We tried what’s recommended in this thread with no luck, it’s still happening:
Interestingly, two of these 2022 servers were provisioned at the same time from the same VMware template, yet only one is affected by this problem (same installer, same config). Overall, it seems to affect only a very small percentage of our Windows Server 2022 hosts, and mostly seems isolated to this OS. We had sparse, similar issues with a couple of other servers running Windows Server 2003 (Zabbix Agent 5.4.12) and Windows Server 2008 R2 (Zabbix Agent 7.0.3) but to be honest, we just shrugged it off as a legacy OS problem.
Since we need to keep everything monitored anyway, and as a troubleshooting method, we switched back to Zabbix Agent 7.0.12 and the problem disappeared.
Has anyone else had or currently have this problem and any insight?
Here’s our configuration
Zabbix Web/Server
Zabbix 7.0.13
2 servers in Native HA
Ubuntu 22.04
6 CPU / 8GB RAM
Zabbix Database
Single server
PostgreSQL 17.5 + TimescaleDB 2.17.2
Ubuntu 24.04
12 CPU / 32GB RAM
Thanks!
Comment