Ad Widget

**dimir** · 22-11-2017, 11:56

You mention in Zabbix Agent Conf:

Code:

Server=10.170.12.240 (This was 127.0.0.1 before,but this way the agent did not work. So I changed it with the ip)

So perhaps try setting the same IP for frontend, /etc/zabbix/web/zabbix.conf.php:

Code:

$ZBX_SERVER      = '10.170.12.240';

**DiViNe** · 23-11-2017, 11:33

Dear dimir

Thanks a lot for you replay!

I had "localhost" in both configs and changed it recently to 10.170.12.240' (but not in both configs -thanks for the info). I changed it now in both, but it still doesn’t work.

Regards

DiViNe

**dimir** · 23-11-2017, 11:37

What do you get if you perform from the command-line:

Code:

telnet 10.170.12.240 10051

or this one:

Code:

telnet 127.0.0.1 10051

also this one please:

Code:

/sbin/ifconfig

**DiViNe** · 28-11-2017, 13:20

here we go:

Code:

[root@chdcvzabbix01 ~]#telnet 10.170.12.240 10051
Trying 10.170.12.240...
Connected to 10.170.12.240.
Escape character is '^]'.


[root@chdcvzabbix01 ~]#telnet 127.0.0.1 10051
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.


[root@chdcvzabbix01 ~]#/sbin/ifconfig
ens160: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.170.12.240  netmask 255.255.255.0  broadcast 10.170.12.255
        inet6 fe80::250:56ff:fe87:a8fd  prefixlen 64  scopeid 0x20<link>
        ether 00:50:56:87:a8:fd  txqueuelen 1000  (Ethernet)
        RX packets 90611516  bytes 7293763950 (6.7 GiB)
        RX errors 0  dropped 2044  overruns 0  frame 0
        TX packets 96339415  bytes 10642285259 (9.9 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 4171639  bytes 248051024 (236.5 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4171639  bytes 248051024 (236.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I tried it also with NC:

Code:

[root@chdcvzabbix01 ~]#nc -v 10.170.12.240 10051
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connected to 10.170.12.240:10051.

[root@chdcvzabbix01 ~]#nc -v 10.170.12.240 10051
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connected to 10.170.12.240:10051.

**dimir** · 28-11-2017, 13:58

Do you have SELinux/grsecurity enabled? Could they be causing an issue?

**DiViNe** · 28-11-2017, 14:06

No:

Code:

grep ^[^#] /etc/sysconfig/selinux
SELINUX=disabled
SELINUXTYPE=targeted

I've also disabled testwise the firewall....

**dimir** · 28-11-2017, 14:39

Maybe your Zabbix server trapper process is so busy all the time it cannot handle requests from frontend. In that case you could try increasing the number of trapper processes (you have StartTrappers=3).

Also make sure the frontend you are using uses the configuration file you specified. As it looks like frontend is has Zabbix server/port misconfigured.

**DiViNe** · 29-11-2017, 13:35

Changed Trapper and looking for frontend-config

Thank you for your input!

Originally posted by dimir

Maybe your Zabbix server trapper process is so busy all the time it cannot handle requests from frontend. In that case you could try increasing the number of trapper processes (you have StartTrappers=3).

I increased it up to 500 (and restarted the server) but it didn't work.

Also make sure the frontend you are using uses the configuration file you specified. As it looks like frontend is has Zabbix server/port misconfigured.

Do you mean this file?
/etc/zabbix/web/zabbix.conf.php
And what should I change?

Thanks you

**DiViNe** · 06-12-2017, 12:16

I've changed it testwise to 10050 but it didn't work, so I switchted it back to 10051

Code:

[root@chdcvzabbix01 ~]#vi /etc/zabbix/web/zabbix.conf.php
<?php
// Zabbix GUI configuration file.
global $DB;

$DB['TYPE']     = 'MYSQL';
$DB['SERVER']   = 'localhost';
$DB['PORT']     = '0';
$DB['DATABASE'] = 'zabbixdb';
$DB['USER']     = 'zabbixuser';
$DB['PASSWORD'] = 'MyCensoredPassword';

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

$ZBX_SERVER      = '10.170.12.240';
[COLOR="red"]$ZBX_SERVER_PORT = '10050';[/COLOR]
$ZBX_SERVER_NAME = 'Zabbix Monitoring';

$IMAGE_FORMAT_DEFAULT = IMAGE_FORMAT_PNG;

**dimir** · 06-12-2017, 15:53

According to the netstat zabbix server is listening on port 10051. You can connect to it with nc. If frontend is giving "Zabbix server is not running" it means it cannot connect to the port, the only reason I see that might be here is that frontend is using different config file. Try to change the DB settings in this file and see if you get a DB error in frontend.

**DiViNe** · 27-12-2017, 13:40

Which file?

I've started over and set up a new server (new OS and new zabbix installation). I haven't got this message and the frontend said "zabbix server is running" = Yes. Everything is fine, right? Yeah, but not for long:
After aprox 15 mins I'll get again the "Zabbix server is not running: the information displayed may not be current" message. Now ther's also an "zabbix server is running" = No. And from this moment on, it stays like that :-/

Strange was, that the frontend get's new messages. For ex. when I restart the server, then the "Zabbix server has just been restarted" message appears in the frontend.
Now, 1h later, are just the old dashboard messages like "Zabbix agent on Zabbix server is unreachable for 5 minutes" visible. No new "Zabbix server has been restarted" messages appear any more

Originally posted by dimir

According to the netstat zabbix server is listening on port 10051. You can connect to it with nc.

Yup, that looks good:

Code:

netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      1/systemd
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1132/sshd
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      1651/master
tcp        0      0 0.0.0.0:10050           0.0.0.0:*               LISTEN      1148/zabbix_agentd
tcp      129      0 0.0.0.0:10051           0.0.0.0:*               LISTEN      1250/zabbix_server
tcp        0      0 0.0.0.0:3306            0.0.0.0:*               LISTEN      1591/mysqld
tcp6       0      0 :::111                  :::*                    LISTEN      1/systemd
tcp6       0      0 :::80                   :::*                    LISTEN      1141/httpd
tcp6       0      0 :::22                   :::*                    LISTEN      1132/sshd
tcp6       0      0 ::1:25                  :::*                    LISTEN      1651/master
tcp6       0      0 :::10050                :::*                    LISTEN      1148/zabbix_agentd
tcp6       0      0 :::10051                :::*                    LISTEN      1250/zabbix_server

Originally posted by dimir

If frontend is giving "Zabbix server is not running" it means it cannot connect to the port, the only reason I see that might be here is that frontend is using different config file. Try to change the DB settings in this file and see if you get a DB error in frontend.

Code:

/etc/zabbix/zabbix_server.conf
DBHost=localhost

to

Code:

DBHost=10.170.12.240

= no sucess

Code:

/etc/zabbix/web/zabbix.conf.php
$DB['SERVER']   = 'localhost';

to

Code:

$DB['SERVER']   = '10.170.12.240';

Frontend wasn't available anymore

Could you please point out which file I could/should change?
Any other ideas other ideas?

**GDBJNC** · 03-01-2018, 21:58

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

I ran into a similar issue on my newly installed Zabbix server. 3.4 (Ubuntu 16.04).

I found that when I added a Cisco switch using a template it added hundreds of items to the host. When I removed the host, I was able to start the service.

What the actual fix was that my /usr/share/zabbix/conf/zabbix_server.conf file needed to be tuned. I did not have enough memory allocated to my server.

I modified the file /etc/zabbix/zabbix_server.conf and modified the CacheSize to the maximum memory my server would support (8G in my case).

I also modified the HistoryIndexCacheSize and TrendCacheSize.

Please note that when modifying the Cache sizes, all must be below or equal the CacheSize. Found that the hard way.

Hope this helps.

**andreaf-it** · 20-04-2020, 22:44

the same problem with ubuntu or centos proxy based on vmware

Ad Widget

Zabbix server is not running: the iformation may not be current

Zabbix server is not running: the iformation may not be current

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment