Skip to main content

ea-wappspector info/warning

Comments

14 comments

  • cPRex Jurassic Moderator

    Hey there!  I'm not seeing this on my personal AlmaLinux 8 system when I checked just now.

    If you run:

    rpm -qa | grep -i wappspector

    do you see any results for that package on your system?

    0
  • verdon

    yes, I do...

    [root@host2 verdon]# rpm -qa | grep -i wappspector
    ea-wappspector-0.2.8-1.3.1.cpanel.x86_64
    OS - AlmaLinux v8.10.0 STANDARD standard
    cPanel Version - 130.0.14
     
     
    0
  • verdon

    oh, in case it matters, I did install Imunify360 yesterday and am trialing it.

    0
  • cPRex Jurassic Moderator

    That command's output would indicate it is installed.  If you can't remove it through the interface you can do it manually with this command:

    rpm -e --nodeps ea-wappspector

    Can you try that and see if that takes care of the warning in Security Advisor?

    0
  • verdon

    Should I check with Immunity to see if its what installed it?

    0
  • cPRex Jurassic Moderator

    Let me look into this and I'll let you know once I have more details.

    1
  • cPRex Jurassic Moderator

    tl;dr - you can ignore this warning for now as it should be fixed later this week.

    I had never heard of this package until this thread, which makes sense as we just released this last week:

    https://docs.cpanel.net/changelogs/easyapache-4-change-log-25/

    You'll note there that it is now a dependency, so cPanel will attempt to reinstall this if it is missing.

    It would seem the Security Advisor tool just wasn't aware of this new package so it was giving that false-positive message bout you needing to remove it.

    At this time, you can just ignore the warning as the team is planning a fix that will take care of it later this week, and after that you will no longer receive that message about the ELevate conflict.

    Let me know if that helps!

    1
  • verdon

    A big help. Thank you. I love a mystery in a novel, not on a server 😂

    0
  • cPRex Jurassic Moderator

    You're very welcome!

    0
  • mtindor

    Similar thing here.  CloudLinux 9.   During nightly update I get:

    [2025-10-16 03:32:13 -0400]      [/usr/local/cpanel/scripts/update-packages] This system is receiving updates from CloudLinux Network server.
    [2025-10-16 03:32:13 -0400]      [/usr/local/cpanel/scripts/update-packages] Last metadata expiration check: 0:32:16 ago on Thu Oct 16 02:59:56 2025.
    [2025-10-16 03:32:13 -0400]      [/usr/local/cpanel/scripts/update-packages] Error: 
    [2025-10-16 03:32:13 -0400]      [/usr/local/cpanel/scripts/update-packages]  Problem: cannot install the best update candidate for package ea-cpanel-tools-1:1.0-112.el9.cloudlinux.x86_64
    [2025-10-16 03:32:13 -0400]      [/usr/local/cpanel/scripts/update-packages]   - nothing provides ea-wappspector needed by ea-cpanel-tools-1:1.0-113.el9.cloudlinux.x86_64 from cloudlinux-ea4-rollout-13
    [2025-10-16 03:32:13 -0400]      [/usr/local/cpanel/scripts/update-packages] (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
    [2025-10-16 03:32:13 -0400]      [/usr/local/cpanel/scripts/update-packages] (XID p2fz56) “/usr/bin/yum†reported error code “1†when it ended: 
    [2025-10-16 03:32:13 -0400] E    [/usr/local/cpanel/scripts/update-packages] The “/usr/local/cpanel/scripts/update-packages†command (process 1038685) reported error number 1 when it ended.
    [2025-10-16 03:32:13 -0400]   The Administrator will be notified to review this output when this script completes

    dnf clean all; dnf make cache; dnf update:

    Error: 
     Problem: cannot install the best update candidate for package ea-cpanel-tools-1:1.0-112.el9.cloudlinux.x86_64
      - nothing provides ea-wappspector needed by ea-cpanel-tools-1:1.0-113.el9.cloudlinux.x86_64 from cl-ea4
    (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

    0
  • cPRex Jurassic Moderator

    mtindor - since we just released that package I doubt it's made it to the CloudLinux repositories yet.  I did let the team know about this just now so we can double-check that, but for now you can just ignore that error.

    1
  • mtindor

    I just heard back from CL and they said it was in their repos and asked me to check if it would update now.   dnf clean all; dnf makecache; dnf update was ran and it still didn't find it.  I reported that back to CL.   I'm probably accessing a repo mirror that has not yet been updated with the package.

    M

    0
  • indianets

    The problem still exists after 1 month of this and CloudLinux support is suggesting enabling EA4-cl9 repo instead of  making ea-wappspector available in their repo cl-ea4.

    I asked them "Do you mean the package ea-wappspector is not available in cl-ea4 repo?" and they replied with "The ea-wappspector package is available through the EA4-c9 repo. So you can safely enable the repo and update the system."

    Anyways, support seems to have downgraded from the last time I had to contact them a year or more ago. I have installed only ea-wappspector package from EA4-c9 repo as a wordkaround for now.

    yum install ea-wappspector --enablerepo=EA4-c9

    Running yum update after this won't report missing dependency.

    0
  • Daniel Muey

    CloudLinux started pushing out the updated pkgs on Dec 24th so it was probably good by Dec 31/Jan 7 👍

    1

Please sign in to leave a comment.