[ZBX-26970] Zabbix startup stuck on "started configuration syncer" Created: 2025 Sep 09 Updated: 2025 Sep 12 |
|
| Status: | Open |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Adi Rusmanto | Assignee: | Maksym Buz |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Description |
|
I deployed a Zabbix server using the Docker image zabbix-server-pgsql:7.0.6-alpine. The problem is that my configuration cache usage exceeds 90%. I reconfigured the Zabbix container by increasing the CacheSize parameter from 20 GB to 30 GB. However, when I restarted the Zabbix server container, it got stuck at the process: I also checked the server resource usage. During startup, the Zabbix server consumed almost all available RAM, leaving only around 100 MB, which made the server unresponsive. I then rolled back the CacheSize parameter to 20 GB, but after restarting, the Zabbix server container was still stuck and continued to consume all available RAM. I don’t understand how the configuration cache works and why Zabbix is consuming almost all of the RAM. If the RAM usage should match the configured CacheSize, it shouldn’t be using all the available memory. When the Zabbix server container is stopped, there’s still around 40 GB of free RAM. Is there any workaround to solve this issue? |
| Comments |
| Comment by Alexey Pustovalov [ 2025 Sep 10 ] |
|
Please share Zabbix server log file with enabled debug level 4. After 20 minutes from startup. |
| Comment by Adi Rusmanto [ 2025 Sep 10 ] |
|
please check here is the log file from docker container. a8da9fa431f082dbff83c555c4a39f88036074a566429cb1c660dae70b721254-json.log |
| Comment by Alexey Pustovalov [ 2025 Sep 10 ] |
|
Sorry, but what is the issue?
{"log":" 1:20250910:080715.563 \"pv-snmptbs1-zab24-11\" node started in \"standby\" mode\n","stream":"stdout","time":"2025-09-10T01:07:15.56356043Z"}
|
| Comment by Adi Rusmanto [ 2025 Sep 10 ] |
|
Seems, it happened when I initiate stop zabbix-server container. Because the server became unresponsive since lack of RAM. |
| Comment by Adi Rusmanto [ 2025 Sep 10 ] |
|
Or maybe because the other zabbix-server is taking over, becasuse that server is unresponsive. |