Skip to main content

YUM encountered errors outside of EasyApache 4

Comments

9 comments

  • andrew.n
    looks like a temporary problem with Immunify repo. Can you run "yum clean all" then try it again?
    0
  • Arman.Motevalian
    looks like a temporary problem with Immunify repo. Can you run "yum clean all" then try it again?

    Hi, the problem is not solved. Shows the same error again
    0
  • andrew.n
    What is the output of yum clean all command? do you have a firewall on the server? If so can you turn it off and try it again?
    0
  • cPRex Jurassic Moderator
    Is your system properly licensed with either CloudLinux or Imunify? That can also cause these issues. If you aren't sure, you're always welcome to submit a ticket to our team and we can check the license status on our end.
    0
  • Arman.Motevalian
    looks like a temporary problem with Immunify repo. Can you run "yum clean all" then try it again?

    [root@panel ~]# yum clean all Loaded plugins: fastestmirror, langpacks, universal-hooks Cleaning repos: EA4 cpanel-plugins base extras imunify360 : imunify360-ea-php-hardened imunify360-rollout-1 : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 : letsencrypt-cpanel mysql-connectors-community : mysql-tools-community mysql57-community updates Cleaning up list of fastest mirrors Other repos take up 580 k of disk space (use --verbose for details)
    0
  • Arman.Motevalian
    Is your system properly licensed with either CloudLinux or Imunify? That can also cause these issues. If you aren't sure, you're always welcome to submit a ticket to our team and we can check the license status on our end.

    Yes, there is no problem with the license. i dont have cloud linux . i have only imunify.
    0
  • cPRex Jurassic Moderator
    That output looks normal to me. The only other thing I would try before submitting a ticket would be to ensure you can reach the URL of the repository from your server. You can try a test using the "wget" command to see if you can download the files properly to your system. You may also want to try replacing the contents of /etc/resolv.conf with the Google public resolvers, to ensure your machine can properly resolve all domain names. Here is what that file should look like if you'd like to try that test: nameserver 8.8.8.8 nameserver 8.8.4.4
    0
  • Arman.Motevalian
    Cloud Linux site support guided me to use the following method to solve the problem: Please remove the culprit repo: rm /etc/yum.repos.d/imunify360-ea-php-hardened.repo
    or disable it: yum-config-manager --disable imunify360-ea-php-hardened
    yum clean all
    and re-check. After that
    0
  • kodeslogic
    Glad to see you were able to fix that. Thanks for sharing the information.
    0

Please sign in to leave a comment.