Skip to content

Cronjobs

The Syncer manages all its automation cronjobs internally. You define which modules to run, in what order, and for which accounts — all from the UI.

Cronjob Groups

Go to: Cronjobs → Cronjob Groups

A Cronjob Group defines:

  • An interval — how often the group should run
  • A time range — the window during which the group is allowed to run
  • An ordered list of jobs to execute

Jobs inside a group run sequentially. If any job fails, the entire group stops. This is intentional — for example, you do not want hosts to be deleted from Checkmk if the import step failed beforehand.

State Table

Go to: Cronjobs → State Table

The State Table keeps one entry per group, showing:

  • When the group will run next
  • The result of the last run
  • Any error messages

To force a group to run immediately or to reset its state, delete or edit its State Table entry.

Running the Scheduler

The Syncer does not have a built-in scheduler daemon. Instead, call the run command periodically from your system cron — every 5 to 10 minutes is typical:

./cmdbsyncer cron run_jobs

Full example with environment activation:

*/5 * * * * cd /opt/cmdbsyncer && source ./ENV/bin/activate && ./cmdbsyncer cron run_jobs

Docker:

*/5 * * * * docker exec CONTAINER_ID /srv/cmdbsyncer cron run_jobs

Docker Compose:

*/5 * * * * docker compose -f /opt/cmdbsyncer/docker-compose.yml exec -T cmdbsyncer /srv/cmdbsyncer cron run_jobs