Thanks, Martin. I will take a look.
On Wed, Nov 12, 2014 at 9:42 AM, Martin Pala <[email protected]> wrote: > Hello, > > some of your tests probably take long time and block the main thread (for > example some network test with timeout - you can see how long each test > takes by running monit in debug mode with the -v option). When the action > is requested, monit wakes up and tries to do the action as soon as > possible. However if the test cycle is in progress already, it will try to > perform the action as part of the service list processing (depending on the > position of the service with action request in the list). We will fix this > design and will make the tests and actions non-blocking. It may also help > to update Monit to latest version - speed of some tests was improved. > > Regards, > Martin > > > > > On 11 Nov 2014, at 16:54, Justin Giancola <[email protected]> > wrote: > > > > Hello, > > > > I have used Monit for many years now and it has been very solid and > reliable. So thanks. > > > > I have noticed something I haven't seen before and I'm wondering whether > this is new behaviour and if so, how I can configure Monit to work the way > I expect. > > > > I have noticed that when I am monitoring services, there is a long delay > (90s or more) between issuing the command `$ monit start myservice` and > when the service actually starts. Here is an example: > > > > Let's say I have a service "myservice" currently running with the > following status: > > > > Process 'myservice' > > status Running > > monitoring status Monitored > > > > and I issue `$ monit stop myservice`, it will then transition to > > > > Process 'myservice' > > status Not monitored > > monitoring status Not monitored > > > > Now, after issuing `$ monit start myservice`, the status becomes > > > > Process 'myservice' > > status Not monitored - start pending > > monitoring status Not monitored > > > > Now, it will eventually transition back to Running/Monitored, but it > stays in the start pending state for a very long time. > > > > During this period, if I try to issue any commands I get the message > > > > monit: action failed -- Other action already in progress -- please try > again later > > > > I should also mention that I am running a very simple config file, just > > > > set daemon 20 > > > > check process myservice > > with pidfile /var/run/myservice.pid > > start program = "/usr/sbin/service myservice start" > > stop program = "/usr/sbin/service myservice stop" > > > > (logging and httpd config elided). > > > > As mentioned, I've been running other installs of Monit for many years > and haven't observed this behaviour so I suspect that I am missing > something obvious that was added in a more recent version. The example > output above was generated using Monit 5.6. > > > > If anyone would be able to point me in the right direction that would be > much appreciated. > > > > Thanks, > > > > > > Justin > > -- > > To unsubscribe: > > https://lists.nongnu.org/mailman/listinfo/monit-general > > > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general >
-- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
