RE: mysql (was: "")

[Benjamin Krajmalnik]

Aswin, you have a major conceptual misunderstanding.

You  re checking a port on a remote server, but restarting a local process which may or may not exist.

 

 

From: address@hidden [mailto:address@hidden On Behalf Of Martin Pala
Sent: Tuesday, June 04, 2013 2:24 AM
To: This is the general mailing list for monit
Subject: Re: mysql (was: "")

 

Hi,

 

the configuration probably detects some error each cycle, which leads to a service restart (per your settings) - since you have also the timeout statement, the service is unmonitored after 5 restarts. You need to fix the configuration (see the monit log for details) and then enable the mysql monitoring again: "monit monitor mysql"

 

Regards,

Martin

 

P.S. please set the message subject if you post to monit mailing list

 

 

 

On Jun 4, 2013, at 8:19 AM, Aswin Roy <address@hidden> wrote:

I am trying to monitor the MySQL process in another system using Monit. The system is connected to the same network connection as mine. I am using this code (inside the configuration file, monitrc) :

check process mysql with pidfile /var/run/mysqld/mysqld.pid

group database

start program = "/etc/init.d/mysql restart"

stop program = "/etc/init.d/mysql stop"

if failed host 192.168.0.189 port 3306 then restart

if 5 restarts within 5 cycles then timeout

Status appears to be "Not monitored". What seems to be the problem?

 

 

--

Aswin Jose Roy

Computer Science and Engineering (2010-2014)

Govt. Model Engineering College

Cochin-21

+91 9746237979

address@hidden

--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general

Email is virus free, scanned by Emsisoft Anti-Malware - www.emsisoft.com
Last signature update: 06/04/2013 - 10,174,514 known threats in database