Back to bug 36229

Who When What Removed Added
dcook 2024-11-01 01:28:17 UTC Status NEW CONFIRMED
imani.thomas 2025-01-08 13:40:17 UTC Status CONFIRMED Needs Signoff
david 2025-01-09 08:57:21 UTC Status Needs Signoff Signed Off
david 2025-01-09 08:57:24 UTC Attachment #176230 Attachment is obsolete 0 1
m.de.rooy 2025-01-10 09:30:22 UTC Assignee koha-bugs dcook
QA Contact testopia m.de.rooy
CC m.de.rooy
m.de.rooy 2025-01-10 09:30:45 UTC Status Signed Off Passed QA
Patch complexity --- Trivial patch
m.de.rooy 2025-01-10 09:30:48 UTC Attachment #176284 Attachment is obsolete 0 1
katrin.fischer 2025-01-10 18:20:44 UTC Status Passed QA Pushed to main
Version(s) released in 25.05.00
david 2025-01-28 01:41:50 UTC Text to go in the release notes This fixes the order of the daily cron jobs (/etc/cron.daily/koha-common) so that koha-run-backups is run first.

Reasons for this include:

1. The koha-run-backups cron job takes a backup before running scripts that change database contents. If there is a problem with those scripts, you'll have a very recent backup on which to fallback.

2. It's a resource intensive job. If you have a lot of Koha instances, this means you're running your most intensive job at the end of the job run, which might be a lot later in the day than you anticipate. (Of course, you can update /etc/crontab to change when /etc/cron.daily is run, but this will help reduce impact in the meantime.)
CC david
david 2025-01-28 02:31:23 UTC Text to go in the release notes This fixes the order of the daily cron jobs (/etc/cron.daily/koha-common) so that koha-run-backups is run first.

Reasons for this include:

1. The koha-run-backups cron job takes a backup before running scripts that change database contents. If there is a problem with those scripts, you'll have a very recent backup on which to fallback.

2. It's a resource intensive job. If you have a lot of Koha instances, this means you're running your most intensive job at the end of the job run, which might be a lot later in the day than you anticipate. (Of course, you can update /etc/crontab to change when /etc/cron.daily is run, but this will help reduce impact in the meantime.)
This fixes the order of the daily cron jobs (/etc/cron.daily/koha-common) so that koha-run-backups is run first.

Reasons for this include:

1. The koha-run-backups cron job takes a backup before running scripts that change database contents. If there is a problem with those scripts, you'll have a very recent backup on which to fallback.

2. It's a resource intensive job. If you have a lot of Koha instances, this means you're running your most intensive job at the end of the job run, which might be a lot later in the day than you anticipate. (Of course, you can update /etc/crontab to change when /etc/cron.daily is run, but this will help reduce impact in the meantime.)

Deployment of this change:
- New installations: This change will seamlessly apply for new installations.
- Existing installations:
. You HAVEN'T manually modified the crontab: it will seamlessly apply.
. You HAVE manually modified the crontab: you will be prompted, and will need to decide about applying the change.
. Where deployment tools are used (such as Ansible): this will depend on what tools you use and how they are configured.

Back to bug 36229