Ошибка zabbix сервер не запущен

EddyEddy

3,48313 gold badges58 silver badges87 bronze badges

just get into the zabbix.conf.php

   >$sudo vim /etc/zabbix/web/zabbix.conf.php
   >$ZBX_SERVER      = '**your zabbix ip address or DNS name**';
   >$ZBX_SERVER_PORT = '10051';
   >$ZBX_SERVER_NAME = '**your zabbix hostname**';

just change the ip address you can resolve the error

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

After that restart the zabbix server

 >$sudo service zabbix-server restart

To verify go to Dashboard Administration -> queue there you see data

i resolved my error like this works fine for me.

Edit this file: sudo nano /etc/default/zabbix-server

Adjust the START property to yes:

START=yes

Then try to run Zabbix again: sudo service zabbix-server start

answered Dec 10, 2015 at 17:40

This may happen because of the old and new IP address
I have faced same issue which was solve by below method:

vim /etc/zabbix/web/zabbix.conf.php

$ZBX_SERVER = new ip address

then restart zabbix server

I was using a special character in my DB password — wrapping the DBPassword option in /etc/zabbix/zabbix_server.conf and doing sudo service zabbix-server restart got me back up and running.

Not Working
DBPassword=MyString?

Working
DBPassword='MyString?'

answered Sep 7, 2017 at 14:03

Solution might be this simple:

    sudo su 
    
    nano /etc/zabbix/zabbix-server.conf

Remove «#» in front of DBPassword=YourPassword (will change from blue to grey)

Ctrl x (Y to save and press enter to exit)

    service zabbix-server restart

Now you can refresh your browser running ZABBIX. If not, you will have to do the same steps for CacheSize=32M

You do not have to change anything in /etc/zabbix/web/zabbix.conf.php (localhost is fine)

When editing anything, remember «#» in front of line means invisible to linux.

As Zabbix Senior Instructor and Consultant Hernandes Martins says in his «Zabbix server is not running what to do?» blog post:

This is the first step that should be checked regardless of the situation, always view the logs, from the moment the error message appeared in the zabbix web interface always view the log.

By following his advice I could be able to identify the cause of the issue with my Zabbix server, and then apply the solution related to the specific problem.

In my case, as I’ve commented in the page:

The problem in my server was of «4. Resource Allocation Issues». Just like you wrote above, Zabbix was showing out of memory errors on the log when trying to start the server.

After increasing the value of parameter CacheSize I tried to restart the service, but it didn’t respond. So, I ended up restarting the whole machine. Fortunately, in the end it resolved the problem for good.

So, take a look at the log with command tail -f /var/log/zabbix/zabbix_server.log on the terminal/prompt, watch for any errors, and tackle the problem according to what it makes sense for your particular case.

answered Oct 29, 2019 at 13:17

Looks like the problem was that I created a Database monitoring Item programmatically and it triggered a bug that caused the server to shutdown.

Once I deleted the item the server came back up, and creating subsequent Items didn’t kill it.

The deadly Item had a value_type of Numeric unsigned, -1 programmatically, while the newly created Items have a value_type of float, which is 0 programmatically.

The whole thing has a voodoo element to it but it did solve my problem.

answered Jul 20, 2015 at 4:35

Maybe is configuration issue

nano /etc/zabbix/zabbix_server.conf

DBHost=localhost

DBName=zabbix_db

DBUser=zabbix_user

DBPassword=XXXXXXX

works for me on Zabbix 3.0 Centos 7

answered Aug 25, 2016 at 18:16

The zabbix-server daemon doesn’t seem to like passwords with special characters in them. Unsure whether quotes would work in the configuration I just removed special characters from the database password, updated the configuration files and restarted the daemon.

Configuration parsing errors don’t show up in logs for some reason.

answered Sep 27, 2016 at 23:00

