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

WiVM

Junior Member

Joined: Nov 2022
Posts: 7

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

22-11-2022, 14:12

Checked the previous topics on this forum related to this notification in Zabbix, but the suggested settings are already applied.

The server log at start-up:

Code:

 9086:20221122:103352.254 Starting Zabbix Server. Zabbix 4.2.6 (revision d3bb18bbc4).
  9086:20221122:103352.254 ****** Enabled features ******
  9086:20221122:103352.254 SNMP monitoring:           YES
  9086:20221122:103352.254 IPMI monitoring:           YES
  9086:20221122:103352.254 Web monitoring:            YES
  9086:20221122:103352.254 VMware monitoring:         YES
  9086:20221122:103352.254 SMTP authentication:       YES
  9086:20221122:103352.254 Jabber notifications:       NO
  9086:20221122:103352.254 Ez Texting notifications:  YES
  9086:20221122:103352.254 ODBC:                      YES
  9086:20221122:103352.254 SSH2 support:              YES
  9086:20221122:103352.254 IPv6 support:              YES
  9086:20221122:103352.254 TLS support:               YES
  9086:20221122:103352.254 ******************************
  9086:20221122:103352.254 using configuration file: /etc/zabbix/zabbix_server.conf
  9086:20221122:103352.258 current database version (mandatory/optional): 04020000/04020001
  9086:20221122:103352.259 required mandatory version: 04020000
  9086:20221122:103352.650 server #0 started [main process]
  9092:20221122:103352.650 server #1 started [configuration syncer #1]
  9093:20221122:103352.650 server #2 started [housekeeper #1]
  9094:20221122:103352.651 server #3 started [timer #1]
  9095:20221122:103352.651 server #4 started [http poller #1]
  9097:20221122:103352.651 server #5 started [discoverer #1]
  9112:20221122:103352.656 server #19 started [unreachable poller #1]
  9113:20221122:103352.657 server #20 started [trapper #1]
  9114:20221122:103352.659 server #21 started [trapper #2]
  9098:20221122:103352.660 server #6 started [history syncer #1]
  9099:20221122:103352.660 server #7 started [history syncer #2]
  9100:20221122:103352.661 server #8 started [history syncer #3]
  9101:20221122:103352.661 server #9 started [history syncer #4]
  9102:20221122:103352.661 server #10 started [escalator #1]
  9103:20221122:103352.663 server #11 started [proxy poller #1]
  9104:20221122:103352.665 server #12 started [self-monitoring #1]
  9105:20221122:103352.665 server #13 started [task manager #1]
  9106:20221122:103352.665 server #14 started [poller #1]
  9107:20221122:103352.668 server #15 started [poller #2]
  9109:20221122:103352.672 server #16 started [poller #3]
  9115:20221122:103352.674 server #22 started [trapper #3]
  9116:20221122:103352.676 server #23 started [trapper #4]
  9117:20221122:103352.677 server #24 started [trapper #5]
  9110:20221122:103352.677 server #17 started [poller #4]
  9118:20221122:103352.679 server #25 started [icmp pinger #1]
  9120:20221122:103352.679 server #27 started [alerter #1]
  9121:20221122:103352.680 server #28 started [alerter #2]
  9123:20221122:103352.680 server #30 started [preprocessing manager #1]
  9129:20221122:103352.680 server #35 started [lld worker #1]
  9130:20221122:103352.681 server #36 started [lld worker #2]
  9111:20221122:103352.682 server #18 started [poller #5]
  9122:20221122:103352.697 server #29 started [alerter #3]
  9119:20221122:103352.697 server #26 started [alert manager #1]
  9128:20221122:103352.699 server #34 started [lld manager #1]
  9127:20221122:103353.096 server #33 started [preprocessing worker #3]
  9125:20221122:103353.101 server #32 started [preprocessing worker #2]
  9124:20221122:103353.181 server #31 started [preprocessing worker #1]
  9093:20221122:110353.288 executing housekeeper

No CacheSize error. It is already set to 32M.

Service is started correctly:

Code:

 $ sudo systemctl status zabbix-server
