[ZBX-24007] Zabbix Server 6.4.11 won't start - configuration syncer crashes Created: 2024 Jan 29  Updated: 2024 Apr 24  Resolved: 2024 Jan 29

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Packages (C), Server (S)
Affects Version/s: 6.4.11rc1
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Dario Andres Susman Assignee: Zabbix Support Team
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Production

Attachments: PNG File image-2024-04-24-01-00-44-228.png     PNG File image-2024-04-24-01-23-22-348.png     PNG File image-2024-04-24-07-56-48-657.png     PNG File image-2024-04-24-12-40-18-060.png     PNG File image-2024-04-24-12-40-59-524.png     PNG File image-2024-04-24-12-41-40-754.png     PNG File image-2024-04-24-12-44-15-410.png    

 Description   

Steps to reproduce:

  1. Upgraded Zabbix packages from 6.4.10 to 6.4.11 (apt-get, Debian 12)

Result:

```

 1383:20240129:130411.709 Starting Zabbix Server. Zabbix 6.4.11 (revision fb6439a26e3).
  1383:20240129:130411.709 ****** Enabled features ******
  1383:20240129:130411.709 SNMP monitoring:           YES
  1383:20240129:130411.709 IPMI monitoring:           YES
  1383:20240129:130411.709 Web monitoring:            YES
  1383:20240129:130411.709 VMware monitoring:         YES
  1383:20240129:130411.709 SMTP authentication:       YES
  1383:20240129:130411.709 ODBC:                      YES
  1383:20240129:130411.709 SSH support:               YES
  1383:20240129:130411.709 IPv6 support:              YES
  1383:20240129:130411.709 TLS support:               YES
  1383:20240129:130411.709 ******************************
  1383:20240129:130411.709 using configuration file: /etc/zabbix/zabbix_server.conf
  1383:20240129:130411.889 current database version (mandatory/optional): 06040000/06040026
  1383:20240129:130411.889 required mandatory version: 06040000
  1393:20240129:130412.009 starting HA manager
  1393:20240129:130412.038 HA manager started in active mode
  1383:20240129:130412.039 server #0 started [main process]
  1395:20240129:130412.040 server #1 started service manager #1
  1396:20240129:130412.041 server #2 started configuration syncer #1
  1396:20240129:130416.342 __mem_malloc: skipped 19 asked 824008 skip_min 344 skip_max 712616
  1396:20240129:130416.352 __mem_malloc: skipped 19 asked 824008 skip_min 344 skip_max 712616
  1396:20240129:130416.352 === memory statistics for configuration cache ===
  1396:20240129:130416.352 free chunks of size     24 bytes:       23
  1396:20240129:130416.352 free chunks of size     32 bytes:       17
  1396:20240129:130416.352 free chunks of size >= 256 bytes:       19
  1396:20240129:130416.352 min chunk size:         24 bytes
  1396:20240129:130416.352 max chunk size:     712616 bytes
  1396:20240129:130416.352 memory of total size 29248096 bytes fragmented into 269123 chunks
  1396:20240129:130416.352 of those,    1550304 bytes are in       59 free chunks
  1396:20240129:130416.352 of those,   27697792 bytes are in   269064 used chunks
  1396:20240129:130416.352 of those,    4305952 bytes are used by allocation overhead
  1396:20240129:130416.352 ================================
  1396:20240129:130416.352 === Backtrace: ===
  1396:20240129:130416.353 15: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_backtrace+0x46) [0x5592cf4083e6]
  1396:20240129:130416.353 14: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](__zbx_shmem_realloc+0x3ef) [0x5592cf34d3bf]
  1396:20240129:130416.353 13: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_hashset_reserve+0x62) [0x5592cf372a72]
  1396:20240129:130416.353 12: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_hashset_insert_ext+0xa6) [0x5592cf372be6]
  1396:20240129:130416.353 11: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](dc_strpool_intern+0x6f) [0x5592cf2c51bf]
  1396:20240129:130416.353 10: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](dc_strpool_replace+0x31) [0x5592cf2c88b1]
  1396:20240129:130416.353 9: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0x1c3373) [0x5592cf2d4373]
  1396:20240129:130416.353 8: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](DCsync_configuration+0x27de) [0x5592cf2e1e3e]
  1396:20240129:130416.353 7: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](dbconfig_thread+0xed) [0x5592cf1a12bd]
  1396:20240129:130416.353 6: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_thread_start+0x20) [0x5592cf354e40]
  1396:20240129:130416.353 5: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0x8e4f8) [0x5592cf19f4f8]
  1396:20240129:130416.353 4: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](MAIN_ZABBIX_ENTRY+0xe37) [0x5592cf1a09c7]
  1396:20240129:130416.353 3: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](main+0x242) [0x5592cf195772]
  1396:20240129:130416.353 2: /lib/x86_64-linux-gnu/libc.so.6(+0x271ca) [0x7ff737acd1ca]
  1396:20240129:130416.353 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7ff737acd285]
  1396:20240129:130416.354 0: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](_start+0x21) [0x5592cf19c741]
  1396:20240129:130416.354 file:dbconfig.c,line:110 __zbx_shmem_realloc(): out of memory (requested 824008 bytes)
  1396:20240129:130416.354 file:dbconfig.c,line:110 __zbx_shmem_realloc(): please increase CacheSize configuration parameter
  1383:20240129:130417.014 One child process died (PID:1396,exitcode/signal:1). Exiting ...
  1393:20240129:130417.014 HA manager has been paused
  1393:20240129:130417.022 HA manager has been stopped
  1383:20240129:130417.024 Zabbix Server stopped. Zabbix 6.4.11 (revision fb6439a26e3).```

