I'm coming along well using Zabbix but trying to figure out how to monitor and restart a failed Linux service is not going well.
I have probably read and followed 20 different articles and most seem to have slightly different variations with nothing working in the end so I thought it's time to post and ask here.
Can someone please walk me through the process of doing this. I'll keep this post handy until I know it inside out I promise
.
I have a cluster of web servers, all Centos 8 that serve web pages.
Server01 must run a custom service that does a tally to update some things in the DB.
If the service fails on server01, I'd like to have zabbix automatically restart it.
This is the first thing I very much need to get working and is mainly why I started looking at and using zabbix.
As a bonus and not so much a requirement
Is there a way that zabbix could be used in the following way as well.
If server01 goes away and zabbix cannot reach it, could it immediately start the same service on that second server.
It would have to keep track of which server is running the service so that it does not start another one on another server.
The server and the agents are 5.0.7.
I have probably read and followed 20 different articles and most seem to have slightly different variations with nothing working in the end so I thought it's time to post and ask here.
Can someone please walk me through the process of doing this. I'll keep this post handy until I know it inside out I promise
.I have a cluster of web servers, all Centos 8 that serve web pages.
Server01 must run a custom service that does a tally to update some things in the DB.
If the service fails on server01, I'd like to have zabbix automatically restart it.
This is the first thing I very much need to get working and is mainly why I started looking at and using zabbix.
As a bonus and not so much a requirement
Is there a way that zabbix could be used in the following way as well.
If server01 goes away and zabbix cannot reach it, could it immediately start the same service on that second server.
It would have to keep track of which server is running the service so that it does not start another one on another server.
The server and the agents are 5.0.7.
Comment