1
More ClamAV problems with v14
Problem reported by Robbie Wright - 6/26/2015 at 10:23 PM
Submitted
Upgraded from the most recent v13 to v14 this evening and we're getting this Clam error:
 
Unable to run Clam virus checks: System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:3310
 
After all of the other issues people had with their v14 upgrade, we uninstalled SM, removed all the contents of service/clam, restart the server, and the did the install. Anyone see that issue before?

5 Replies

Reply to Thread
0
Matt Petty Replied
Employee Post
Your ClamAV is not running, check your process list for clamd.exe. Make sure you have C++ 2010 32bit and 64bit installed.
Matt Petty Senior Software Developer SmarterTools Inc. www.smartertools.com
0
Robbie Wright Replied
clamd.exe is not listed in Windows Services but is listed as a running process.

Running a fully patched 2012R2. Had 2010 x86 installed. Completely uninstalled SM, removed the contents of the clam folder, and installed 14.0.5647.

64bit appears to have not been installed prior to v14 and was not installed by the SM installer. I have since manually installed it. What should my next step be to try and get it working again?
0
Matt Petty Replied
Employee Post
I would check your clamd.conf and make sure the listen port is set to 3310.
Does this error happen all the time? Like do you see it making a lot of attempts?
Matt Petty Senior Software Developer SmarterTools Inc. www.smartertools.com
0
Robbie Wright Replied
3310 is config'd as the port.

We manually installed the 64bit version of 2010 C++ redist, rebooted the server, and it appears to be happy again.

I'd check your installer make sure it is running through the correctly sys requirement checks...
0
Matt Petty Replied
Employee Post
Yea we are looking at that. Glad we were able to figure it out. We will be reviewing the installer and fixing the requirements.
Matt Petty Senior Software Developer SmarterTools Inc. www.smartertools.com

Reply to Thread