So all of a sudden, after a week of using it, I get an error message on my zabbix server
gui (http://localhost/zabbix/.)
The error says: Zabbix serve
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 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
There maybe IP address conflict, try host 'Zabbix server'
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.
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.
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