How to remove ClamAV Scanner

rohit09

Well-Known Member
Dec 10, 2010
61
0
56
My server has cento 4

I tried
Code:
Redhat/Fedora: yum remove clamav*
but it shows
Code:
No Packages marked for removal
Please Help me.

My all other accounts facing problem
[6/22/2011 4:49:23 PM] 500 I won't open a connection to 192.168.1.2 (only to 117.194.1.224)
ERROR:> [6/22/2011 4:49:23 PM] Syntax error: command unrecognized.
ERROR:> [6/22/2011 4:49:23 PM] Failed to establish data socket.
 

Infopro

Well-Known Member
May 20, 2003
17,075
524
613
Pennsylvania
cPanel Access Level
Root Administrator
Twitter
If you installed ClamAV from: WHM > cPanel > Manage Plugins, untick the checkbox there and then click Uninstall ClamAV Connector.


About this:

[6/22/2011 4:49:23 PM] 500 I won't open a connection to 192.168.1.2 (only to 117.194.1.224)
ERROR:> [6/22/2011 4:49:23 PM] Syntax error: command unrecognized.
ERROR:> [6/22/2011 4:49:23 PM] Failed to establish data socket.
I'm not exactly sure what the error is telling us, but I do know that 192.168.1.2 is a local IP for your computer for example, nothing on the server should be using that IP anywhere. If you're running cPanel on your home server you'll need to be sure you've got a dedicated IP address or cPanel will not operate as expected.
 

sneader

Well-Known Member
Aug 21, 2003
1,195
67
178
La Crosse, WI
cPanel Access Level
Root Administrator
InfoPro... I don't wish to run ClamAV on a particular box, and I have never checked the box "install and keep updated" for ClamAv, but still, each morning, I've been getting these emails after a recent WHM upgrade:

[checkperlmodules] The perl module File::Scan::ClamAV could not be installed.

This module is required by cPanel, and the system may not function correctly until it is installed, and functional. Below is the results of the auto-install attempt:

Test Run
==============
Can't locate File/Scan/ClamAV.pm in @INC (@INC contains: /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.7/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.6/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.5/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.7/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.6/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 .) at - line 1.
BEGIN failed--compilation aborted at - line 1.
Suggestions on the right way to make ClamAV go away, in this situation?

Thanks!

- Scott
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
42
348
somewhere over the rainbow
cPanel Access Level
Root Administrator
You might also check if the option is still listed in WHM > Service Manager area and uncheck it there. If it isn't listed or checked, these files might still have it:

/etc/chkserv.d/chkservd.conf
/var/run/chkservd/clamd
/etc/chkserv.d/clamd

You'd want to remove the /var/run/chkservd/clamd and /etc/chkserv.d/clamd files, then edit /etc/chkserv.d/chkservd.conf file to remove clamd in it. After that, restart chkservd:

Code:
/scripts/restartsrv_chkservd
You might then want to ensure clamd binary doesn't show on the system:

Code:
whereis clamd
If you see any binary file or others, you would want to remove or move them to root. You would then want to re-run "/scripts/checkperlmodules --full --force" to see if that error ceases to occur.

If the above does not work, please let us know the ticket number so we can see the resolution to the issue to post here.
 

sneader

Well-Known Member
Aug 21, 2003
1,195
67
178
La Crosse, WI
cPanel Access Level
Root Administrator
Thanks guys!

Before I saw Tristan's message, I decided to "install" it via plug-ins, then "uninstall" it via plug-ins, to see if that got everything in sync. I'll know tonight whether that strategy worked or not... and if not, I'll go through Tristan's steps to get 'er done.

Thanks again, and have a great weekend!

- Scott