Skip to main content

Ignoring deprecated option AllowSupplementaryGroups error

Comments

10 comments

  • 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.
    0
  • 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"
    0
  • 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.
    0
  • 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?
    0
  • 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.
    0
  • 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.
    0
  • 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 - [QUOTE]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 - [QUOTE] root@webhost1 [~]# /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
    0
  • 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:
    0
  • magicalwonders
    The output after running rpm -qa|grep clam
    is as follows - [QUOTE] root@webhost1 [~]# 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.
    0
  • 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.
    0

Please sign in to leave a comment.