|
From: | Martin Pala |
Subject: | Re: Monit did not restart mysql |
Date: | Sun, 2 Jun 2013 10:43:46 +0200 |
Hi, please check monit logs and "monit status" for mysqld. You can run monit in debug mode using "-v" option to see more details. From the description i'm not sure exactly what happened - it seems that mysql was running and you tried to kill/stop it to see whether monit will recover it? As you have two tests, the mysql error should be detected when the process stops (i.e. the PID in the /var/run/mysqld/mysqld.pid file is not present in the process table) and/or if the connection fails. As Sven correctly pointed out the 127.0.1.1 is wrong, so the connection test probably always failed. Because you have restart action on connection failure, monit will try to restart it - and since there is also the timeout statement, it'll give up after 5 attempts and will disable the service monitoring. My guess is, that the misconfigured connection test (127.0.1.1 instead of 127.0.0.1) caused monit to restart mysql five times (as the test failed after the restart too), which led to service unmonitoring => monit most probably doesn't watch mysql anymore and if you killed it, it won't restart it. The solution if this state is to fix the configuration (127.0.1.1 -> 127.0.0.1) and enable mysql monitoring again: "monit monitor mysqld" Regards, Martin On Jun 2, 2013, at 10:19 AM, frwa onto <address@hidden> wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |