Skip to main content

cPanel & WHM update failure in upcp script

Comments

21 comments

  • cPRex Jurassic Moderator
    Hey there! If you manually run "/scripts/findphpversion" what output do you receive?
    0
  • garconcn
    Hey there! If you manually run "/scripts/findphpversion" what output do you receive?

    [QUOTE] # /scripts/findphpversion PHP version file has been updated to 7.0.33
    0
  • cPRex Jurassic Moderator
    That seems like normal output from that script. Can you try running "/script/upcp --force" again and see if you get the same error?
    0
  • garconcn
    I don't see any error after run "/scripts/upcp --force". Why multiple servers show the same error in last Maintenance? Is there an issue on our server or cpanel side? Just curious, does cpanel receive a copy of the update failure log for analysis? If not, I suggest you consider that(not the whole log file, but at least the error part). We can only see the error from our own servers, but cpanel can see from all. It will be easier for cpanel to conclude whether the issue is sole case or affect everyone.
    0
  • cPRex Jurassic Moderator
    I haven't seen any reports of multiple machines experiencing the same error. Is it the exact same error across all the servers?
    0
  • garconcn
    Not on all servers, I received this error on 12 servers, they run on different OS(cloudlinux 6, 7 and CentOS 7).
    0
  • cPRex Jurassic Moderator
    That's odd - could you submit a ticket to our team so we can check that out? We wouldn't need access to all twelve machines, but maybe one or two would be enough to get some useful details.
    0
  • sHORTYWZ
    I am receiving this same error on my CloudLinux v6.10.0 server.. when I run /scripts/findphpversion I am getting: "/usr/local/cpanel/bin/python-packman" reported error code "1" when it ended: Traceback (most recent call last): File "/usr/local/cpanel/bin/packman_get_info_json", line 16, in packman.init_yum() File "/usr/local/cpanel/bin/packman_lib/yum_impl.py", line 78, in init_yum yb.repos.populateSack() File "/usr/lib/python2.6/site-packages/yum/repos.py", line 324, in populateSack sack.populate(repo, mdtype, callback, cacheonly) File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 165, in populate if self._check_db_version(repo, mydbtype): File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 223, in _check_db_version return repo._check_db_version(mdtype) File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 1263, in _check_db_version repoXML = self.repoXML File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 1462, in repoXML = property(fget=lambda self: self._getRepoXML(), File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 1458, in _getRepoXML raise Errors.RepoError, msg yum.Errors.RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: wp-toolkit-cpanel. Please verify its path and try again w/ /usr/local/cpanel/bin/packman_get_info_json ea-php74 Often errors like this can be resolved by running `yum makecache`
    Running yum makecache did not help, nor did running an upcp --force (same error).
    0
  • cPRex Jurassic Moderator
    @sHORTYWZ - before you ran "yum makecache" did you run "yum clean all"?
    0
  • sHORTYWZ
    @sHORTYWZ - before you ran "yum makecache" did you run "yum clean all"?

    Just did, output of makecache following clean all: https://wp-toolkit.plesk.com/cPanel/CentOS-6-x86_64/5.11.2/wp-toolkit/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found" Trying other mirror. To address this issue please refer to the below knowledge base article https://access.redhat.com/articles/1320623 If above article doesn't help to resolve this issue please open a ticket with CloudLinux Support. Error: Cannot retrieve repository metadata (repomd.xml) for repository: wp-toolkit-cpanel. Please verify its path and try again
    0
  • cPRex Jurassic Moderator
    That's interesting - the first thing I would try would be to disable the WordPress Toolkit repository: yum-config-manager --disable wp-toolkit-cpanel
    and then try the update again with this: yum clean all yum makecache yum update
    If that doesn't work that could indicate deeper issues with the RPM system. If there are still errors you can try the WHM >> Rebuild RPM Database tool.
    0
  • sHORTYWZ
    That's interesting - the first thing I would try would be to disable the WordPress Toolkit repository: yum-config-manager --disable wp-toolkit-cpanel
    and then try the update again with this: yum clean all yum makecache yum update
    If that doesn't work that could indicate deeper issues with the RPM system. If there are still errors you can try the WHM >> Rebuild RPM Database tool.

    Had to disable one more repo, and we're back in business now: yum-config-manager --disable wp-toolkit-thirdparties
    0
  • cPRex Jurassic Moderator
    I'm glad that worked - I'd still expect those repositories to work though, so it might be worth checking their contents. Here's the output of my wp-toolkit-cpanel file: [wp-toolkit-cpanel] name=WordPress Toolkit for cPanel baseurl=https://wp-toolkit.plesk.com/cPanel/CentOS-8-x86_64/5.11.2/wp-toolkit/ enabled=1 gpgcheck=1 [wp-toolkit-thirdparties] name=WordPress Toolkit third parties baseurl=https://wp-toolkit.plesk.com/cPanel/CentOS-8-x86_64/5.11.2/thirdparty/ enabled=1 gpgcheck=1
    0
  • sHORTYWZ
    I'm glad that worked - I'd still expect those repositories to work though, so it might be worth checking their contents. Here's the output of my wp-toolkit-cpanel file: [wp-toolkit-cpanel] name=WordPress Toolkit for cPanel baseurl=https://wp-toolkit.plesk.com/cPanel/CentOS-8-x86_64/5.11.2/wp-toolkit/ enabled=1 gpgcheck=1 [wp-toolkit-thirdparties] name=WordPress Toolkit third parties baseurl=https://wp-toolkit.plesk.com/cPanel/CentOS-8-x86_64/5.11.2/thirdparty/ enabled=1 gpgcheck=1

    Your repo is set up with CentOS-8-x86_64, whereas mine (CloudLinux6) is CentOS-6-x86_64 - it looks like this repo stops at version 5.10 (which makes sense, as there is a deprecation notice in the WP Toolkit plugin), but it seems a code change needs to happen on the cPanel side to stop looking for newer versions of the yum repo.
    0
  • cPRex Jurassic Moderator
    Oh, I wouldn't expect anything to work unless you have the extended support option through CloudLinux. You'll likely continue to run into repo issues if that is the case:
    0
  • sHORTYWZ
    Oh, I wouldn't expect anything to work unless you have the extended support option through CloudLinux. You'll likely continue to run into repo issues if that is the case:
    0
  • cPRex Jurassic Moderator
    I reached out to our developers and Plesk is not currently building a newer version, as they manage that repository, except for critical security updates as mentioned in that notification in the interface. In order to suppress the warning messages you can enable the repositories but change the URL to use the "latest" version, instead of the specific version that it's trying to update to:
    0
  • sHORTYWZ
    I reached out to our developers and Plesk is not currently building a newer version, as they manage that repository, except for critical security updates as mentioned in that notification in the interface. In order to suppress the warning messages you can enable the repositories but change the URL to use the "latest" version, instead of the specific version that it's trying to update to:
    0
  • cPRex Jurassic Moderator
    You're welcome!
    0
  • SoundInTheory
    Hi, I've got exactly the same problem as Garconcn: ... [2022-07-19 00:39:56 +0100] E [/usr/local/cpanel/scripts/findphpversion] "/usr/local/cpanel/bin/python-packman" reported error code "1" when it ended: Traceback (most recent call last): [2022-07-19 00:39:56 +0100] E [/usr/local/cpanel/scripts/findphpversion] File "/usr/local/cpanel/bin/packman_get_info_json", line 16, in [2022-07-19 00:39:56 +0100] E [/usr/local/cpanel/scripts/findphpversion] packman.init_yum() [2022-07-19 00:39:56 +0100] E [/usr/local/cpanel/scripts/findphpversion] File "/usr/local/cpanel/bin/packman_lib/yum_impl.py", line 78, in init_yum ... If I run: /scripts/findphpversion PHP version file has been updated to 7.4.30 # yum clean all then # yum makecache Gives me an error: ... (57/58): wp-toolkit-thirdparties/filelists_db | 3.9 kB 00:00:00 extras/7/x86_64/other_db FAILED
    0
  • cPRex Jurassic Moderator
    Could you open a ticket with our support team so we can look at this? I can't reproduce this on a test machine, but if multiple people are experiencing similar behavior there could be something going on we need to check.
    0

Please sign in to leave a comment.