Troubleshooting / symptôme

systemd timer does not trigger

A task planned via systemd does not run at the expected time.

⌚ About 3 min read
View my favorites
Real-world problem · V2

Quick troubleshooting view

What you are seeing

A task planned via systemd does not run at the expected time.

Likely causes
  1. timer 1993.
  2. OnCalendar.
  3. service.
First checks
  1. Limit the impact.
  2. Collecting Evidence.
  3. Test the the simplest hypothesis.
Recommended actions
  1. Correct the confirmed cause rather than the symptom.
  2. Document the change and result.
  3. Establish supervision if the defect can recur.
Start Symptom → Cause →
LinuxIntermediate.

A task planned via systemd does not run at the expected time.

Important: relevez toujours le message d’erreur exact et l’heure du problème avant de modifier la configuration. Les actions proposées doivent être adaptées à votre environnement.

Causes probables

  • timer 1993.
  • OnCalendar.
  • service.

Diagnostic étape par étape

  1. 1

    Limit the impact.

    Identify whether a position, service or entire site is affected.

  2. 2

    Collecting Evidence.

    Keep the message accurate, time, and associated logs.

  3. 3

    Test the the simplest hypothesis.

    Compare with equipment or functional path.

  4. 4

    Correct and validate.

    Apply only one change at a time and retester.

Commands utiles

systemctllist-timers --all.

Solutions possibles

  • Correct the confirmed cause rather than the symptom.
  • Document the change and result.
  • Establish supervision if the defect can recur.
Quand escalader ?

Cadader if the impact extends, if the data are at risk or if the cause involves irreversible modification.

♡ 0