<service> start Generates email noise

[Aaron Scamehorn]

Hello,

From version 4.8 to 4.8.2, the following bug has been introduced:

When we issue a monit <service> start command, we get "Does not exist" and a corresponding "Exists" emails.

Here is the debug output showing this behavior in 4.8.2:
'LogClient' Error testing process id [11034] -- No such process
'LogClient' Error testing process id [11034] -- No such process
'LogClient' start: /cogcap/ccts/bin/logclnt
'LogClient' Error testing process id [11034] -- No such process
Monitoring enabled -- service LogClient
'LogClient' Error testing process id [11034] -- No such process
'LogClient' process is not running
Does not exist notification is sent to address@hidden
'LogClient' Error testing process id [11034] -- No such process
'LogClient' trying to restart
Monitoring disabled -- service LogClient (stop)
'LogClient' Error testing process id [11034] -- No such process
'LogClient' process is running with pid 11189
Exists notification is sent to address@hidden
'LogClient' zombie check passed [status_flag=0000]
'LogClient' loadavg(5min) check passed [current loadavg(5min)=0.2]
'LogClient' cpu usage check passed [current cpu usage=0.0%]
'LogClient' mem amount check passed [current mem amount=2776kB]

Under version 4.8, we don't get the annoying "Does not exist" and a corresponding "Exists" emails:

'LogClient' Error testing process id [10970] -- No such process
'LogClient' Error testing process id [10970] -- No such process
'LogClient' start: /cogcap/ccts/bin/logclnt
'LogClient' Error testing process id [10970] -- No such process
Monitoring enabled -- service LogClient
'LogClient' Error testing process id [10970] -- No such process
'LogClient' Error testing process id [10970] -- No such process
'LogClient' zombie check passed [status_flag=0000]
'LogClient' loadavg(5min) check passed [current loadavg(5min)=0.1]
'LogClient' cpu usage check passed [current cpu usage=0.0%]
'LogClient' mem amount check passed [current mem amount=2776kB]

Additionally, in our config file, we have the following set:
set alert address@hidden only on { nonexist, exec, connection }

We shouldn't be getting an "Exists" email under any circumstance, should we?

Thanks,
Aaron