# Sensu checks from like sensu-plugins-disk-checks not found after reboot

**URL:** <https://discourse.sensu.io/t/sensu-checks-from-like-sensu-plugins-disk-checks-not-found-after-reboot/568>\
**Category:** Sensu Classic (EOL)\
**Created:** [March 30, 2016, 3:06pm UTC](https://discourse.sensu.io/t/sensu-checks-from-like-sensu-plugins-disk-checks-not-found-after-reboot/568 "2016-03-30T15:06:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sonny\_Alvesdias](https://avatars.discourse-cdn.com/v4/letter/s/9e8a1a/32.png) [@Sonny\_Alvesdias](https://discourse.sensu.io/u/Sonny_Alvesdias)\
**Post date:** [March 30, 2016, 3:06pm UTC](https://discourse.sensu.io/t/sensu-checks-from-like-sensu-plugins-disk-checks-not-found-after-reboot/568/1 "2016-03-30T15:06:48Z")

</div>

Hi all,

I have a weird situation where, when any of my monitored instance reboots, it reboots properly and can be tracked in sensu But it seems its PATH variable is not set to the right value as the checks I set are all “not found”.

In that case now, I restart the sensu-client service and everything’s come back to normal… So what could be wrong that on boot it cannot set the right PATH and any time later it can?

What can I do to avoid to have to do “sensu-client restart” after reboot?

Thanks

---

<div class="post-metadata">

**Author:** ![Alexander\_Skiba](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/alexander_skiba/32/408_2.png) [@Alexander\_Skiba](https://discourse.sensu.io/u/Alexander_Skiba)\
**Post date:** [March 31, 2016, 11:25am UTC](https://discourse.sensu.io/t/sensu-checks-from-like-sensu-plugins-disk-checks-not-found-after-reboot/568/2 "2016-03-31T11:25:55Z")

</div>

Have you checked the log files for strange things? E.g. in Ubuntu it’s in

/var/log/sensu/…

``

Also, it might help to post a **redacted** version of one check configuration.

> **···**
>
> On Wednesday, March 30, 2016 at 5:06:48 PM UTC+2, [sonny.a...@pixelmatic.com](mailto:sonny.a...@pixelmatic.com) wrote:
> 
> > I have a weird situation where, when any of my monitored instance reboots, it reboots properly and can be tracked in sensu But it seems its PATH variable is not set to the right value as the checks I set are all “not found”.
> 
> > 
> 
> > In that case now, I restart the sensu-client service and everything’s come back to normal… So what could be wrong that on boot it cannot set the right PATH and any time later it can?
