Skip to main content

Last cPanel & WHM update attempt blocked. Details

Comments

13 comments

  • cPRex Jurassic Moderator
    Hey there! When this message appears, it's best to try a "yum update" on the system to make sure the operating system itself is also updated to the latest version. That will download and install all necessary packages, and unless there are errors, should resolve that message and allow you to update cPanel. Can you try that and let me know your results?
    0
  • oksijensizsolunum
    Evet, tabii ki ?imdi yap?yorum
    0
  • oksijensizsolunum
    Hey there! When this message appears, it's best to try a "yum update" on the system to make sure the operating system itself is also updated to the latest version. That will download and install all necessary packages, and unless there are errors, should resolve that message and allow you to update cPanel. Can you try that and let me know your results?

    I have done the update process but I cannot get an update in the same way. Already my server was getting almost 1 year of continuous updates, the last time this error came out
    0
  • cPRex Jurassic Moderator
    Do you get any additional errors when you run the "yum update" command on the system? If that isn't working properly, the cPanel updates won't work either.
    0
  • oksijensizsolunum
    Do you get any additional errors when you run the "yum update" command on the system? If that isn't working properly, the cPanel updates won't work either.

    It ends like this after the yum is over ---> Package yum.noarch 0:3.4.3-168.el7.cloudlinux will be an update --> Processing Conflict: iproute-4.11.0-30.el7.cloudlinux.x86_64 conflicts kernel < 3.10.0-793.21.1.lve1.5.20 --> Finished Dependency Resolution Error: iproute conflicts with kernel-3.10.0-327.el7.x86_64 You could try using --skip-broken to work around the problem ** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows: mod_fcgid-2.3.9-6.el7.x86_64 has missing requires of httpd-mmn = ('0', '20120211x8664', None) [root@server ~]# ^C
    0
  • cPRex Jurassic Moderator
    Thanks for the additional details. There is a recent issue with CloudLinux and the iproute package. Can you try the workarounds mentioned in this thread and let me know if that fixes things for you?
    0
  • oksijensizsolunum
    iproute * is add but didn't work again eroor continues
    0
  • cPRex Jurassic Moderator
    Are you seeing the exact same error after editing the Yum configuration or has the error changed?
    0
  • oksijensizsolunum
    error the same hasn't changed
    0
  • cPRex Jurassic Moderator
    Inside /etc/yum.conf you'll want to add the "iproute*" value to the end of the exclude line, so that will be one long line in the file. After that, you can run the following: yum clean all yum makecache yum update
    Can you try all that and let me know if you still get the same result?
    0
  • oksijensizsolunum
    I did it but it didn't work
    0
  • oksijensizsolunum
    Inside /etc/yum.conf you'll want to add the "iproute*" value to the end of the exclude line, so that will be one long line in the file. After that, you can run the following: yum clean all yum makecache yum update
    Can you try all that and let me know if you still get the same result?

    .
    0
  • vacancy
    yum -y remove mod_fcgid
    Then run the update and restart the server.
    0

Please sign in to leave a comment.