Expected:
Service running

 Comments   
Comment by Dario Andres Susman [ 2024 Jan 29 ]

I had to re-image the server from a snapshot (AWS) because I couldn't downgrade back to 6.4.10. The package seems to have been obsoleted.

Comment by Dario Andres Susman [ 2024 Jan 29 ]

Reconfiguring the CacheSize from default (16M) to 512M allowed zabbix-server to start.

Comment by Lucas Mauricio Soder [ 2024 Apr 24 ]

hey,

Even changing CACHESIZE as shown in the image below, I am unable to restart the service.

What is the limit I can add?

 

Comment by Lucas Mauricio Soder [ 2024 Apr 24 ]

A alteração de tamanho do cache foi feita após a leitura dos logs.
Na imagem abaixo, ele mostra que o temq deve ser alterado na linha 187 do arquivo "dbconfig".

Você pode me ajudar?
Está correto?

Comment by Dario Andres Susman [ 2024 Apr 24 ]

How much RAM has the server got? And are you using a beta version on a production environment?

Comment by Lucas Mauricio Soder [ 2024 Apr 24 ]

No, I'm approving.

but I was using version 6.4.14 and had the same problem

 

 

I am replacing the current server which is at version 5.0.13.

I have approximately 500 hosts in the environment.

Can you point me to a version?

Comment by Dario Andres Susman [ 2024 Apr 24 ]

I'm currently running 6.4.14 on my environment on Debian Bookworm.

Comment by Lucas Mauricio Soder [ 2024 Apr 24 ]

hey,

upload the new server
debian 12
zabbix 6.4.14

in cachesize I configured 512M

when it reached 190 hosts, the zabbix server stopped

Comment by Dario Andres Susman [ 2024 Apr 24 ]

Has the zabbix server stopped due to the same error?

I don't have that many servers, nor am I a Zabbix expert or developer...

Here are some ideas that I hope may help you, though:

Have you taken a look at htop or top to see how much resources are being used while zabbix-server is starting up?

Is 8Gb of RAM enough for your setup of 500 hosts? Was it working with Zabbix 6.0? Have you tried using 6.0 LTS?

Comment by Lucas Mauricio Soder [ 2024 Apr 24 ]

thank you for the help!

 

Did the zabbix server stop due to the same error?

yes, the same message appears in the LOG

 

Have you taken a look at htop or top to see how many resources are being used while zabbix-server is starting up?

yes, zabbix-server doesn't even appear in the top 10.

 

Is 8 Gb of RAM enough for your 500 host setup?

Checking the zabbix website they say that for 1000 hosts it uses the same configuration that I am using for 500.

 

Was it working with Zabbix 6.0?

today it works on version 5.0.13, with 128m CACHESIZE

 

 

Have you tried using 6.0 LTS?

I haven't performed this test, but it will be the next step.

Comment by Dario Andres Susman [ 2024 Apr 24 ]

I've just seen the top output and the specification of the instance.

they say they give you 8Gb but the system sees about 4Gb of RAM? something is wrong there.

Comment by Dario Andres Susman [ 2024 Apr 24 ]

to me, it was working on 6.0, yes - that's why I went to try 6.4.x

Comment by Lucas Mauricio Soder [ 2024 Apr 24 ]

Could you point out where this information is?

Comment by Lucas Mauricio Soder [ 2024 Apr 24 ]

But, I'm not upgrading the version, but installing a new one

Comment by Dario Andres Susman [ 2024 Apr 24 ]

Man, it says so there in the total amount of memory on `top`.

"MB mem: 3931,9 total"

Comment by Lucas Mauricio Soder [ 2024 Apr 24 ]

I have already increased the server size to 8vcpu and 16gb ram.

Even so, the serving didn't go up.

I will try to increase the cachesize initially to 2048mb or change to version 6.0LTS

Generated at Fri Apr 04 14:37:28 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.