Debian 10 – Cron jobs fail silently from PATH issues – Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Scheduled tasks do not run as expected, causing missed maintenance operations.

Environment & Reproduction

Common when scripts rely on interactive shell PATH or profile files.

Root Cause Analysis

Cron runs with a minimal environment, so unqualified commands are not found.

Quick Triage

Review `/var/log/syslog` for cron execution lines and command-not-found output.

Step-by-Step Diagnosis

Run script with a clean environment (`env -i`) to reproduce missing PATH and variable assumptions.

Solution – Primary Fix

Use absolute command paths and define required environment variables directly in crontab.

Solution – Alternative Approaches

Migrate critical jobs to systemd timers with explicit environment control.

Verification & Acceptance Criteria

Scheduled runs complete successfully and produce expected artifacts/log output.

Rollback Plan

Restore previous crontab entry if new invocation logic fails unexpectedly.

Prevention & Hardening

Require cron jobs to be idempotent and fully path-qualified.

Related Errors & Cross-Refs

Related to shell mismatch (`/bin/sh` vs `/bin/bash`) and locale assumptions.

Related tutorial: View the step-by-step tutorial for debian-10.

View all debian-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Debian cron and systemd timer operational guidance.