# Cron check fails for no reason

**URL:** <https://discourse.sensu.io/t/cron-check-fails-for-no-reason/34>\
**Category:** Sensu Classic (EOL)\
**Created:** [June 3, 2013, 12:09pm UTC](https://discourse.sensu.io/t/cron-check-fails-for-no-reason/34 "2013-06-03T12:09:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nick\_Stielau](https://avatars.discourse-cdn.com/v4/letter/n/ed8c4c/32.png) [@Nick\_Stielau](https://discourse.sensu.io/u/Nick_Stielau)\
**Post date:** [June 3, 2013, 12:09pm UTC](https://discourse.sensu.io/t/cron-check-fails-for-no-reason/34/1 "2013-06-03T12:09:57Z")

</div>

Strange. Perhaps the client name changed or something after the initial configuration and the failed check is for a different client? You can look at the clients in the dashboard. If you delete the clients, any events will be flushed and the clients will re-register if you restart the sensu-client service. Looking at the client and server logs should help as well.

> **···**
>
> On Sunday, June 2, 2013 7:50:43 PM UTC-7, Carl Mercier wrote:
> 
> > Hi guys.
> 
> > I just installed Sensu for the first time following the instructions on the website. I have the client and server on the same machine. I’m getting alerts this alert in the dashboard:
> 
> > > CheckProcs CRITICAL: Found 0 matching processes; cmd /cron/
> 
> > Running the check manually in the console with ‘/etc/sensu/plugins/check-procs.rb -p cron -C 1’ reports that it’s running:
> 
> > > CheckProcs OK: Found 1 matching processes; cmd /cron/
> 
> > What am I missing?
> 
> > Thanks!
> 
> > -c
> 
> >

---

<div class="post-metadata">

**Author:** ![jspaleta](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/jspaleta/32/141_2.png) [@jspaleta](https://discourse.sensu.io/u/jspaleta)\
**Post date:** [November 22, 2018, 2:04am UTC](https://discourse.sensu.io/t/cron-check-fails-for-no-reason/34/2 "2018-11-22T02:04:54Z")

</div>