This happened to me again on a fresh install on a new 16.04 server, and the fix, for me was adding directly to clamav-daemon.socket
[Socket] ListenStream=/run/clamav/clamd.ctl ListenStream=xx.xx.xx.xx:3310 SocketUser=clamav SocketGroup=clamav RemoveOnStop=True Adding it to extend.conf did not work for me, but when i commted everything out of extend.conf and reloaded and restarted it listened on both. I may play around with different configurations in the future but for now, this took up too much time. Seems like its not only me: http://serverfault.com/questions/798587/debian-8-cant-get-clamav-to-listen-on-tcp-3310?newreg=0a11acb857d341e7b3b4a44aed83553e https://answers.launchpad.net/ubuntu/+source/clamav/+question/357500 On Mon, Aug 29, 2016 at 10:01 AM, Jeff Dyke <jeff.d...@gmail.com> wrote: > thats what i assumed/knew just checking. It may be something odd with > this particular lxc container, but it works well with the others, so the > (self start) hack allows me to deploy and test code properly. > > I'll dig around or perhaps just try a complete purge of all things clam > and reinstall. > > On Mon, Aug 29, 2016 at 9:51 AM, Reindl Harald <h.rei...@thelounge.net> > wrote: > >> >> >> Am 29.08.2016 um 15:34 schrieb Jeff Dyke: >> >>> our config locations for the .service files are in slightly different >>> areas, so do you mind saying what distro you're running >>> >> >> Fedora but it does not matter >> >> the whole concept of systemd is when you disable a existing service and >> place a unit with the same name below /etc/systemd/system/ that "systemctl >> enable name.service" enables this one and the distro shipped is no longer >> used in any way >> >> the same for .timer. .socket and what not else >> >> /etc/systemd/system/ has the same strcuture as /usr/lib/systemd/system/ >> and is meant for local overrides / replacements >> >> >> _______________________________________________ >> Help us build a comprehensive ClamAV guide: >> https://github.com/vrtadmin/clamav-faq >> >> http://www.clamav.net/contact.html#ml >> > > _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
