Error in monit 5.18 Cannot activate service check. The process status engine was disabled.

Issue #379 resolved
АндрейК created an issue

We upgrade up to monit 5.18 and see errors when start monit on some servers.

Part of config:

check system localhost
    group system
    group admin
    if memory usage > 95% for 3 cycles then alert
    if memory usage > 90% for 5 cycles then alert
    if swap usage > 25% for 5 cycles then alert
    if cpu usage > 95% for 5 cycles then alert

# uname -a Linux localhost 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29) x86_64 GNU/Linux

# monit -vv
system statistic error -- cannot get system boot time
Adding host allow 'localhost'
Adding net allow '127.0.0.1'
Adding net allow '78.47.64.63'
Adding net allow '172.31.1.100'
Adding credentials for user 'monit'
Adding credentials for user 'admin'
/etc/monitrc:26: Cannot activate service check. The process status engine was disabled. On certain systems you must run monit as root to utilize this feature)
 'if'
-------------------------------------------------------------------------------
    monit() [0x41b6b3]
    monit() [0x41be0f]
    monit() [0x4055c7]
    monit() [0x40d2f7]
    monit() [0x40d9d8]
    monit() [0x411f4b]
    monit() [0x4132f5]
    /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fc381d2eb45]
    monit() [0x404d2a]
-------------------------------------------------------------------------------
/etc/monitrc:27: Cannot activate service check. The process status engine was disabled. On certain systems you must run monit as root to utilize this feature)
 'if'
-------------------------------------------------------------------------------
    monit() [0x41b6b3]
    monit() [0x41be0f]
    monit() [0x4055c7]
    monit() [0x40d2f7]
    monit() [0x40d9d8]
    monit() [0x411f4b]
    monit() [0x4132f5]
    /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fc381d2eb45]
    monit() [0x404d2a]
-------------------------------------------------------------------------------
/etc/monitrc:28: Cannot activate service check. The process status engine was disabled. On certain systems you must run monit as root to utilize this feature)
 'if'
-------------------------------------------------------------------------------
    monit() [0x41b6b3]
    monit() [0x41be0f]
    monit() [0x4055c7]
    monit() [0x40d2f7]
    monit() [0x40d9d8]
    monit() [0x411f4b]
    monit() [0x4132f5]
    /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fc381d2eb45]
    monit() [0x404d2a]
-------------------------------------------------------------------------------
/etc/monitrc:29: Cannot activate service check. The process status engine was disabled. On certain systems you must run monit as root to utilize this feature)
 'if'
-------------------------------------------------------------------------------
    monit() [0x41b6b3]
    monit() [0x41be0f]
    monit() [0x4055c7]
    monit() [0x40d2f7]
    monit() [0x40d9d8]
    monit() [0x411f4b]
    monit() [0x4132f5]
    /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fc381d2eb45]
    monit() [0x404d2a]
-------------------------------------------------------------------------------

Comments (7)

  1. Tildeslash repo owner

    Fixed: Issue #379: A linux system with lots of interrupts may disable process and system resource checks.

    Fixed: If the resource check is disabled (for example because the user doesn't have privileges to read the data), emit just warning on startup.

    → <<cset de64d110b01e>>

  2. Alexander Blagoev

    Hello,

    I can confirm the commit fixes the issue. Latest master works without a problem, where as 5.18 failed.

    System is huge, 32 CPU cores, 96 GB Ram.

  3. Log in to comment