● zabbix-server.service - Zabbix Server
   Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2022-11-22 10:33:52 CET; 2h 25min ago
  Process: 9079 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=0/SUCCESS)
  Process: 9084 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
 Main PID: 9086 (zabbix_server)
    Tasks: 37
   Memory: 42.6M
   CGroup: /system.slice/zabbix-server.service
           ├─9086 /usr/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
           ├─9092 /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.361516 sec, idle 60 sec]
           ├─9093 /usr/sbin/zabbix_server: housekeeper [deleted 42826 hist/trends, 0 items/triggers, 990 events, 0 sessions, 0 alarms, 0 audit items, 0 records in 11.578174 sec, idle for
           ├─9094 /usr/sbin/zabbix_server: timer #1 [updated 0 hosts, suppressed 0 events in 0.001378 sec, idle 59 sec]
           ├─9095 /usr/sbin/zabbix_server: http poller #1 [got 0 values in 0.000465 sec, idle 5 sec]
           ├─9097 /usr/sbin/zabbix_server: discoverer #1 [processed 0 rules in 0.000386 sec, idle 60 sec]
           ├─9098 /usr/sbin/zabbix_server: history syncer #1 [processed 0 values, 33 triggers in 0.000697 sec, idle 1 sec]
           ├─9099 /usr/sbin/zabbix_server: history syncer #2 [processed 0 values, 0 triggers in 0.000025 sec, idle 1 sec]
           ├─9100 /usr/sbin/zabbix_server: history syncer #3 [processed 9 values, 9 triggers in 0.009789 sec, idle 1 sec]
           ├─9101 /usr/sbin/zabbix_server: history syncer #4 [processed 0 values, 0 triggers in 0.000017 sec, idle 1 sec]
           ├─9102 /usr/sbin/zabbix_server: escalator #1 [processed 0 escalations in 0.000549 sec, idle 3 sec]
           ├─9103 /usr/sbin/zabbix_server: proxy poller #1 [exchanged data with 0 proxies in 0.000021 sec, idle 5 sec]
           ├─9104 /usr/sbin/zabbix_server: self-monitoring [processed data in 0.000018 sec, idle 1 sec]
           ├─9105 /usr/sbin/zabbix_server: task manager [processed 0 task(s) in 0.000413 sec, idle 5 sec]
           ├─9106 /usr/sbin/zabbix_server: poller #1 [got 0 values in 0.000007 sec, idle 1 sec]
           ├─9107 /usr/sbin/zabbix_server: poller #2 [got 2 values in 0.000099 sec, idle 1 sec]
           ├─9109 /usr/sbin/zabbix_server: poller #3 [got 0 values in 0.000016 sec, idle 1 sec]
           ├─9110 /usr/sbin/zabbix_server: poller #4 [got 0 values in 0.000016 sec, idle 1 sec]
           ├─9111 /usr/sbin/zabbix_server: poller #5 [got 0 values in 0.000007 sec, idle 1 sec]
           ├─9112 /usr/sbin/zabbix_server: unreachable poller #1 [got 0 values in 0.000020 sec, idle 5 sec]
           ├─9113 /usr/sbin/zabbix_server: trapper #1 [processed data in 0.000034 sec, waiting for connection]
           ├─9114 /usr/sbin/zabbix_server: trapper #2 [processed data in 0.000039 sec, waiting for connection]
           ├─9115 /usr/sbin/zabbix_server: trapper #3 [processed data in 0.000025 sec, waiting for connection]
           ├─9116 /usr/sbin/zabbix_server: trapper #4 [processed data in 0.000025 sec, waiting for connection]
           ├─9117 /usr/sbin/zabbix_server: trapper #5 [processed data in 0.000056 sec, waiting for connection]
           ├─9118 /usr/sbin/zabbix_server: icmp pinger #1 [got 0 values in 0.000019 sec, idle 5 sec]
           ├─9119 /usr/sbin/zabbix_server: alert manager #1 [sent 0, failed 0 alerts, idle 5.006850 sec during 5.006909 sec]
           ├─9120 /usr/sbin/zabbix_server: alerter #1 [sent 0, failed 0 alerts, idle 659.871890 sec during 660.748330 sec]
           ├─9121 /usr/sbin/zabbix_server: alerter #2 [sent 0, failed 0 alerts, idle 660.886616 sec during 661.684920 sec]
           ├─9122 /usr/sbin/zabbix_server: alerter #3 [sent 0, failed 0 alerts, idle 659.931764 sec during 660.714166 sec]
           ├─9123 /usr/sbin/zabbix_server: preprocessing manager #1 [queued 0, processed 53 values, idle 4.999561 sec during 5.000028 sec]
           ├─9124 /usr/sbin/zabbix_server: preprocessing worker #1 started
           ├─9125 /usr/sbin/zabbix_server: preprocessing worker #2 started
           ├─9127 /usr/sbin/zabbix_server: preprocessing worker #3 started
           ├─9128 /usr/sbin/zabbix_server: lld manager #1 [processed 0 LLD rules during 5.004959 sec]
           ├─9129 /usr/sbin/zabbix_server: lld worker #1 [processed 1 LLD rules, idle 3600.212872 sec during 3600.220818 sec]
           └─9130 /usr/sbin/zabbix_server: lld worker #2 [processed 1 LLD rules, idle 3600.208454 sec during 3600.220096 sec]

Nov 22 10:33:52 spappl00112.lnx.*****.** systemd[1]: Starting Zabbix Server...
Nov 22 10:33:52 spappl00112.lnx.*****.** systemd[1]: Started Zabbix Server.

SELinux is disabled:

Code:

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#     enforcing - SELinux security policy is enforced.
#     permissive - SELinux prints warnings instead of enforcing.
#     disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of three two values:
#     targeted - Targeted processes are protected,
#     minimum - Modification of targeted policy. Only selected processes are protected.
#     mls - Multi Level Security protection.
SELINUXTYPE=targeted

The MySQL user/dbname/password are aligned with the Zabbix configuration file /web/zabbix.conf.php and the server config: /zabbix_server.conf

The used Zabbix version is 4.2.6 on RedHat:

Static hostname: spappl00112.lnx.*****.**
Icon name: computer-vm
Chassis: vm
Machine ID: 26bbe5104a9b4a96b28ca4720cd58a40
Boot ID: aae28ed2b79e420d932b5fd6bf6dab56
Virtualization: vmware
Operating System: Red Hat Enterprise Linux
CPE OS Name: cpe:/o:redhat:enterprise_linux:7.9:GA:server
Kernel: Linux 3.10.0-1160.80.1.el7.x86_64
Architecture: x86-64

Server usage:

Tags: None

cyber

Senior Member

Joined: Dec 2006

Posts: 4807
#2

23-11-2022, 17:07

Frontend checks directly, is backend is running.. if it cannot do this, it will display that "server not running" warning... so from frontend directly to server:10051 should be possible to connect...
Comment
WiVM

Junior Member

Joined: Nov 2022

Posts: 7
#3

23-11-2022, 17:51

This is available and also remains available. The logs are not mentioning anything, so I assume this is some kind of a check to the database or what so ever? Is there a way to check this somewhere? Lower the sensitivity?
Comment

Previous template Next

Ad Widget

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

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

Comment

Comment