digitalpulse
May 2 2007, 01:58 PM
When attempting to upload a file via the file manager in cpanel this error is received: Virus Detected; File not Uploaded! (Clamd is not configured properly.) While I have no idea why it would attempt to use clamd when uploading a file, I attempted to look further. One of the things I tried was a restart of exim since I know that that will restart clamd. That is when I receive this error: Starting clamd: ERROR: Please define server type (local and/or TCP). From there I attempted to look at the clamd.conf file which only has the following line in it: FixStaleSocket yes .
I have no idea where to specify server type and need some help.
markcausa
May 2 2007, 08:16 PM
Hmmm. Tough one here...
Do you need clamd on at all?
digitalpulse
May 3 2007, 12:10 PM
Well what I do know is that clamd was working fine, before last Monday or Tuesday. I am not even sure why it is not working correctly now other than an cpanel update which wasn't complete or something on that line. As for whether or not I need it, my understanding is that it is standardly run with exim.
markcausa
May 4 2007, 08:37 AM
Well, yeah. As you may know, since cPanel releases a new update very often, problems arise often.
Did you try /scripts/upcp in SSH? Did that fix it?
digitalpulse
May 4 2007, 03:43 PM
There is a cron set to run that script nightly, but I will run it again just to make sure. I'll get back later if that has or has not fixed the issue. I suspect that since it does run nightly and the clamd was still down when I restart exim (for another reason) a little bit ago it has not yet been resolved.
digitalpulse
May 4 2007, 04:04 PM
Alright, the update just finished and I attempted to restart exim again. I still receive the: Starting clamd: ERROR: Please define server type (local and/or TCP). error when doing so. Any idea where to define that in the configuration so it will work correctly again?
omshivaprakash
May 23 2007, 09:53 AM
Ok, its mainly due to the clamavconnector Addon module installed.
Uninstall it from WHM -> Addon module section and install it back.
This did fix the issue for me. Trying to find the config changes.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.