Ad Widget

Collapse

Zabbix server is not running:the information displayed may not be current

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • sph919
    Member
    • Jan 2019
    • 38

    #1

    Zabbix server is not running:the information displayed may not be current

    Hi all,

    Logging into my zabbix I'm getting 'Zabbix server is not running:the information displayed may not be current'

    Checking the status showes it running but the

    systemctl status zabbix-server
    lines 1--1...skipping...
    ● zabbix-server.service - Zabbix Server
    Loaded: loaded (/lib/systemd/system/zabbix-server.service; enabled; vendor preset: enabled)
    Active: active (running) since Fri 2019-01-25 13:23:33 UTC; 171ms ago
    Process: 9479 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
    Main PID: 9490 (zabbix_server)
    Tasks: 1 (limit: 9472)
    CGroup: /system.slice/zabbix-server.service
    └─9490 /usr/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf

    Jan 25 13:23:33 zabbix systemd[1]: Starting Zabbix Server...
    Jan 25 13:23:33 zabbix systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
    Jan 25 13:23:33 zabbix systemd[1]: Started Zabbix Server.
    Jan 25 13:23:33 zabbix systemd[1]: zabbix-server.service: Main process exited, code=exited, status=1/FAILURE
    Jan 25 13:23:33 zabbix systemd[1]: zabbix-server.service: Failed with result 'exit-code'.

    Checking /var/log/zabbix/zabbix_server.log its showing

    x
    10249:20190125:132735.106 === Backtrace: ===
    10249:20190125:132735.106 9: /usr/sbin/zabbix_server(zbx_backtrace+0x44) [0x55c220deace4]
    10249:20190125:132735.106 8: /usr/sbin/zabbix_server(__zbx_mem_realloc+0x14d) [0x55c220de6dee]
    10249:20190125:132735.106 7: /usr/sbin/zabbix_server(+0xc5248) [0x55c220db1248]
    10249:20190125:132735.106 6: /usr/sbin/zabbix_server(+0xd0883) [0x55c220dbc883]
    10249:20190125:132735.106 5: /usr/sbin/zabbix_server(DCsync_configuration+0x1136) [0x55c220dbdc2d]
    10249:20190125:132735.106 4: /usr/sbin/zabbix_server(MAIN_ZABBIX_ENTRY+0x6b7) [0x55c220d24179]
    10249:20190125:132735.106 3: /usr/sbin/zabbix_server(daemon_start+0x315) [0x55c220dea42d]
    10249:20190125:132735.106 2: /usr/sbin/zabbix_server(main+0x305) [0x55c220d23aac]
    10249:20190125:132735.106 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fa23d170b97]
    10249:20190125:132735.106 0: /usr/sbin/zabbix_server(_start+0x2a) [0x55c220d22c7a]
    10282:20190125:132745.316 Starting Zabbix Server. Zabbix 4.0.1 (revision 86073).
    10282:20190125:132745.316 ****** Enabled features ******
    10282:20190125:132745.316 SNMP monitoring: YES
    10282:20190125:132745.316 IPMI monitoring: YES
    10282:20190125:132745.316 Web monitoring: YES
    10282:20190125:132745.316 VMware monitoring: YES
    10282:20190125:132745.316 SMTP authentication: YES
    10282:20190125:132745.316 Jabber notifications: YES
    10282:20190125:132745.316 Ez Texting notifications: YES
    10282:20190125:132745.316 ODBC: YES
    10282:20190125:132745.316 SSH2 support: YES
    10282:20190125:132745.316 IPv6 support: YES
    10282:20190125:132745.316 TLS support: YES
    10282:20190125:132745.316 ******************************
    10282:20190125:132745.316 using configuration file: /etc/zabbix/zabbix_server.conf
    10282:20190125:132745.319 current database version (mandatory/optional): 04000000/04000000
    10282:20190125:132745.319 required mandatory version: 04000000
    10282:20190125:132745.561 __mem_malloc: skipped 0 asked 24 skip_min 18446744073709551615 skip_max 0
    10282:20190125:132745.561 [file:dbconfig.c,line:94] zbx_mem_realloc(): out of memory (requested 16 bytes)
    10282:20190125:132745.561 [file:dbconfig.c,line:94] zbx_mem_realloc(): please increase CacheSize configuration parameter
    10282:20190125:132745.561 === memory statistics for configuration cache ===
    10282:20190125:132745.561 min chunk size: 18446744073709551615 bytes
    10282:20190125:132745.561 max chunk size: 0 bytes
    10282:20190125:132745.561 memory of total size 8388232 bytes fragmented into 75484 chunks
    10282:20190125:132745.561 of those, 0 bytes are in 0 free chunks
    10282:20190125:132745.561 of those, 7180504 bytes are in 75484 used chunks
    10282:20190125:132745.561 ================================


    Just to rule it out I've check the zabbix.conf.php conf settings and there appear to be correct:


    // Zabbix GUI configuration file.
    global $DB;

    $DB['TYPE'] = 'MYSQL';
    $DB['SERVER'] = 'localhost';
    $DB['PORT'] = '0';
    $DB['DATABASE'] = 'zabbix';
    $DB['USER'] = 'zabbix';
    $DB['PASSWORD'] = 'MYPASSWORD*';

    // Schema name. Used for IBM DB2 and PostgreSQL.
    $DB['SCHEMA'] = '';

    $ZBX_SERVER = 'MYSERVERSIP';
    $ZBX_SERVER_PORT = '10051';
    $ZBX_SERVER_NAME = 'zabbix';

    $IMAGE_FORMAT_DEFAULT = IMAGE_FORMAT_PNG;



    This only thing that has changed on the server is I have added around 100 new devices to monitor and then the error started appearing. I did notices that the ram was maxing out, so gave the vm more 8.
    Not sure what the problem is?

  • sph919
    Member
    • Jan 2019
    • 38

    #2
    Got it - Found this thread https://www.zabbix.com/forum/zabbix-...not-be-current

    To any one new to zabbix. The key bit of information is in the error log

    Code:
    10282:20190125:132745.316 using configuration file: /etc/zabbix/zabbix_server.conf 
    10282:20190125:132745.319 current database version (mandatory/optional): 04000000/04000000 
    10282:20190125:132745.319 required mandatory version: 04000000 
    10282:20190125:132745.561 __mem_malloc: skipped 0 asked 24 skip_min 18446744073709551615 skip_max 0 
    10282:20190125:132745.561 [file:dbconfig.c,line:94] zbx_mem_realloc(): out of memory (requested 16 bytes) 
    10282:20190125:132745.561 [file:dbconfig.c,line:94] zbx_mem_realloc(): [B]please increase CacheSize configuration parameter[/B]
    But from reading the other thread, its not just the CacheSize. You will need to increase these as well:

    HistoryCacheSize
    TrendCacheSize
    HistoryTextCacheSize
    ValueCacheSize

    The config is good and does explain what these are each used for.

    So just edit vi /etc/zabbix/zabbix_server.conf and make you increases.

    My set up at the moment is

    Number of hosts: 111
    Number of items: 10598
    Number of triggers: 5734

    But I'm in the middle of adding more host, this is doing to grow to around 360 host so the below config will increase.

    CacheSize=3g
    HistoryCacheSize=1524M
    TrendCacheSize=1524M
    HistoryIndexCacheSize=500M
    ValueCacheSize= 5120M

    Comment


    • shiju22
      shiju22 commented
      Editing a comment
      this was a grate help been days was looking
      specialy this part
      But from reading the other thread, its not just the CacheSize. You will need to increase these as well:

      HistoryCacheSize
      TrendCacheSize
      HistoryTextCacheSize
      ValueCacheSize
  • kaos
    Junior Member
    • Feb 2021
    • 6

    #3
    Sph919,

    Followed your guidance. Server is now working properly. Thank you.

    I'll keep an eye on it in the future if it ever stop working again and I'll increase the CacheSize where necessary.
    Too bad there's no guidance on what they should be based on the numbers of device and items monitored.

    This might be asking a lot since this is dependent on number of devices and items monitored, not to mention the type being monitored.

    Comment

    • charliesks
      Junior Member
      • Jan 2021
      • 2

      #4
      Hey Sph919,

      Thanks for the information if helped solve the issue wherein my case the server stopped when I added the PFSense template.

      The PFSense template added around 16000 items to the host which caused the server to be unresponsive.

      So in case you are reading this and having a similar issue, double-check the templates before adding them more specifically the number of items that are being monitored.

      Comment

      Working...