# Cron check fails for no reason

**URL:** https://discourse.sensu.io/t/cron-check-fails-for-no-reason/35
**Category:** Sensu Classic (EOL)
**Created:** [June 3, 2013, 8:23pm UTC](https://discourse.sensu.io/t/cron-check-fails-for-no-reason/35 "2013-06-03T20:23:56Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Carl\_Mercier](https://avatars.discourse-cdn.com/v4/letter/c/a4c791/32.png) [@Carl\_Mercier](https://discourse.sensu.io/u/Carl_Mercier)
#### Post date: [June 3, 2013, 8:23pm UTC](https://discourse.sensu.io/t/cron-check-fails-for-no-reason/35/1 "2013-06-03T20:23:56Z")

</div>

Thanks.

I figured out the issue and how to solve it.

Basically, `ps` only returns the current user’s process when user is non-root. This is because of OVH’s custom kernel with grsecurity. It took me a while to figure out why this was happening.

I installed a vanilla kernel and it’s working great now. Hopefully this will help someone in the future!

-c

> **···**
>
> On Sunday, June 2, 2013 10:50:43 PM UTC-4, 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/35/2 "2018-11-22T02:04:54Z")

</div>