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!

check_cpanel_rpms - p0f Missing

Discussion in 'General Discussion' started by izghitu, Sep 16, 2016.

Tags:
  1. tommyxv

    tommyxv Member

    Joined:
    Jun 15, 2006
    Messages:
    15
    Likes Received:
    4
    Trophy Points:
    153
    I'll be the test dummy and try the cPanel method. :) If the problem comes back again, then I'll go back to @Chris Rose's solution.
     
  2. rpvw

    rpvw Well-Known Member

    Joined:
    Jul 18, 2013
    Messages:
    1,088
    Likes Received:
    442
    Trophy Points:
    113
    Location:
    Spain
    cPanel Access Level:
    Root Administrator
    Is it worth considering the implications of using an 'exclude' for one or more packages (which leaves epel with the potential to overwrite loads of packages, even though they may not cause issues now - perhaps they might at some future time) ..... or 'includes 'to JUST update specific packages from the epel repo ?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. caroseuk

    caroseuk Member

    Joined:
    Aug 4, 2015
    Messages:
    24
    Likes Received:
    5
    Trophy Points:
    3
    Location:
    United kingdom
    cPanel Access Level:
    Root Administrator
    I agree, this is just a short term fix.

    Ideally you would only include the updates for packages you have installed from EPEL.

    So for me "blacklisting" everything apart from redis/fail2ban would suit me.

    Perhaps it could be something cPanel/WHM could build into the control panel to manage better than command line? (Just an idea) though it's a conflict issue with repos and not really cPanels fault.

    I'll shut up now.
     
  4. Infopro

    Infopro cPanel Sr. Product Evangelist Staff Member

    Joined:
    May 20, 2003
    Messages:
    16,909
    Likes Received:
    484
    Trophy Points:
    583
    Location:
    Pennsylvania
    cPanel Access Level:
    Root Administrator
    Twitter:
    There is a case open to properly address this issue, as mentioned in the quote above:

     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. rpvw

    rpvw Well-Known Member

    Joined:
    Jul 18, 2013
    Messages:
    1,088
    Likes Received:
    442
    Trophy Points:
    113
    Location:
    Spain
    cPanel Access Level:
    Root Administrator
    In that case, I would have thought that the line (in the epel.repo file)
    Code:
    includepkgs=redis fail2ban
    would have done the trick. That should ONLY update redis and fail2ban from the epel repo AND NOTHING ELSE
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. izghitu

    izghitu Well-Known Member

    Joined:
    Aug 9, 2006
    Messages:
    52
    Likes Received:
    1
    Trophy Points:
    158
    Thanks guys, it solved my problem
     
  7. caroseuk

    caroseuk Member

    Joined:
    Aug 4, 2015
    Messages:
    24
    Likes Received:
    5
    Trophy Points:
    3
    Location:
    United kingdom
    cPanel Access Level:
    Root Administrator
    Correct, it solves it for my case. However for other users facing the same issue then it needs to be addressed.

    Otherwise cPanel Users need to disable the EPEL repo. Which isn't really an option depending on each users case and their circumstances.

    Anyway, cPanel have spoken and it seems it's a known issue and is being addressed.
     
  8. Ed Bergavera

    Ed Bergavera Member

    Joined:
    Sep 16, 2016
    Messages:
    6
    Likes Received:
    5
    Trophy Points:
    3
    Location:
    Panabo City, Philippines
    cPanel Access Level:
    Root Administrator
    I ran into an issue like this on CentOS 7 WHM 11.58 build 28. The command as suggested by Travis went all good.
     
  9. caroseuk

    caroseuk Member

    Joined:
    Aug 4, 2015
    Messages:
    24
    Likes Received:
    5
    Trophy Points:
    3
    Location:
    United kingdom
    cPanel Access Level:
    Root Administrator
    Simply running that command will only fix the issue until the next time the cPanel Update job runs (~24 hours). At which time, it will remove the rpm again and replace it with the one in the EPEL repo.

    You need to tell the EPEL repo to not update the p0f rpm that cPanel provides.

    In Centos 7, I edited the /etc/yum.repos.d/epel.repo and within the enabled block I added:
    exclude=p0f*.el7.*

    So the complete block looks like:

    [epel]
    name=Extra Packages for Enterprise Linux 7 - $basearch
    failovermethod=priority
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
    enabled=1
    disabled=True
    mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch
    gpgcheck=1
    exclude=p0f*.el7.*
    #baseurl=http://download.fedoraproject.org/pub/epel/7/$basearch

    I then save and re run the following script:
    /usr/local/cpanel/scripts/check_cpanel_rpms --fix command

    Then, next time the cPanel Update scripts run, it will not get overwritten/removed.
     
    Dradden45 likes this.
  10. cPanelMichael

    cPanelMichael Technical Support Community Manager Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    47,331
    Likes Received:
    2,161
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello,

    To update, internal case CPANEL-8634 will address this issue in cPanel version 60 by ensuring the EPEL repository is disabled when invoking YUM from within cPanel. Note that EPEL is currently not a supported repository, and can cause unforeseen issues when enabled.

    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. tommyxv

    tommyxv Member

    Joined:
    Jun 15, 2006
    Messages:
    15
    Likes Received:
    4
    Trophy Points:
    153
    I can confirm that this method also works too. No errors this morning like the last few days.

    Thanks again.
     
  12. cPanelMichael

    cPanelMichael Technical Support Community Manager Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    47,331
    Likes Received:
    2,161
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Twitter:
    We're also including CPANEL-8634 with cPanel version 58. A new build is tentatively scheduled for publication today, and I'll update this thread once it's released.

    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. twhiting9275

    twhiting9275 Well-Known Member

    Joined:
    Sep 26, 2002
    Messages:
    556
    Likes Received:
    16
    Trophy Points:
    168
    cPanel Access Level:
    Root Administrator
    Twitter:
    EPEL is a very valid repository. Instead of trying to discredit them and blame them, perhaps you should be fixing the core issue here... There are conflicts between the two versions and they should be resolved, not just blamed on someone else.

    I understand it's easier to blame someone else for your conflicts, but, that's about as unprofessional as it gets.

    I've been dealing with EPEL for years now. There are absolutely no 'unforeseen issues', except with your software. Seems the problem isn't with EPEL, but with your software version.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. cPanelMichael

    cPanelMichael Technical Support Community Manager Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    47,331
    Likes Received:
    2,161
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello @twhiting9275,

    Thank you for the valued feedback. To clarify, the resolution associated with CPANEL-8634 won't permanently disable the EPEL YUM repo on a server. Instead, the change will only temporarily disable the EPEL repo when invoking YUM from within cPanel. This addresses the issue, while also allowing for the continued use of the custom repo. There's also discussion in this case of officially supporting EPEL, but that's not something we'd be able to implement right away due to the testing required to determine all of the existing incompatibilities.

    Currently, the issue is addressed in cPanel version 59 (development build for cPanel version 60):

    Fixed case CPANEL-8634: Perform cPanel YUM calls with EPEL disabled.

    I'll update this thread again once the resolution is published to cPanel version 58.

    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. Tsafarog

    Tsafarog Member

    Joined:
    Oct 23, 2009
    Messages:
    15
    Likes Received:
    1
    Trophy Points:
    53
    So any news on the release?
     
  16. cPanelMichael

    cPanelMichael Technical Support Community Manager Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    47,331
    Likes Received:
    2,161
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello,

    Yes, the resolution was published to cPanel version 58.0.31 about an hour ago:

    Fixed case CPANEL-8756: Perform cPanel YUM calls with EPEL disabled.

    58.0.31 is tentatively scheduled for publication to the "RELEASE" build tier on Monday.

    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. Morphis

    Morphis Registered

    Joined:
    Sep 25, 2016
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Australia
    cPanel Access Level:
    Root Administrator

    This fix it !!

    Beens bugging me for a few weeks now.

    Thanks
     
  18. tommyxv

    tommyxv Member

    Joined:
    Jun 15, 2006
    Messages:
    15
    Likes Received:
    4
    Trophy Points:
    153
    Just updated to 58.0.31.

    Do I need to undo this previous fix now?

     
  19. cPanelMichael

    cPanelMichael Technical Support Community Manager Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    47,331
    Likes Received:
    2,161
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Twitter:
    Yes, you should revert that manual workaround, as it's no longer required once you system is using cPanel version 58.0.31 or newer.

    58.0.31 is now available on the "RELEASE" build tier.

    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    tommyxv likes this.
  20. tommyxv

    tommyxv Member

    Joined:
    Jun 15, 2006
    Messages:
    15
    Likes Received:
    4
    Trophy Points:
    153
    Cool. Thanks!
     
    cPanelMichael likes this.
Loading...

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.
    Dismiss Notice