what the hell is this? you changed a lot of stuff to systemd units and now there is still some cronjob which tries to load signatues and do who knows what on machines not supposed to run freshclam at all? just because a package is installed don't mean it has any business to run and previously it didn't - the shipped freshcal stuff is completly unused and updates are done by a service preadting your changes yaers ago and then rsync the updated signatures to destination servers, the amchine spewing OOM is not supposed to have any signartures on it at all [root@backup-buildserver:/etc/cron.d]$ rpm -q --file /etc/cron.d/clamav-update clamav-update-0.102.2-1.fc31.x86_64 ERROR: Database load killed by signal 9 ERROR: Database test FAILED. ERROR: Unexpected error when attempting to update database: daily ERROR: Database update process failed: Test failed (8) ERROR: Update failed. [Mon Feb 10 12:52:16 2020] Out of memory: Killed process 815129 (freshclam) total-vm:660480kB, anon-rss:537504kB, file-rss:0kB, shmem-rss:0kB, UID:490 pgtables:1156kB oom_score_adj:0 [root@backup-buildserver:/etc/cron.d]$ systemctl status clamav-freshclam.service ● clamav-freshclam.service Loaded: masked (Reason: Unit clamav-freshclam.service is masked.) Active: inactive (dead)
FEDORA-2020-eb709b2d86 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-eb709b2d86
clamav-0.102.2-2.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-eb709b2d86
0.102.2-2.fc31 Warning: clamav-update package changed Now we provide clamav-freshclam.service systemd unit instead old scripts and the cron.d entry. Unfortunately this may break existing unattended installations. Please run 'systemctl enable clamav-freshclam --now' to enable freshclam updates again. this is pure nonsense and i suggest to read how systemd works! you don't enable a periodic service you enable timers but you don't provide one /usr/lib/systemd/system/clamav-freshclam.service expects a /usr/lib/systemd/system/clamav-freshclam.timer which defines when "clamav-freshclam.service" get started, that unit with "ExecStart=/usr/bin/freshclam -d --foreground=true" will work *once* and then fail
that one below (you as packager have your business in /usr/lib/systemd/system and not /etc/systemd/system) fires "letsencrypt.service" nor matter if it is installed in /usr or overriden by the local admin in /etc every 5 minutes and you DO NOT enable the service itself RTFM: https://wiki.archlinux.org/index.php/Systemd/Timers ------------------------------------------ [root@srv-rhsoft:~]$ cat /etc/systemd/system/letsencrypt.timer [Unit] Description=Letsencrypt-Updateservice Timer After=network.service systemd-networkd.service network-online.target httpd.service [Timer] OnCalendar=*:0/5 Persistent=true RandomizedDelaySec=30 [Install] WantedBy=multi-user.target ------------------------------------------
and fianally don't do such crazy changes back and forth in the middle of a stable release especially in case you don't know what you are doing at all
Dear tester, thank you for your report what sentence do you suggest when I remove a bunch of files with the systemd file (clamav-freshclam) and put freshclam working as upstream recommends 8 year later ?
that one needs to enable clamav-freshclam.timer but you fail to understand how systemd works and miss the timer for the freshclam update-service, otherwise you won't introduce a long running daemon where a oneshot-service with a timer would do it's job in doubt you need a post-script which enables / starts the service / timer based on the local configuration if you insist doing breaking changes in the middle of a release instead of rawhide now it's too late anyways but yu clearly should refrain from such *invaisve* changes in the middle of a stable Fedora release, such things like yesterday with OOM beause some cron file while the last update removed /etc/sysconfig/freshclam and change are unacceptable in a stable release
(In reply to Harald Reindl from comment #7) > now it's too late anyways but yu clearly should refrain from such *invaisve* > changes in the middle of a stable Fedora release, such things like yesterday > with OOM beause some cron file while the last update removed > /etc/sysconfig/freshclam and change are unacceptable in a stable release that was because I did a mistake and instead [2] I put [1] , the /etc/freshclam.conf have [3] , no need timer , it is unit systemd provide by upstream ... [1] %if 0%{?fedora} && 0%{?rhel} >= 8 %bcond_with old_freshclam [2] %if 0%{?fedora} || 0%{?rhel} >= 8 %bcond_with old_freshclam [3] # Number of database checks per day. # Default: 12 (every two hours) #Checks 24
you didn't get it: ALL that invasive changes in packaging are *not* suiteable in the middle of a stable release when they need user actions after an update and there is no unavoidable reason for it
(In reply to Harald Reindl from comment #9) > you didn't get it: ALL that invasive changes in packaging are *not* > suiteable in the middle of a stable release when they need user actions > after an update and there is no unavoidable reason for it In my point of view it is a very small detail that I change and (as message says ) . But you can join to the club on https://bugzilla.redhat.com/show_bug.cgi?id=1800226 .
> In my point of view it is a very small detail that I change and (as message says) if every packager in the distribution changes a small detail and a random point in time where i *must* react manually to keep my systems running as desigend and verified after the latest dist-upgrade i hardly couldn't cope with that load and Fedora as a distribution would be unuseable
clamav-0.102.2-2.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.