Univention Bugzilla – Bug 45489
Cron job for univention-sa-learn without locking
Last modified: 2022-03-14 13:39:12 CET
The cron job "univention-spamassassin" in /etc/cron.daily/, that calls univention-sa-learn on a daily basis, does not perform locking. Therefore customers with large mail spools will run into the problem, that the next instance of the daily learn job is started before the current one has finished its job (overlapping cron jobs). There should be some kind of locking.
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.
The behaviour hasnt changed in UCS 4.4. A customer has noticed that univention-sa-learn is causing a significant daily load even in the early stage of a project where mailboxes have been deployed but the amount of messages and especially the not mentionable usage os Spam/Ham folders should not cause a load peak for over 8 hours. Beside the more generic question if a training based on spam/ham classification is still appropriate nowadays we should look if there is a better and scalable solution.
This issue has been filed against UCS 4.3. UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.
reopen because of my remark in comment 2 regarding UCS 4.4