Zabbix – service restart

zabbixzabbix-agent

I have zabbix monitoring multiple servers (Linux and Windows). Is it possible to have zabbix automate services that they are down to automatically restart?

Best Answer

It is possible. First thing you will have to do is enable remote actions on zabbix agents, by setting the following in zabbix_agentd.conf:

EnableRemoteCommands=1

You will also need to grant sudo privileges to your zabbix user, so create a file /etc/sudoers.d/zabbix_nopasswd with the following content:

zabbix ALL=NOPASSWD: ALL

For better security concerns, you'd better only allow zabbix to run specific shell commands, e,g:

# allows 'zabbix' user to restart apache without password.
zabbix ALL=NOPASSWD: /etc/init.d/apache restart

After that, restart zabbix agent(s).

Now, on the Zabbix server, log in as an user that has admin privileges to Zabbix web gui, and create new action: Configuration -> Actions -> New Action. Name the new action someething like 'Restart Apache'.

Set Action Type to "Remote Command". Set Remote Command to:

{HOSTNAME}:/usr/bin/sudo service apache2 restart

After that, create a Trigger on an item that counts number of apache processes running, in a way that if the number is 0 that the action "Restart Apache" is run, and that's it.

Related Solutions

Stop Zabbix notification for nodes under zabbix-proxy when proxy service is down

One way to accomplish that would be to monitor whether Zabbix proxy is reachable. This is done using zabbix[proxy,<name>,lastaccess] internal item. In the documentation on internal items, it then suggests to use fuzzytime() trigger function to check availability of your proxy:

{<zabbix>:zabbix[proxy,<name>,lastaccess].fuzzytime(2m)}=0

After that you can make your "host unreachable" triggers depend on this trigger, which will stop them from being activated when proxy is unreachable (see documentation on trigger dependencies for more information).

Mysql – Zabbix: MySQL service monitor – invalid entry when restarting zabbix-agent

The problem with your configurations are:

You are putting the .my.cnf file at the wrong place.

Zabix agent configuration file has prescribed format and parameters defined. If you may use Include option to load additional config files, be sure it follows the same format. The zabbix documentation states it clearly:

Starting from version 1.8.6 Zabbix agent daemon will not start up if invalid (not following parameter=value notation) or unknown parameter entry is present in configuration file.

So, in your case the .my.cnf file fails to load when you put it under /etc/zabbix/zabbix_agentd.d.

You are missing the part to configure userparameter_mysql.conf file properly.

To resolve the issues:

Move the .my.cnf file from /etc/zabbix/zabbix_agentd.d directory to /etc/zabbix. And also remove any Include entry to refere to the .my.cnf file (if there is any). The content of the file may look like this:

[mysqld]
user=username
password=userpass

[mysqladmin]
user=username
password=userpass

Please make sure that the user listed here exists and have the necessary permissions in mysql.

Edit /etc/zabbix/zabbix_agentd.d/userparameter_mysql.conf file: You need to replace HOME=/var/lib/zabbix with HOME=/etc/zabbix to point to the right file (should appear three times) as mentioned in the first line of the file.
Finally restart the agent: service zabbix-agent restart

Best Answer

Related Solutions

Stop Zabbix notification for nodes under zabbix-proxy when proxy service is down

Mysql – Zabbix: MySQL service monitor – invalid entry when restarting zabbix-agent

Related Topic