This bug was fixed in the package clamav - 0.100.1+dfsg-1ubuntu0.14.04.2 --------------- clamav (0.100.1+dfsg-1ubuntu0.14.04.2) trusty-security; urgency=medium
* SECURITY REGRESSION: clamav-daemon fails to start due to options removed in new version and manually edited configuration file. (LP: #1783632) - debian/patches/Deprecate-unused-options-instead-of-removing-it.patch: add patch from Debian stretch to simply warn about removed options. -- Marc Deslauriers <marc.deslauri...@ubuntu.com> Thu, 26 Jul 2018 10:28:32 -0400 ** Changed in: clamav (Ubuntu Trusty) Status: Confirmed => Fix Released ** Changed in: clamav (Ubuntu Bionic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1783632 Title: clamav-daemon won't start after upgrade to 0.100.1+dfsg, complaining of "Unknown option StatsEnabled" Status in clamav package in Ubuntu: Confirmed Status in clamav source package in Precise: Confirmed Status in clamav source package in Trusty: Fix Released Status in clamav source package in Xenial: Fix Released Status in clamav source package in Bionic: Fix Released Status in clamav source package in Cosmic: Confirmed Status in clamav package in Debian: Fix Released Bug description: On Ubuntu 16.04 LTS, clamav-daemon was upgraded 0.99.4+addedllvm- 0ubuntu0.16.04.1 to 0.100.1+dfsg-1ubuntu0.16.04.1 as part of USN 3722-1 (https://usn.ubuntu.com/3722-1/). After the upgrade clamav- daemon fails to restart: # systemctl status clamav-daemon ● clamav-daemon.service - Clam AntiVirus userspace daemon Loaded: loaded (/lib/systemd/system/clamav-daemon.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/clamav-daemon.service.d └─extend.conf Active: failed (Result: exit-code) since Wed 2018-07-25 11:57:22 PDT; 1min 6s ago Docs: man:clamd(8) man:clamd.conf(5) https://www.clamav.net/documents/ Process: 20017 ExecStart=/usr/sbin/clamd --foreground=true (code=exited, status=1/FAILURE) Process: 20013 ExecStartPre=/bin/chown clamav /run/clamav (code=exited, status=0/SUCCESS) Process: 20008 ExecStartPre=/bin/mkdir /run/clamav (code=exited, status=1/FAILURE) Main PID: 20017 (code=exited, status=1/FAILURE) Jul 25 11:57:22 smtp4 systemd[1]: Starting Clam AntiVirus userspace daemon... Jul 25 11:57:22 smtp4 mkdir[20008]: /bin/mkdir: cannot create directory ‘/run/clamav’: File exists Jul 25 11:57:22 smtp4 systemd[1]: Started Clam AntiVirus userspace daemon. Jul 25 11:57:22 smtp4 clamd[20017]: ERROR: Parse error at line 76: Unknown option StatsEnabled Jul 25 11:57:22 smtp4 clamd[20017]: ERROR: Can't open/parse the config file /etc/clamav/clamd.conf Jul 25 11:57:22 smtp4 systemd[1]: clamav-daemon.service: Main process exited, code=exited, status=1/FAILURE Jul 25 11:57:22 smtp4 systemd[1]: clamav-daemon.service: Unit entered failed state. Jul 25 11:57:22 smtp4 systemd[1]: clamav-daemon.service: Failed with result 'exit-code'. The regression seems to have been introduced upstream: 0.99.4 supports StatsEnabled and related options in clamd.conf, whereas 0.100.0 dropped support for those directives. See https://github.com/Cisco-Talos/clamav-devel/commit/16bd67 . /etc/clamav/clamd.conf could be regenerated programmatically, but that was not automatically done as part of the upgrade. I'm filing this as an Ubuntu bug because a security upgrade should never cause a production server to break, and because USN 3722-1 never mentions the possibility of such breakage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1783632/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp