-
-
Notifications
You must be signed in to change notification settings - Fork 18.6k
services.mysqlBackup: Backup job might break due to garbage collection #29031
Copy link
Copy link
Closed
Labels
0.kind: bugSomething is brokenSomething is broken1.severity: blockerThis is preventing another PR or issue from being completedThis is preventing another PR or issue from being completed3.skill: sprintableA larger issue which is split into distinct actionable tasksA larger issue which is split into distinct actionable tasks6.topic: nixosIssues or PRs affecting NixOS modules, or package usability issues specific to NixOSIssues or PRs affecting NixOS modules, or package usability issues specific to NixOS
Milestone
Metadata
Metadata
Assignees
Labels
0.kind: bugSomething is brokenSomething is broken1.severity: blockerThis is preventing another PR or issue from being completedThis is preventing another PR or issue from being completed3.skill: sprintableA larger issue which is split into distinct actionable tasksA larger issue which is split into distinct actionable tasks6.topic: nixosIssues or PRs affecting NixOS modules, or package usability issues specific to NixOSIssues or PRs affecting NixOS modules, or package usability issues specific to NixOS
Fields
Give feedbackNo fields configured for issues without a type.
Issue description
Surprise email from cron daemon:
The cron job created by the backup service is broken. Several referenced paths do no longer exist:
Given enough time I will eventually reimplement the service using systemd-timers (as it was already discussed in #24728) but I might not get this done in time for the next release.
edit: It seems to me that services.cron.systemCronJobs it severly broken. Changes are sometimes not detected and cron runs for quite some time with an old version of the crontab (or no crontab at all!)
Steps to reproduce
Technical details