> Source: [sk92873](https://support.checkpoint.com/results/sk/sk92873)

# sk92873 - Cron Jobs stop running

| Property | Value |
|----------|-------|
| Solution ID | sk92873 |
| Date Created | 2013-05-24 |
| Last Modified | 2016-03-06 |
| Technical Level | Advanced |
| Products | Security Gateway, Security Management Server |
| Versions | R82.10, R82, R81.20, R82.10, R82, R81.20, R82.20 |
| OS | Gaia |

## Symptoms

- * after a while the cron job stops running
* Get the following error in the /var/log/messages or /var/log/cron:
* crond\[4035\]: Authentication token is no longer valid\^ new one required
* CRON (admin) ERROR: failed to open PAM security session: Success
* CRON (admin) ERROR: cannot set security context

## Cause

- running the command : "chage -l admin"

Last password change : Nov 29, 2012  
Password expires : Feb 27, 2013  
Password inactive : never  
Account expires : never  
Minimum number of days between password change : 0  
Maximum number of days between password change : 90  
Number of days of warning before password expires : 7

- running ps -aux\|grep crond, shows that the crond daemon runs under the admin account :

admin 2898 0.0 0.0 3192 1132 ? Ss Apr06 0:00 crond

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content