Install nmap (( # yum/apt-get install nmap ))tool and check to find out which port the zabbix is listenning to?(( # nmap -sT -p1-65535 localhost )) 10050 or 10051?
The result should be somthing like this:

Starting Nmap 6.40 ( http://nmap.org ) at 2016-11-01 22:54 IRST
Nmap scan report for localhost (127.0.0.1)
Host is up (0.00032s latency).
Other addresses for localhost (not scanned): 127.0.0.1
Not shown: 65530 closed ports
PORT      STATE SERVICE
22/tcp    open  ssh
25/tcp    open  smtp
80/tcp    open  http
3306/tcp  open  mysql
10050/tcp open  unknown    <--- In my case this is it

Then open /etc/zabbix/web/zabbix.conf.php and check the line starting with: $ZBX_SERVER_PORT , it’s value should be the same number you saw in the nmap scan result. Change it and restart zabbix-server and httpd and you are good to go!

answered Nov 1, 2016 at 19:00

answered Dec 15, 2016 at 18:36

On RHEL/CentOS/OEL 6

• Check that the firewall is allowing connection to Zabbix Server port which is 10051, as a user with root priv:

  vi /etc/sysconfig/iptables

and add the following lines

-A INPUT -m state --state NEW -m tcp -p tcp --dport 10051 -j ACCEPT

restart iptables

# service iptables restart

If you have disabled IPV6, you need to also edit the hosts file and remove IPV6 line for «localhost»

# vi /etc/hosts

remove or comment out «#» the ipv6 line for localhost

::1                   localhost6.localdomain6   localhost6

restart the zabbix-server and check if the error message is gone.

answered Nov 27, 2017 at 10:24

I was in the same trouble.
For my case, that was a conflict between /etc/zabbix/zabbix_agentd.conf and zabbix_server.conf parameters.
I adjusted

"DBHost=localhost", 
"DBName=zabbix",
"DBUser=zabbix",
"DBPassword=******", 
"DebugLevel=3"
"ListenPort".

If you run the default installation, you should keep ListenPort=10051 for the server and 10050 for the agent.

Cheers!

In my case it happens when introducing host with templates, graphs,trigger etc, the server falls.
The problem was that by default the cache is at 128k and you have to change it.

sudo nano /etc/zabbix/zabbix-server.conf

Uncheck # Sizecache and add 32M for example.

Cachesize=32M

restart service and voila!! server working

service zabbix-server start

answered Mar 10, 2018 at 12:09

My problem was caused by having external ip in $ZBX_SERVER setting.

I changed it to localhost instead so that ip was resolved internally,

$sudo nano /etc/zabbix/web/zabbix.conf.php

Changed

$ZBX_SERVER = ‘external ip was written here’;

to

$ZBX_SERVER = ‘localhost’;

then

$sudo service zabbix-server restart

Zabbix 3.4 on Ubuntu 14.04.3 LTS

answered Apr 26, 2018 at 13:08

I had the same issue.

I forgotten selinux conf, not all is ok:

setsebool -P httpd_can_connect_zabbix on

answered Jun 30, 2018 at 10:25

In my case, this occurred because the password in the server config file was commented out.

Open the server config file: # sudo vim /etc/zabbix/zabbix-server.conf

Scroll down to db user and below there will be the password with a # commenting out. Remove the hash and insert your DB password.

answered Aug 3, 2018 at 4:51

In my case i had to disable Linux SE

[root@webserverlocaldomain /]# setenforce 0

Disable Firewall

[root@webserverlocaldomain /]# systemctl stop firewalld

Edit config file uncommenting#

[root@webserverlocaldomain /]# vi /etc/zabbix/zabbix_server.conf

 ListenPort=10051
 DBHost=localhost
 DBPassword=password

Then restart the services

[root@webserverlocaldomain /]# systemctl restart zabbix-server zabbix-agent httpd

answered Nov 21, 2018 at 22:50

in my case after installing zabbix from sources (removed zabbix 4.0 because upgrading to 4.2 wasn’t possible via apt on a Raspbian GNU/Linux 9.4 stretch) it loaded the config from /usr/local/etc/zabbix_server.conf instead from /etc/zabbix/zabbix_server.conf

After deleting /usr/local/etc/zabbix_server.conf and creating a symlink pointing to the correct config file in /etc/zabbix/zabbix_server.conf it started to work

answered Jul 3, 2019 at 15:43

I solved this problem on Ubuntu 18.04 by uninstalling Zabbix and reinstalling it again from scratch.

The initial installation didn’t work because I had followed old posts/guides/tutorials, even from Zabbix documentation itself, so these might probably be outdated. So, the trick was to find and follow the most updated guide to Zabbix installation from its docs.

Here are the two links I followed for uninstalling and reinstalling Zabbix:

• How to uninstall Zabbix: https://www.quora.com/How-do-I-uninstall-Zabbix-server-agent-in-Ubuntu
• How to (properly) install Zabbix: https://www.zabbix.com/download?zabbix=4.0&os_distribution=ubuntu&os_version=18.04_bionic&db=postgresql

When installing Zabbix from the link above, your choosen Zabbix Version, OS Distribution, OS Version or Database may be different from the ones I’ve selected, but following the instructions on this page will probably be also the right way for you to install your chosen Zabbix configuration without getting errors post installation.

answered Jul 18, 2019 at 11:22

Never had the problem until it suddenly appeared once, for me, the solution was to add (uncomment) the following line in /etc/zabbix/zabbix_server.conf

 ListenIP=0.0.0.0

answered Jan 17, 2019 at 9:35