Ignoring deprecated option AllowSupplementaryGroups error

[magicalwonders]

Hi,

I'm running CENTOS 6.10 virtuozzo v72.0.10. After a recent update, I've been receiving the following daily cron warning -

/etc/cron.daily/freshclam:
WARNING: Ignoring deprecated option AllowSupplementaryGroups at line 60
​

I've contacted my hosting support and asked them to stop the message or fix the issue, and they've responded as follows -

The message received from cPanel updates which run daily. Some part of the message is from /usr/local/cpanel/3rdparty/bin/freshclam cron. We have changed the time for this cron job so you will not receive some part of it daily. This is the message from the system so it can not be stopped so you can ignore it.
​

I don't know what they've done, but I am continuing to get this daily cron message. Is there anything I can do to stop it? It will drive me crazy!

Hope someone can advise.

Myles

 

[cPanelMichael]

Hello Myles,

/etc/cron.daily/freshclam:
WARNING: Ignoring deprecated option AllowSupplementaryGroups at line 60

The /etc/cron.daily/freshclam cron job isn't setup by default. Can you let us know the contents of that file on your system?

Thank you.

 

[magicalwonders]

Hi Michael,

It's not a big file, so I'll copy it here, rather than upload an attachment. This is the freshclam file in /etc/cron.daily/

#!/bin/sh

### A simple update script for the clamav virus database.
### This could as well be replaced by a SysV script.

### fix log file if needed
LOG_FILE="/var/log/clamav/freshclam.log"
if [ ! -f "$LOG_FILE" ]; then
touch "$LOG_FILE"
chmod 644 "$LOG_FILE"
chown clamav.clamav "$LOG_FILE"
fi

/usr/bin/freshclam \
--quiet \
--datadir="/var/lib/clamav" \
--log="$LOG_FILE" \
--daemon-notify="/usr/local/cpanel/3rdparty/etc/clamd.conf"​

 

[cPanelMichael]

Hello @magicalwonders,

It looks like that cron job is making use of /usr/bin/freshclam. You may want to verify that alternate versions of ClamAV are not installed on your system. The version of freshclam offered through cPanel & WHM is located at:

/usr/local/cpanel/3rdparty/bin/freshclam

Thank you.

 

[magicalwonders]

I can see that a freshclam file is located at /usr/local/cpanel/3rdparty/bin/freshclam

Should that be referenced in the daily cron instead of the one at /usr/bin/freshclam \ ?

I've attached a copy of it as a text doc. It looks a bit weird, so not sure if it's meant to look this way?

 

[cPanelMichael]

Hello @magicalwonders,

There's also a reference to /var/lib/clamav/ which is not a directory utilized for the instance of ClamAV provided through cPanel & WHM. Are you using that cron job for a specific purpose? If not, you may want to consider removing it and then removing any third-party installations of ClamAV. Note there's already a freshclam cron job that is setup automatically as part of the root crontab. EX:

# crontab -l|grep freshclam
49 22 * * * /usr/local/cpanel/3rdparty/bin/freshclam --quiet --no-warnings

Thank you.

 

[magicalwonders]

I'm not sure how that cron job came to be created. I'll ask my host to remove it, along with any third-party install of ClamAV.

Thanks for the advice.

 

[magicalwonders]

Ok, I've asked my host to remove the cron job and third party ClamAV. I also referred them to this thread. I've received this response -

The freshclam is default clamv version but as you don't wish to run it daily, we have set it to run it on Sunday. Please let us know if you find any problem

They also included this -

[email protected] [~]# /usr/local/cpanel/3rdparty/bin/freshclam
ClamAV update process started at Wed Jul 18 11:07:26 2018
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.99.4 Recommended version: 0.100.1
DON'T PANIC! Read http://www.clamav.net/documents/upgrading-clamav
main.cld is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
daily.cld is up to date (version: 24760, sigs: 2015700, f-level: 63, builder: neo)
bytecode.cld is up to date (version: 324, sigs: 89, f-level: 63, builder: neo)

It looks like they've ignored my request and updated the third-party ClamAv?

I assume ClamAv installed with cPanel is automatically kept up to date, and probably not a good idea to have two installs of ClamAV running at the same time?

 

[cPanelMichael]

Hello @magicalwonders,

That's correct. Let them know the root of the issue is the installation of multiple instances of ClamAV. ClamAV documents the uninstall instructions at the URL below:

https://www.clamav.net/documents/uninstalling-clamav

Uninstalling the additional instance of ClamAV should solve the issue. If you'd like to verify if the additional instance was installed as an RPM, run the following command via SSH as root:

rpm -qa|grep clam

The output should resemble the following:

# rpm -qa|grep clam
cpanel-clamav-virusdefs-0.100.0-1.cp1170.x86_64
cpanel-clamav-0.100.0-1.cp1170.x86_64

If you see additional ClamAV RPMs, you can remove them using the following command:

yum remove clamav*

Thank you.

 

[magicalwonders]

The output after running

rpm -qa|grep clam

is as follows -

[email protected] [~]# rpm -qa|grep clam
clamav-db-0.100.0-1.el6.x86_64
cpanel-clamav-0.99.4-3.cp1170.x86_64
clamav-0.100.0-1.el6.x86_64
cpanel-clamav-virusdefs-0.99.4-3.cp1170.x86_64

If I run

yum remove clamav*

on the command line, that will remove the third-party ClamAV and leave the cPanel ClamAV intact, yes?

Presumably I then just need to remove the cron job my host created, for the the third-party ClamAV.

 

[cPanelMichael]

on the command line, that will remove the third-party ClamAV and leave the cPanel ClamAV intact, yes?

Presumably I then just need to remove the cron job my host created, for the the third-party ClamAV.

Hello @magicalwonders,

That's correct. The "yum remove" command should automatically remove the cron job as well, but if it doesn't then manually removing it is the correct step to take.

Thank you.