von Thomas Kramer.
Same here!
Since the upgrade from 4.1.x to 4.5.y (and migrating from Debian11 to Debian12), there is no e-mail notification about the course-backup summary anymore. Every other system message is delivered successfully and even all the checkboxes for sending these messages are active. It worked fine bevor the upgrade, since the early 2020s. Every week, on every sunday, we recieved this message. Even if the process was not finished on some of the courses, because of there huge sice (three courses in total about 7-8GB each), but that was fine. The notification was always sent. We have 10k+ courses on our system (from bevor the upgrade), so this should'nt be a cause for this behavior. Every other course on the system (if edited/updated since the last backup) is backed up well and the process finishes. We can see that in the status report (.../report/backups/index.php).
I have no more clue, where I should looking for. What else could be causing this? As far as the logs show, these messages are no longer being sent, which could well indicate a bug?!
Thomas
Since the upgrade from 4.1.x to 4.5.y (and migrating from Debian11 to Debian12), there is no e-mail notification about the course-backup summary anymore. Every other system message is delivered successfully and even all the checkboxes for sending these messages are active. It worked fine bevor the upgrade, since the early 2020s. Every week, on every sunday, we recieved this message. Even if the process was not finished on some of the courses, because of there huge sice (three courses in total about 7-8GB each), but that was fine. The notification was always sent. We have 10k+ courses on our system (from bevor the upgrade), so this should'nt be a cause for this behavior. Every other course on the system (if edited/updated since the last backup) is backed up well and the process finishes. We can see that in the status report (.../report/backups/index.php).
I have no more clue, where I should looking for. What else could be causing this? As far as the logs show, these messages are no longer being sent, which could well indicate a bug?!
Thomas