Hi there, On Tue, 16 Aug 2022, John wrote:
I apologise in advance if this question is trivial but I am getting very lost. [...] recently I started using the Debian package rather that a self-build (mainly because clamav requires an increase of support code)
It isn't too difficult to set up a build system on Debian but there is quite a bit to do. It would probably be worth your while to put in the effort get on top of it. There's help here. If you use packages, unfortunately most package maintainers seem to like a configuration for ClamAV which is very different from that which which you'll be familiar if you've been building it yourself. Things are in different places, and ownerships and groups will be different. You will need to go through all the configuration methodically. You can use 'clamconf' to see most of the important configuration settings.
... Starting ClamAV daemon: Tue Aug 9 16:36:00 2022 -> !LOCAL: Socket file /var/run/clamav/clamd could not be bound: Permission denied Tue Aug 9 16:36:00 2022 -> *Closing the main socket. I have tried changing ownership/permissions on /var/run/clamav with no noticeable affect. In the past I had to change ownership to Debian-exim but that does not seem sufficient.
You haven't actually said what permissions and ownerships you tried, but just to see if the permissions really are the problem you could try chmod +777 /var/run/clamav/ I don't mean for you to use those permissions routinely of course. Another packaging issue is that there's usually an init script or systemd configuration to start clamd, and that might not do what you expect. Instead of relying on that sort of thing, at least to get clamd running initially you can start it from the command line. If you do that you can specify on the command line the configuration file to be used so there's no room for doubt: # /path/to/clamd -c /path/to/clamd.conf The '#' there means you're to start clamd as root. It will read its configuration file, drop root permissions and take on the UID of the owner specified in the config. That owner has certain permissions. Set the permissions on the directory which will contain the socket so that they allow that owner (and/or group if you like) to create the socket. It might be helpful to configure verbose logging to a file which you specify in the config rather than e.g. relying on syslog and then hunting for messages from clamd in the system logs. If you still have problems post the output of the command clamconf -n to the list. -- 73, Ged. _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/Cisco-Talos/clamav-documentation https://docs.clamav.net/#mailing-lists-and-chat
