Thank you for taking the time to file a bug report. So, I've spent some time trying to reproduce it here, but was unsuccessful. Here's what I tried:
- Create a Bionic LXD container. - Grab the .deb files for the last-but-one clamav version that was available in Bionic. They can be found here (for amd64): https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/+build/19629559 - Install the files grabbed above. Verify that the "clamav- freshclam.service" is running. - apt update && apt ugprade. This will upgrade all clamav packages. - Verify that the "clamav-freshclam.service" is still running. Given the unsuccessful attempt to reproduce the problem, I tried searching on the internet for similar reports. I've found some people saying that this scenario might happen when there is a freshclam process blocked, which would prevent the new freshclam process (being started by systemd) from manipulating the log file. I don't know if that's your case, though, because I don't see any explicit error messages saying that there is another blocked freshclam process. I have found https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972974, which, albeit similar, ended up being an apparmor problem that is not present in Ubuntu. I have also double checked your configuration files, and they both seem normal. I'm wondering if this is a problem that happened due to very specific conditions: freshclam must have been busy trying to update the database, and coincidentally unattended-upgrades ran at that very moment and tried to restart the service, leading to the error. Woud you be able to provide a bit more information so that we can try to reproduce the problem determine what's causing it? For example, would you be able to downgrade your freshclam/clamav packages and then update them again? Also, is there anything interesting in journalctl that is worth mentioning here? Some explicit message about the file being locked by another freshclam process, for example? Since there is not enough information in your report to begin triage or to differentiate between a local configuration problem and a bug in Ubuntu, I am marking this bug as "Incomplete". We would be grateful if you would: provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Bug watch added: Debian Bug tracker #972974 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972974 ** Changed in: clamav (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925182 Title: ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1925182/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
