DB Errors - Nagios down

[jbennett]

ok - I discovered that my /tmp folder was filled with checks in the form of inodes.

It took me a while to delete these and then restart all processes, but I was able to restart postgresql.

I'm going to monitor for the rest of the day to make sure there wasn't something else that caused the system to create all of these check files and not process them.

[lmiltchev]

Sure. Let us know how it goes.

[jwelch]

I got tired of manually deleting orphaned check files in /tmp and created a root cronjob to do it for me:

0 1 * * * /bin/find /tmp -maxdepth 1 -type f -mmin +480 -name "check*" -exec rm {} \;

[jbennett]

jwelch - thanks for the suggestion - I will be implementing this for sure.

I'm just running into this on a somewhat regular basis and would like to know how to prevent it in the first place.

[lmiltchev]

jbennett, jwelch's suggestion will probably help but you are correct - we need to find out why this is happening. I would recommend opening a new support ticket in our email ticketing system. Email your profile at [email protected]. We will review your configs and logs and go from there. Remote session would be almost impossible to schedule this week as we are hosting the Nagios World Conference at the moment, but we can schedule one sometime next week if we need to.