Using the precompiled binary,monit-5.19.0-linux-x86.tar.gz, I see the same 
behavior.


> On Oct 10, 2016, at 10:41 AM, jobhunt...@aol.com wrote:
> 
> monitrc is attached.
>> $ bin/monit -vI -c monitrc
>> Runtime constants:
>>  Control file       = /home/jones/monit519/monitrc
>>  Log file           = syslog
>>  Pid file           = /home/jones/monit_code/.monit.pid
>>  Id file            = /home/jones/monit_code/.monit.id
>>  State file         = /home/jones/monit_code/.monit.state
>>  Debug              = True
>>  Log                = True
>>  Use syslog         = True
>>  Is Daemon          = True
>>  Use process engine = True
>>  Limits             = {
>>                     =   programOutput:     512 B
>>                     =   sendExpectBuffer:  256 B
>>                     =   fileContentBuffer: 512 B
>>                     =   httpContentBuffer: 1024 kB
>>                     =   networkTimeout:    5 s
>>                     = }
>>  Poll time          = 5 seconds with start delay 0 seconds
>>  Start monit httpd  = False
>> 
>> The service list contains the following entries:
>> 
>> Filesystem Name       = var
>>  Path                 = /var
>>  Monitoring mode      = active
>>  On reboot            = start
>>  Filesystem flags     = if changed then alert
>>  Space usage limit    = if greater than 95.0% then alert
>> 
>> Filesystem Name       = etc
>>  Path                 = /etc
>>  Monitoring mode      = active
>>  On reboot            = start
>>  Filesystem flags     = if changed then alert
>>  Space usage limit    = if greater than 95.0% then alert
>> 
>> System Name           = localhost.localdomain
>>  Monitoring mode      = active
>>  On reboot            = start
>>  CPU usage limit      = if greater than 0.0% for 5 cycles then alert
>>  CPU system limit     = if greater than 65.0% then alert
>>  CPU user limit       = if greater than 75.0% then alert
>>  Memory usage limit   = if greater than 85.0% then alert
>> 
>> -------------------------------------------------------------------------------
>> pidfile '/home/jones/monit_code/.monit.pid' does not exist
>> Starting Monit 5.19.0 daemon
>> 'localhost.localdomain' Monit 5.19.0 started
>> 'var' succeeded getting filesystem statistics for '/var'
>> 'var' filesystem flags has not changed
>> 'var' space usage test succeeded [current space usage=32.2%]
>> 'etc' succeeded getting filesystem statistics for '/etc'
>> 'etc' filesystem flags has not changed
>> 'etc' space usage test succeeded [current space usage=32.2%]
>> 'localhost.localdomain' cpu usage check succeeded [current cpu usage=0.0%]
>> 'localhost.localdomain' cpu system usage check skipped (initializing)
>> 'localhost.localdomain' cpu user usage check skipped (initializing)
>> 'localhost.localdomain' mem usage check succeeded [current mem usage=37.8%]
>> 'var' succeeded getting filesystem statistics for '/var'
>> 'var' filesystem flags has not changed
>> 'var' space usage test succeeded [current space usage=32.2%]
>> 'etc' succeeded getting filesystem statistics for '/etc'
>> 'etc' filesystem flags has not changed
>> 'etc' space usage test succeeded [current space usage=32.2%]
>> 'localhost.localdomain' cpu usage of 2.4% matches resource limit [cpu 
>> usage>0.0%]
>> 'localhost.localdomain' cpu system usage check succeeded [current cpu system 
>> usage=0.8%]
>> 'localhost.localdomain' cpu user usage check succeeded [current cpu user 
>> usage=1.4%]
>> 'localhost.localdomain' mem usage check succeeded [current mem usage=37.8%]
>> 'var' succeeded getting filesystem statistics for '/var'
>> 'var' filesystem flags has not changed
>> 'var' space usage test succeeded [current space usage=32.2%]
>> 'etc' succeeded getting filesystem statistics for '/etc'
>> 'etc' filesystem flags has not changed
>> 'etc' space usage test succeeded [current space usage=32.2%]
>> 'localhost.localdomain' cpu usage of 2.0% matches resource limit [cpu 
>> usage>0.0%]
>> 'localhost.localdomain' cpu system usage check succeeded [current cpu system 
>> usage=0.6%]
>> 'localhost.localdomain' cpu user usage check succeeded [current cpu user 
>> usage=1.1%]
>> 'localhost.localdomain' mem usage check succeeded [current mem usage=37.8%]
>> 'var' succeeded getting filesystem statistics for '/var'
>> 'var' filesystem flags has not changed
>> 'var' space usage test succeeded [current space usage=32.2%]
>> 'etc' succeeded getting filesystem statistics for '/etc'
>> 'etc' filesystem flags has not changed
>> 'etc' space usage test succeeded [current space usage=32.2%]
>> 'localhost.localdomain' cpu usage of 2.0% matches resource limit [cpu 
>> usage>0.0%]
>> 'localhost.localdomain' cpu system usage check succeeded [current cpu system 
>> usage=0.6%]
>> 'localhost.localdomain' cpu user usage check succeeded [current cpu user 
>> usage=0.9%]
>> 'localhost.localdomain' mem usage check succeeded [current mem usage=37.8%]
>> 'var' succeeded getting filesystem statistics for '/var'
>> 'var' filesystem flags has not changed
>> 'var' space usage test succeeded [current space usage=32.2%]
>> 'etc' succeeded getting filesystem statistics for '/etc'
>> 'etc' filesystem flags has not changed
>> 'etc' space usage test succeeded [current space usage=32.2%]
>> 'localhost.localdomain' cpu usage of 2.4% matches resource limit [cpu 
>> usage>0.0%]
>> 'localhost.localdomain' cpu system usage check succeeded [current cpu system 
>> usage=0.7%]
>> 'localhost.localdomain' cpu user usage check succeeded [current cpu user 
>> usage=1.0%]
>> 'localhost.localdomain' mem usage check succeeded [current mem usage=37.8%]
>> 'var' succeeded getting filesystem statistics for '/var'
>> 'var' filesystem flags has not changed
>> 'var' space usage test succeeded [current space usage=32.2%]
>> 'etc' succeeded getting filesystem statistics for '/etc'
>> 'etc' filesystem flags has not changed
>> 'etc' space usage test succeeded [current space usage=32.2%]
>> 'localhost.localdomain' cpu usage of 2.0% matches resource limit [cpu 
>> usage>0.0%]
>> 'localhost.localdomain' cpu system usage check succeeded [current cpu system 
>> usage=0.6%]
>> 'localhost.localdomain' cpu user usage check succeeded [current cpu user 
>> usage=1.0%]
>> 'localhost.localdomain' mem usage check succeeded [current mem usage=37.8%]
>> 'var' succeeded getting filesystem statistics for '/var'
>> 'var' filesystem flags has not changed
>> 'var' space usage test succeeded [current space usage=32.2%]
>> 'etc' succeeded getting filesystem statistics for '/etc'
>> 'etc' filesystem flags has not changed
>> 'etc' space usage test succeeded [current space usage=32.2%]
>> 'localhost.localdomain' cpu usage of 2.4% matches resource limit [cpu 
>> usage>0.0%]
>> 'localhost.localdomain' cpu system usage check succeeded [current cpu system 
>> usage=0.6%]
>> 'localhost.localdomain' cpu user usage check succeeded [current cpu user 
>> usage=0.9%]
>> 'localhost.localdomain' mem usage check succeeded [current mem usage=37.8%]
>> 
>> 
> Syslog output.
>> 
>> Oct 10 10:25:32 localhost monit[16217]: Starting Monit 5.19.0 daemon
>> Oct 10 10:25:32 localhost monit[16217]: 'localhost.localdomain' Monit 5.19.0 
>> started
>> Oct 10 10:25:37 localhost monit[16217]: 'localhost.localdomain' cpu usage of 
>> 2.4% matches resource limit [cpu usage>0.0%]
>> Oct 10 10:25:42 localhost monit[16217]: 'localhost.localdomain' cpu usage of 
>> 2.0% matches resource limit [cpu usage>0.0%]
>> Oct 10 10:25:47 localhost monit[16217]: 'localhost.localdomain' cpu usage of 
>> 2.0% matches resource limit [cpu usage>0.0%]
>> Oct 10 10:25:52 localhost monit[16217]: 'localhost.localdomain' cpu usage of 
>> 2.4% matches resource limit [cpu usage>0.0%]
>> Oct 10 10:25:57 localhost monit[16217]: 'localhost.localdomain' cpu usage of 
>> 2.0% matches resource limit [cpu usage>0.0%]
>> Oct 10 10:26:03 localhost monit[16217]: 'localhost.localdomain' cpu usage of 
>> 2.4% matches resource limit [cpu usage>0.0%]
>> 
>> 
>> 
> 
> <monitrc>
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general

Reply via email to