[clamav-users] clamd does not bind to port when starting through init.d/service ubuntu 16.04
jeff.dyke at gmail.com
Mon Aug 29 08:46:23 EDT 2016
Thanks, the other machines are all 16.04 and all installed the same way as
all configuration is through salt, so i'm using default packaging.
Currently i'm using these to scan uploads and fail them if they don't
succeed. i want to put them on a TCP socket so they can be shared across
servers via HAProxy, which works great when they are properly started.
I'll try your suggestions and report back, i've been gone all weekend, so
sorry for the delay and thanks for you response.
On Sat, Aug 27, 2016 at 12:30 PM, G.W. Haywood <clamav at jubileegroup.co.uk>
> Hi there,
> On Sat, 27 Aug 2016, Jeff Dyke wrote:
> ... if i start clamd with
>> sudo -u clamav /usr/sbin/clamd --config-file=/etc/clamav/clamd.conf
>> it *will* bind to that address and port.
>> When starting via /etc/init.d/clamav-daemon start or sudo service
>> clamav-daemon start it does not bind to the port.
>> ... No ... socket received from systemd.
> Are the other servers also Ubuntu 16.04?
> What are they all doing?
> Anything more from the clamd.conf debug options?
> I use ClamAV only on mail servers. I tend not to use distro packages
> for things mail, and anyway I have yet to use ClamAV on a systemd box
> (and with luck I never will) - but in your shoes I'd be inclined e.g.
> to chmod a-x the ClamAV scripts in /etc/init.d then put something to
> start clamd in /etc/rc.local to see if it works there after the
> network stack is all up and running.
> Help us build a comprehensive ClamAV guide:
More information about the clamav-users