Why default handler unknown

1- {“timestamp”:“2013-06-22T15:40:24.806664+0300”,“level”:“error”,“message”:“unknown handler”,“handler_name”:“default”} in sensu-server.log

It must be:

I, [2012-01-18T21:18:07.559666 #30970] INFO -- : [publisher]
-- publishing check request -- cron_check -- webservers {"message":"[publisher]
-- publishing check request -- cron_check -- webservers","level":"info","timestamp":"2012-01-18T21:18:07.
%6N-0700"}
I, [2012-01-18T21:25:07.745012 #30970] INFO -- : [result] -- received result
-- sensu-client.domain.tld -- cron_check -- 0 -- CheckProcs OK: Found 1 matching processes; cmd /crond/

2- sudo: /etc/init.d/crond: command not found. Why crond is not stopped by this command? crond is not in folder init.d

Hello,

I believe the docs may have been written against an older version of ubuntu. You could try ps aux | grep cron and killing the PID, or initctl list | grep cron and using the service command to stop cron that way. If you figure anything out, please report back and we can update the docs. Cheers

···

On Saturday, June 22, 2013 5:54:54 AM UTC-7, hasan kenar wrote:

I, [2012-01-18T21:18:07.559666 #30970] INFO -- : [publisher]
-- publishing check request -- cron_check -- webservers {"message":"[publisher]
-- publishing check request -- cron_check -- webservers","level":"info","timestamp":"2012-01-18T21:18:07.
%6N-0700"} I, [2012-01-18T21:25:07.745012 #30970] INFO -- : [result] -- received result
-- sensu-client.domain.tld -- cron_check -- 0 -- CheckProcs OK: Found 1 matching processes; cmd /crond/

1- {“timestamp”:“2013-06-22T15:40:24.806664+0300”,“level”:“error”,“message”:“unknown handler”,“handler_name”:“default”} in sensu-server.log

It must be:

2- sudo: /etc/init.d/crond: command not found. Why crond is not stopped by this command? crond is not in folder init.d