Check for Unbound

Issue #26 resolved
Maison da Silva created an issue

Hi check for unbound in ubuntu server 12 is?

check process unbound with pidfile /var/run/unbound.pid start program = "/etc/init.d/unbound start" stop program = "/etc/init.d/unbound stop" if 5 restarts within 5 cycles then timeout

Thanks Maison

Comments (8)

  1. Maison da Silva reporter

    Corret is

    check process unbound with pidfile /var/run/unbound.pid
      start program = "/etc/init.d/unbound start"
      stop  program = "/etc/init.d/unbound stop"
      if 5 restarts within 5 cycles then timeout
    

    or

    check process unbound with pidfile /var/run/unbound.pid
      start program = "/etc/init.d/unbound start"
      stop  program = "/etc/init.d/unbound stop"
       if failed host 127.0.0.1(or ip machine ex: 172.31.255.X) port 53 type tcp protocol dns then alert
       if failed host 127.0.0.1(or ip machine ex: 172.31.255.X) port 53 type udp protocol dns then alert
       if 5 restarts within 5 cycles then timeout
    
  2. Maison da Silva reporter

    Test

    Process 'unbound' status Connection failed

    check process unbound with pidfile /var/run/unbound.pid
      start program = "/etc/init.d/unbound start"
      stop  program = "/etc/init.d/unbound stop"
       if failed host 127.0.0.1 port 53 type tcp protocol dns then alert
       if failed host 127.0.0.1 port 53 type udp protocol dns then alert
       if 5 restarts within 5 cycles then timeout
    

    Show conection failed see:

    root@dns:~# monit status
    The Monit daemon 5.3.2 uptime: 3m
    
    Process 'unbound'
      status                            Connection failed
      monitoring status                 Monitored
      pid                               5296
      parent pid                        1
      uptime                            20m
      children                          0
      memory kilobytes                  6940
      memory kilobytes total            6940
      memory percent                    0.3%
      memory percent total              0.3%
      cpu percent                       0.0%
      cpu percent total                 0.0%
      port response time                0.000s to 127.0.0.1:53 [DNS via UDP]
      port response time                0.000s to 127.0.0.1:53 [DNS via TCP]
      data collected                    Thu, 10 Apr 2014 11:29:27
    
    System 'system_dns'
      status                            Running
      monitoring status                 Monitored
      load average                      [0.00] [0.01] [0.05]
      cpu                               0.0%us 0.0%sy 0.0%wa
      memory usage                      127672 kB [6.2%]
      swap usage                        0 kB [0.0%]
      data collected                    Thu, 10 Apr 2014 11:29:27
    
    root@dns:~#
    
  3. Tildeslash repo owner

    Hello,

    please try with latest Monit version (5.8) ... the "Connection failed" seems as error flag reset issue, which was fixed long time ago.

  4. Maison da Silva reporter

    Thanks for your support in excellent time. How do I see which version I'm using the Monit?

  5. Tildeslash repo owner

    You can get the version with "monit -V", but according to the"monit status" output, it is Monit 5.3.2:

      The Monit daemon 5.3.2 ...
    
  6. Tildeslash repo owner

    No reply. Closing this issue under the assumption that the problem was fixed by upgrading to a newer Monit version.

  7. Log in to comment