Ad Widget

Collapse

Zabbix Server not running.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • BattleOP
    Junior Member
    • Jun 2020
    • 2

    #1

    Zabbix Server not running.

    I logged into my Zabbix interface this morning and noticed an error that said "Zabbix server not running: the information displayed may not be current". No changes overnight to the server (I'm currently the only admin that knows about this server) but it was working last night before I was done for the day.

    I logged into the CLI and restarted Zabbix and I'm still getting the message.

    It's a recent install from about a week ago. So I'm running the most recent version and the most recent LTS version of Ubuntu. I'm running this on a VMWare ESXi server with local storage to the server.


    The log file has the following message on restart:



    16740:20200619:153536.213 Zabbix Server stopped. Zabbix 5.0.1 (revision c2a0b03480).
    16782:20200619:153546.470 Starting Zabbix Server. Zabbix 5.0.1 (revision c2a0b03480).
    16782:20200619:153546.470 ****** Enabled features ******
    16782:20200619:153546.470 SNMP monitoring: YES
    16782:20200619:153546.470 IPMI monitoring: YES
    16782:20200619:153546.470 Web monitoring: YES
    16782:20200619:153546.470 VMware monitoring: YES
    16782:20200619:153546.470 SMTP authentication: YES
    16782:20200619:153546.470 ODBC: YES
    16782:20200619:153546.472 SSH support: YES
    16782:20200619:153546.472 IPv6 support: YES
    16782:20200619:153546.472 TLS support: YES
    16782:20200619:153546.472 ******************************
    16782:20200619:153546.472 using configuration file: /etc/zabbix/zabbix_server.conf
    16782:20200619:153546.500 current database version (mandatory/optional): 05000000/05000000
    16782:20200619:153546.501 required mandatory version: 05000000
    16782:20200619:153546.555 server #0 started [main process]
    16791:20200619:153546.556 server #1 started [configuration syncer #1]
    16791:20200619:153546.945 __mem_malloc: skipped 0 asked 256 skip_min 18446744073709551615 skip_max 0
    16791:20200619:153546.945 [file:dbconfig.c,line:95] __zbx_mem_malloc(): out of memory (requested 256 bytes)
    16791:20200619:153546.945 [file:dbconfig.c,line:95] __zbx_mem_malloc(): please increase CacheSize configuration parameter
    16791:20200619:153546.945 === memory statistics for configuration cache ===
    16791:20200619:153546.945 free chunks of size 24 bytes: 112
    16791:20200619:153546.945 free chunks of size 32 bytes: 1
    16791:20200619:153546.945 free chunks of size 40 bytes: 4
    16791:20200619:153546.945 free chunks of size 56 bytes: 5
    16791:20200619:153546.945 free chunks of size 64 bytes: 1
    16791:20200619:153546.945 free chunks of size 72 bytes: 1
    16791:20200619:153546.945 free chunks of size 168 bytes: 1
    16791:20200619:153546.945 min chunk size: 24 bytes
    16791:20200619:153546.945 max chunk size: 168 bytes
    16791:20200619:153546.945 memory of total size 8388232 bytes fragmented into 73679 chunks
    16791:20200619:153546.946 of those, 3464 bytes are in 125 free chunks
    16791:20200619:153546.946 of those, 7205920 bytes are in 73554 used chunks
    16791:20200619:153546.946 ================================
    16791:20200619:153546.946 === Backtrace: ===
    16791:20200619:153546.946 13: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_backtrace+0x52) [0x55877b4b474c]
    16791:20200619:153546.946 12: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](__zbx_mem_malloc+0x184) [0x55877b4af0c5]
    16791:20200619:153546.946 11: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0x1a22b4) [0x55877b4732b4]
    16791:20200619:153546.946 10: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0x1f0c78) [0x55877b4c1c78]
    16791:20200619:153546.946 9: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_vector_ptr_append+0x20) [0x55877b4c1e43]
    16791:20200619:153546.946 8: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0x1ab5ea) [0x55877b47c5ea]
    16791:20200619:153546.946 7: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](DCsync_configuration+0x1029) [0x55877b480bde]
    16791:20200619:153546.947 6: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](dbconfig_thread+0x11a) [0x55877b328190]
    16791:20200619:153546.947 5: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_thread_start+0x3b) [0x55877b4c4531]
    16791:20200619:153546.947 4: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](MAIN_ZABBIX_ENTRY+0x9e8) [0x55877b3191dc]
    16791:20200619:153546.947 3: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](daemon_start+0x303) [0x55877b4b428e]
    16791:20200619:153546.947 2: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](main+0x309) [0x55877b3187de]
    16791:20200619:153546.947 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f7846ae60b3]
    16791:20200619:153546.947 0: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](_start+0x2e) [0x55877b3177ce]
    16782:20200619:153546.951 One child process died (PID:16791,exitcode/signal:1). Exiting ...
    16782:20200619:153546.962 syncing trend data...
    16782:20200619:153546.962 syncing trend data done
    16782:20200619:153546.962 Zabbix Server stopped. Zabbix 5.0.1 (revision c2a0b03480).



    Any ideas? Google and the forum search turns up nothing. What I have found the log shows Zabbix does not like.
  • BattleOP
    Junior Member
    • Jun 2020
    • 2

    #2
    Can anyone point me in the right direction?

    Comment

    • Atsushi
      Senior Member
      • Aug 2013
      • 2028

      #3
      A workaround is specified in the log message.
      16791:20200619:153546.945 [file:dbconfig.c,line:95] __zbx_mem_malloc(): please increase CacheSize configuration parameter
      Please try adjust the CacheSize setting.

      Similar questions:




      Comment

      Working...