I’ve restarted the Monit service a few times and even rejiggered the ruleset to see if it helps but none of that seems to affect anything. On the General Settings tab, turn on Monit and fill in the details of your SMTP server. And the timeout condition seems to result in the MySQL service ruleset being ignored my Monit. ![]() ![]() In this section, we will install Apache and MariaDB and monitor both services using Monit. 63.6k 31 31 gold badges 131 131 silver badges 192 192 bronze badges. If any service goes down Monit, automatically start it. Install monit: sudo apt update sudo apt install -t buster-backports monit Share. To install monit, run To start monit, run Monitor Apache Add Activate the rule with. Monit works by continuously monitoring different services in your system. With the /etc/init.d/mysql start command not able to work, the system attempted 5 restarts, failed 5 times and then timed out as a result. Monit can be used to monitor services, restart them if required. Okay, my bad… But the issue is you see that if 5 restarts within 5 cycles then timeout part? That seems to have bit me hard. The issue is I was attempting to invoke start/stop items via /etc/init.d/ - which is more of a CentOS/RedHat system construct - instead of using /usr/sbin/service which would be more appropriate for a Ubuntu/Debian system. Install EPEL repository: Install Monit: Activate Monit to start automatically during the system boot and start it: To configure Monit, open the /etc/monitrc. Start program = "/etc/init.d/mysql start"Īlert only on ![]() While devising an answer to this question I ran into a snag while testing this MySQL Monit ruleset on an Ubuntu 12.04.5 setup: check process mysqld with pidfile /var/run/mysqld/mysqld.pid
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |