Hi, what alert exactly you get from monit?
The start timeout sets the time, that will monit wait for process to start, i.e. when the process with PID matching to the "pidfile" content will show up in the process table. As soon as the process is started, monit resumes all tests (e.g. connection test, etc.). Some processes are slow to provide the network service - even though they are started, it takes time to them to start accepting connections and processing requests. Such services need the "settle" period before the connection test can be resumed - this is not provided by the start timeout. Regards, Martin On May 22, 2012, at 1:44 PM, Amit Naudiyal wrote: > Dear All, > > Please advise if there is any configuration by which I can skip alerts for > few starting cycles. > Like we have few services which we manage through Monit but those application > take time to start and on next cycle, monit starts sending mail for them. > We want, monit can skip alerts particularly for those services for defined > cycles before actually sending alerts for them. > > The option "start program = /etc/init.d/<program> start" with timeout 360 > seconds does not seems to be working. Program actually takes few seconds to > start with a pid file. Monit does not find pid and start sending mail even > when program is under start process. > > > Regards, > Amit > > > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general
-- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
