We experienced an outage after 1.5.4+dfsg-0ubuntu0.22.04.1. But it took a few weeks to manifest after either a systemd refresh or a daemon restart.
We had been adding the listener (127.0.0.1:3310) to /usr/lib/systemd/system/clamav-daemon.socket As well as "TCPAddr localhost" in clamd.conf But after the recent update: > systemctl cat clamav-daemon.socket # /lib/systemd/system/clamav-daemon.socket [ . . . ] [Socket] ListenStream=/run/clamav/clamd.ctl #ListenStream=1024 SocketUser=clamav SocketGroup=clamav RemoveOnStop=True ListenStream = 127.0.0.1:3310 # our local config [ . . . ] # /run/systemd/generator/clamav-daemon.socket.d/listen.conf # Automatically generated by clamav-daemon-socket-generator # Based on configuration in /etc/clamav/clamd.conf [Socket] # Clear any existing ListenStream directives ListenStream= ListenStream=localhost:3310 # pulled from clamd.conf ListenStream=/var/run/clamav/clamd.ctl SocketMode=666 SocketGroup=clamav That broke our TCP socket because the blank ListenStream= wiped out our prior ListenStream= and then the new ListenStream= populated a hostname, which systemd does not like. Switching clamd.conf to "TCPAddr 127.0.0.1" resolved our situation. Ideas: 1) Expose "you're trying to put a hostname in systemd" as an error. 2) Perhaps, be lazy about wiping out prior art with the empty ListenStream. 3) Is/should the package be forcing systemd to update and restart the socket and the daemon? I would have expected this to break when the package updated. Thank you for your hard work maintaining this package for us! -danny -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2129160 Title: [FFe] [SRU] dpkg-reconfigure clamav-daemon does not respect TCP configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2129160/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
