By A A
Whenever I try to start the zabbix server it doesn’t start and when I check the status, following pops-up: Redirecting to /bin/systemctl status zabbix-server.service
● zabbix-server.service - Zabbix Server
Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: resources) since Thu 2018-02-08 15:20:46 EST; 7s ago
Process: 8846 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)
Process: 8929 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
Main PID: 8844 (code=exited, status=1/FAILURE)
CGroup: /system.slice/zabbix-server.service
Feb 08 15:20:46 system[1]: zabbix-server.service never wrote its PID file. Failing.
Feb 08 15:20:46 system[1]: Failed to start Zabbix Server.
Feb 08 15:20:46 system[1]: Unit zabbix-server.service entered failed state.
Feb 08 15:20:46 system[1]: zabbix-server.service failed.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hello,
The error message you provided suggests that the Zabbix server is failing to start due to a PID file issue.
A PID file contains the process ID of the Zabbix server process and is used to stop and restart the process. The error message indicates that the Zabbix server failed to create a PID file, which is causing the service to fail to start.
To resolve this issue, you can try the following steps:
-
Make sure that the Zabbix server configuration file (usually located at
/etc/zabbix/zabbix_server.conf) is correctly configured. -
Check the file permissions for the PID directory (
/var/run/zabbix) and make sure that the Zabbix user has permission to create files in this directory. -
Try deleting the existing PID file for the Zabbix server (
/var/run/zabbix/zabbix_server.pid) and restarting the Zabbix server.
- sudo rm /var/run/zabbix/zabbix_server.pid
After deleting the file, start the Zabbix server again using the following command:
sudo systemctl start zabbix-server.service
- If the issue persists, try stopping the Zabbix server, deleting the PID file, and then starting the server again.
You can stop the Zabbix server using the following command:
sudo systemctl stop zabbix-server.service
After stopping the server, delete the PID file and start the server again using the commands mentioned in step 3.
If none of the above steps work, you may need to consult the Zabbix server logs for more information about the issue. The logs can usually be found in the /var/log/zabbix/ directory.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.