Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

Ignoring deprecated option AllowSupplementaryGroups error

Discussion in 'General Discussion' started by magicalwonders, Jul 17, 2018.

Tags:
  1. magicalwonders

    magicalwonders Well-Known Member

    Joined:
    Nov 21, 2012
    Messages:
    106
    Likes Received:
    2
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    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
     
    #1 magicalwonders, Jul 17, 2018
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    44,344
    Likes Received:
    1,852
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello Myles,

    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.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    #2 cPanelMichael, Jul 17, 2018
  3. magicalwonders

    magicalwonders Well-Known Member

    Joined:
    Nov 21, 2012
    Messages:
    106
    Likes Received:
    2
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    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"​
     
    #3 magicalwonders, Jul 17, 2018
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    44,344
    Likes Received:
    1,852
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    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:

    Code:
    /usr/local/cpanel/3rdparty/bin/freshclam
    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    #4 cPanelMichael, Jul 17, 2018
  5. magicalwonders

    magicalwonders Well-Known Member

    Joined:
    Nov 21, 2012
    Messages:
    106
    Likes Received:
    2
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    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?
     
    #5 magicalwonders, Jul 17, 2018
  6. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    44,344
    Likes Received:
    1,852
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    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:

    Code:
    # crontab -l|grep freshclam
49 22 * * * /usr/local/cpanel/3rdparty/bin/freshclam --quiet --no-warnings
    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    #6 cPanelMichael, Jul 17, 2018
  7. magicalwonders

    magicalwonders Well-Known Member

    Joined:
    Nov 21, 2012
    Messages:
    106
    Likes Received:
    2
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    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.
     
    #7 magicalwonders, Jul 17, 2018
    cPanelMichael likes this.
  8. magicalwonders

    magicalwonders Well-Known Member

    Joined:
    Nov 21, 2012
    Messages:
    106
    Likes Received:
    2
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    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 -

    They also included this -
    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?
     
    #8 magicalwonders, Jul 18, 2018
  9. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    44,344
    Likes Received:
    1,852
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    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:

    Code:
    rpm -qa|grep clam
    The output should resemble the following:

    Code:
    # 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:

    Code:
    yum remove clamav*
    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    #9 cPanelMichael, Jul 18, 2018
  10. magicalwonders

    magicalwonders Well-Known Member

    Joined:
    Nov 21, 2012
    Messages:
    106
    Likes Received:
    2
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    The output after running
    Code:
    rpm -qa|grep clam
    is as follows -
    If I run
    Code:
    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.
     
    #10 magicalwonders, Jul 18, 2018
  11. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    44,344
    Likes Received:
    1,852
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    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.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    #11 cPanelMichael, Jul 18, 2018
    magicalwonders likes this.
(You must log in or sign up to post here.)
Loading...
Similar Threads - Ignoring deprecated option
  1. _jman

    SOLVED PHP ignoring modified document root

    _jman, Aug 1, 2018, in forum: EasyApache
    Replies:
    3
    Views:
    72
    cPanelMichael
    Aug 15, 2018 at 9:38 AM
  2. webicom

    SOLVED error: Ignoring alt-phpxx-newrelic-daemon because of bad file mode - must be 0644 or 0444.

    webicom, Jul 4, 2018, in forum: General Discussion
    Replies:
    8
    Views:
    582
    cPanelLauren
    Jul 6, 2018
  3. mikefromnz

    EXIM And Smart Host ignoring mail queue rules?

    mikefromnz, Dec 6, 2017, in forum: E-mail Discussion
    Replies:
    3
    Views:
    313
    cPanelMichael
    Dec 8, 2017
  4. Dedan Irungu

    SOLVED Mysql is ignoring /etc/my.cnf setting

    Dedan Irungu, Oct 19, 2017, in forum: Database Discussion
    Replies:
    5
    Views:
    1,097
    cPWilliamL
    Oct 19, 2017
  5. Spencer Marsden

    SOLVED useraccount/logs/website.php.error.log ignoring php.ini settings

    Spencer Marsden, Apr 21, 2017, in forum: EasyApache
    Replies:
    4
    Views:
    804
    Spencer Marsden
    Apr 21, 2017

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...
    Dismiss Notice