[Bug 201919] sysutils/monit delay of several minutes on "monit stop"

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201919

            Bug ID: 201919
           Summary: sysutils/monit delay of several minutes on "monit
                    stop"
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: sirdice at gmail.com
                CC: martinp at tildeslash.com
             Flags: maintainer-feedback?(martinp at tildeslash.com)
                CC: martinp at tildeslash.com

We use sysutils/monit (and M/Monit) to control several services. Since version
5.12.2 there's a delay of several minutes when shutting down a service.

For example, we have the following in monitrc:
check process apache with pidfile  /var/run/httpd.pid
  start program = "/usr/local/etc/rc.d/apache22 start" with timeout 60 seconds
  stop program  = "/usr/local/etc/rc.d/apache22 stop"
  if cpu > 60% for 2 cycles then alert
  if cpu > 80% for 5 cycles then alert
  if cpu > 90% for 6 cycles then restart
  if totalmem > 14000.0 MB for 5 cycles then alert
  if totalmem > 15000.0 MB for 5 cycles then restart
  if children > 750 then alert
  if failed host 172.17.40.104 port 80 protocol http
                     and request "/system/"
                     for 2 cycles then restart
  if 3 restarts within 15 cycles then timeout
  group server

A "monit stop apache" takes several minutes for Apache to actually start
shutting down. This causes problems with our automated deployment scripts. With
previous versions the shutdown happened immediately after issuing "monit stop
apache". A normal '/usr/local/etc/rc.d/apache22 stop' stops the service almost
immediately. 

Version 5.12.1 did not exhibit this behavior, all versions (5.12.2, 5.13 and
5.14) after it do. 

For the time being I've downgraded to Monit 5.12.1. 

(This may need to be fixed upstream)

-- 
You are receiving this mail because:
You are the assignee for the bug.