error update

chanklish

• March 25, 2022 04:58

hello everyone is anyone facing this update issue ? if yes how did you solve it ? The system cannot check the kernel status: "/usr/bin/yum" reported error code "1" when it ended: yum-errors - CentOS Wiki If above article doesn't help to resolve this issue please use

• 

  cPanelWilliam

  • March 25, 2022 12:47

  Hey there! Could you check the contents of the /etc/yum.repos.d/wp-toolkit-cpanel.repo file? We've had a few reports of this issue within our ticket system. In these tickets, we were able to resolve the issue by changing the baseurl entries in /etc/yum.repos.d/wp-toolkit-cpanel.repo. Here's what the baseurl entries in the file should look like for CentOS 7: grep baseurl /etc/yum.repos.d/wp-toolkit-cpanel.repo baseurl=https://wp-toolkit.plesk.com/cPanel/wp-toolkit/ baseurl=https://wp-toolkit.plesk.com/cPanel/dist-rpm-CentOS-7-x86_64/
  In the tickets we've seen the entries looked like this instead: # grep baseurl /etc/yum.repos.d/wp-toolkit-cpanel.repo.orig | grep toolkit baseurl=https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/ baseurl=https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/
  If the baseurl entries do not match the first pair I provided, I would suggest making a backup of the /etc/yum.repos.d/wp-toolkit-cpanel.repo file and updating them to match, then running another update at your earliest convenience to see if the issue is resolved.

  0
• 

  Mr.Malmgren

  • March 27, 2022 08:08

  Thanks! This solved our problem with Cloudlinux 8. cat /etc/yum.repos.d/wp-toolkit-cpanel.repo [wp-toolkit-cpanel] name=WordPress Toolkit for cPanel baseurl=https://wp-toolkit.plesk.com/cPanel/wp-toolkit/ enabled=1 gpgcheck=1 [wp-toolkit-thirdparties] name=WordPress Toolkit third parties baseurl=https://wp-toolkit.plesk.com/cPanel/dist-rpm-CentOS-8-x86_64/ enabled=1 gpgcheck=1
  

  0
• 

  cPRex Jurassic Moderator

  • March 29, 2022 19:12

  I'm glad things are working well. WordPress Toolkit released a fix for this as part of yesterday's update so this should be permanently resolved now.

  0

Please sign in to leave a comment.