📖 ~1 min read
Table of contents
Symptom & Impact
crontab jobs do not run and /var/adm/cron/log shows syntax or environment errors.
Environment & Reproduction
Custom crontab edits with non-standard fields, PATH issues, or missing shebang.
crontab -l
tail /var/adm/cron/log
lssrc -s cron
Root Cause Analysis
Crontab entry has malformed fields, references missing binaries, or lacks PATH context.
Quick Triage
Identify the failing job and check cron daemon status.
lssrc -s cron
tail /var/adm/cron/log
crontab -l | head
Step-by-Step Diagnosis
Run the script manually with cron’s typical environment.
env -i /bin/ksh -c '/scripts/job.sh'
ls -la /scripts/job.sh
file /scripts/job.sh

Solution – Primary Fix
Correct the crontab entry, add full paths, and reinstall the user crontab.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.
crontab -e
chmod +x /scripts/job.sh
tail /var/adm/cron/log

Solution – Alternative Approaches
Use the at command or smitty cron for scheduling assistance and validation.
Verification & Acceptance Criteria
cron log records job runs and outputs appear at expected times.
tail /var/adm/cron/log
ls -la /tmp/jobout
lssrc -s cron
Rollback Plan
Restore the previous crontab backup if the new entry causes side effects.
crontab cron.bak
crontab -l
lssrc -s cron
Prevention & Hardening
Store crontabs in version control and validate with a syntax check before install.
Related Errors & Cross-Refs
Related to skulker job failures, accounting issues, and logrotate misses.
Related tutorial: View the step-by-step tutorial for aix-7.2.
View all aix-7.2 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
IBM AIX 7.2 cron and at command reference.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.