After a fresh install (SL 6.3) I walk through the post-installation wizard of Virtualmin Pro. A problem occured when I want to enable the Clam AV Virusscanner in the virus section:
A problem occurred testing the ClamAV server scanner :
ERROR: Can’t connect to clamd: No such file or directory
when I chose NO I can walk through, but, off course, I did not want that. I didn’t had that problem before with my other hosting servers
running /etc/init.d/clamd restart as andreycheck suggested didn’t work. There is no clamd in /etc/init.d/
I instead ran /etc/init.d/clamav-daemon restart and the following was the output:
Stopping ClamAV daemon: clamd.
Clamav signatures not found in /var/lib/clamav … failed!
Please retrieve them using freshclam … failed!
Then run ‘/etc/init.d/clamav-daemon start’ … failed!
So as it says, I ran freshclam and the output was:
ClamAV update process started at Sat Nov 3 22:08:00 2012
Downloading main.cvd [100%]
main.cvd updated (version: 54, sigs: 1044387, f-level: 60, builder: sven)
Downloading daily.cvd [100%]
daily.cvd updated (version: 15535, sigs: 278578, f-level: 63, builder: guitar)
Downloading bytecode.cvd [100%]
bytecode.cvd updated (version: 191, sigs: 37, f-level: 63, builder: neo)
Database updated (1323002 signatures) from db.local.clamav.net (IP: 194.47.250.218)
After that, I ran /etc/init.d/clamav-daemon start
The daemon started, I went back to Virtualmin’s web interface, clicked “yes” for “Run ClamAV server scanner?”, I hit “Next”, and everything worked.
So in this case, the clamAV daemon wasn’t even running. Running freshclam and starting the daemon made the Virtualmin setup process for ClamAV run smoothly.
I then also had same issue with Spamassin not getting started properly by Virtualmin’s setup wizzard, but this fixed it:
/etc/init.d/spamassassin start
That worked for me also. When I run into de postinstalation, I also opened a terminal and started clamd (centos). Then I went to the step where I could select wether run clamav or not.
Because I started clamd the selection was already to Yes and I went with no futher problem to the next screen.
I am sure that something is changed after the end of september, because that was the date I installed 4 VirtualMachine’s with Centos and VM GPL. I didn’t experienced that problem then.
You might double-check if Webmin in general (recently) has a problem with starting/stopping services, by going to Webmin’s “System / Bootup and Shutdown” module, and see if you can start/stop ClamAV and Spamassassin there.
If that works, it might just be the Virtualmin installer / post-install wizard that has a problem.
Again today with 3rd installation of Debian 7 on a virtual server.
That’s what I did:
/etc/init.d/clamav-daemon start
[FAIL] Clamav signatures not found in /var/lib/clamav … failed!
[FAIL] Please retrieve them using freshclam … failed!
[FAIL] Then run ‘/etc/init.d/clamav-daemon start’ … failed!
freshclam
ERROR: /var/log/clamav/freshclam.log is locked by another process
ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).
reboot
/etc/init.d/clamav-daemon start
[ ok ] Starting ClamAV daemon: clamd .
I built Virtualmin on Ubuntu 18.04 at least 5 times in last 1 month with no issues whatsoever (as far as build/fresh installation of virtualmin is concerned). However, I just built a new server for Test purposes (before rolling out the new code changes on Prod Server) and I have seen this issue for the first time.
I have tried everything suggested in the forum but the service does not start at all and so the issue persists with both ClamAv as well as spamassassin and Webmin is not ready to be used and so I cannot oroiceed further,
However, the following 5 steps in exact same order did help me fix the issue:
/etc/init.d/clamav-daemon start
/etc/init.d/spamassassin start
Restarted Webmin from within Webmin, waited for 2 mins
Rebooted the Server
Went back to Virtualmin -> System Settings -> Re-Check Configuration
Let the process run thru and it picked up everything needed and now the Webmin is ready to be used.