11.94.0.2 UPCP errors

Hi, Tonight UPCP had ran at it's regular daily time and the email report indicated there was an update, but had the following errors and warnings. [QUOTE][2021-03-03 00:00:10 -0800] E Blocker found: Upgrade to the next 11.94 build is blocked in order to gradually distribute upgrades over multiple days. If you wish to upgrade now, you can do so by executing "/usr/local/cpanel/scripts/upcp --force" via SSH or "WHM ? Home ? Server Configuration ? Terminal" [2021-03-03 00:00:10 -0800] W An attempt to upgrade to 11.94.0.2 was blocked. Please review blockers. [2021-03-03 00:00:10 -0800] E The install encountered a fatal error: An attempt to upgrade to 11.94.0.2 was blocked. Please review blockers. => Log closed Wed Mar 3 00:00:10 2021 [2021-03-03 00:01:09 -0800] W NOTE: A system upgrade was not possible due to the following blockers: [2021-03-03 00:01:09 -0800] W [INFO] - Upgrade to the next 11.94 build is blocked in order to gradually distribute upgrades over multiple days. If you wish to upgrade now, you can do so by executing "/usr/local/cpanel/scripts/upcp --force" via SSH or "WHM ? Home ? Server Configuration ? Terminal"
I then checked in WHM and it flagged that there was an update from 11.92.0.11 to 11.94.0.2 so I ran the update again from Home > cPanel > Upgrade to Latest Version (not forced), thinking it would either defer it or run it if all was well. It exited with error (256). I received 4 email notifications. Subject lines were: 1- PowerDNS Configuration updated. 2- The application "munin_addon" has been registered with AppConfig for the service: whostmgr 3- [abrt] yum-utils: yumRepo.py:1334:_revertOldRepoXML:OSError: [Errno 2] No such file or directory 4- cPanel & WHM update failure in upcp script The first two don't seem to be a problem. Contents of 3 and 4 are as follows. #3 email [QUOTE] reason: yumRepo.py:1334:_revertOldRepoXML:OSError: [Errno 2] No such file or directory cmdline: /usr/bin/python -tt /usr/bin/repoquery --qf %{repoid}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{name}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{version}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{release}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{arch}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{group}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{summary}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{description}<>~:;<>~:;<>~:;-1614761173-17392-pkg-<>~:;<>~:;<>~:; --whatprovides cPanel-cPAddon executable: /usr/bin/repoquery package: yum-utils-1.1.31-54.el7_8 component: yum-utils pid: 17406 hostname: *****.***********.*** count: 1 abrt_version: 2.1.11 analyzer: Python architecture: x86_64 dso_list: yum-3.4.3-168.el7.centos.noarch duphash: 064006f54b75bb9271c60312b0babdd786ec7363 event_log: kernel: 3.10.0-1160.11.1.el7.x86_64 last_occurrence: 1614761187 os_release: CentOS Linux release 7.9.2009 (Core) pkg_arch: noarch pkg_epoch: 0 pkg_fingerprint: 24C6 A8A7 F4A8 0EB5 pkg_name: yum-utils pkg_release: 54.el7_8 pkg_vendor: CentOS pkg_version: 1.1.31 runlevel: N 3 time: Wed 03 Mar 2021 12:46:27 AM PST type: Python uid: 0 username: root uuid: 064006f54b75bb9271c60312b0babdd786ec7363 backtrace: :yumRepo.py:1334:_revertOldRepoXML:OSError: [Errno 2] No such file or directory : :Traceback (most recent call last): : File "/usr/bin/repoquery", line 1547, in : main(sys.argv) : File "/usr/bin/repoquery", line 1537, in main : repoq.runQuery(regexs) : File "/usr/bin/repoquery", line 995, in runQuery : for p in self.doQuery(oper, prco): : File "/usr/bin/repoquery", line 1034, in doQuery : return getattr(self, "fmt_%s" % method)(*args, **kw) : File "/usr/bin/repoquery", line 1044, in fmt_whatprovides : return self.returnPackagesByDepStr(name) : File "/usr/bin/repoquery", line 883, in returnPackagesByDepStr : matches = yum.YumBase.searchPackageProvides(self, [str(depstring)]) : File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3469, in searchPackageProvides : where = self.returnPackagesByDep(arg) : File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 4295, in returnPackagesByDep : return self.pkgSack.searchProvides(depstring) : File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1075, in : pkgSack = property(fget=lambda self: self._getSacks(), : File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in _getSacks : self.repos.populateSack(which=repos) : File "/usr/lib/python2.7/site-packages/yum/repos.py", line 347, in populateSack : self.doSetup() : File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup : self.retrieveAllMD() : File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD : dl = repo._async and repo._commonLoadRepoXML(repo) : File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1506, in _commonLoadRepoXML : self._revertOldRepoXML() : File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1334, in _revertOldRepoXML : os.rename(old_data['old_local'>, old_data['local'>) :OSError: [Errno 2] No such file or directory : :Local variables in innermost frame: :eek:ld_data: {'old_repo_XML': , 'local': '/var/cache/yum/x86_64/7/imunify360/repomd.xml', 'new_MD_files': [], 'old_local': '/var/cache/yum/x86_64/7/imunify360/repomd.xml.old.tmp'} :self: environ: :TMP=/root/tmp :NOTIFY_SOCKET=/run/systemd/notify :TEMP=/root/tmp :USER=root :HOME=/root :PATH=/usr/local/jdk/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/X11R6/bin:/root/bin:/opt/bin machineid: :systemd=326c10d56b194e4ebe72ad7514e5a39a :sosreport_uploader-dmidecode=088fdb69987cb928a3f663e9d25ba1cce4b48d10de85218d90fcdb44188a7e8a os_info: :NAME="CentOS Linux" :VERSION="7 (Core)" :ID="centos" :ID_LIKE="rhel fedora" :VERSION_ID="7" :PRETTY_NAME="CentOS Linux 7 (Core)" :ANSI_COLOR="0;31" :CPE_NAME="cpe:/o:centos:centos:7" :HOME_URL= :BUG_REPORT_URL= : :CENTOS_MANTISBT_PROJECT="CentOS-7" :CENTOS_MANTISBT_PROJECT_VERSION="7" :REDHAT_SUPPORT_PRODUCT="centos" :REDHAT_SUPPORT_PRODUCT_VERSION="7" :
#4 email [QUOTE]

The cPanel & WHM update process failed for the following reason:

Maintenance ended; however, it did not exit cleanly (256). The following events were logged: "scripts/find_outdated_services". Review the update logs to determine why the update failed.

Update log preview:
... ... [2021-03-03 00:46:34 -0800] E [/usr/local/cpanel/scripts/find_outdated_services] STDERR: Could not parse metalink

cPRex Jurassic Moderator

March 03, 2021 19:35

Hey hey! upcp also calls the "rpmup" script as part of its maintenance, so if there were any type of RPM issues on the system at all, it would have detected those and notified you. If a subsequent run of the update didn't show any issues you're likely good to go. You could always try a manual "yum update" to see if you notice anything else out of the ordinary there, but it doesn't sound like you will from what you've said.

PeteS

March 03, 2021 20:10

Thanks! The original upcp block error, and #4 seemed definitely to be transient connection problems, but #3 I wasn't sure about. I have a kernel update to do, so a manual yum update will happen then. I just didn't want to proceed until I ran the other by here, in case there was a bug in the 11.94.0.2 update.

March 03, 2021 20:23

It's likely that 3 could have been a connection issue too, but it's always hard to say if that was related after the fact.

June 02, 2021 07:39

@cPRex FYI: after the system updated automatically to 96.0.9 I received the same error message in an email sent during the update process. Message from March (above): reason: yumRepo.py:1334:_revertOldRepoXML:OSError: [Errno 2] No such file or directory cmdline: /usr/bin/python -tt /usr/bin/repoquery --qf %{repoid}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{name}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{version}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{release}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{arch}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{group}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{summary}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{description}<>~:;<>~:;<>~:;-1614761173-17392-pkg-<>~:;<>~:;<>~:; --whatprovides cPanel-cPAddon executable: /usr/bin/repoquery package: yum-utils-1.1.31-54.el7_8 component: yum-utils pid: 17406 hostname: ************************ count: 1 abrt_version: 2.1.11 analyzer: Python architecture: x86_64 dso_list: yum-3.4.3-168.el7.centos.noarch duphash: 064006f54b75bb9271c60312b0babdd786ec7363 event_log: kernel: 3.10.0-1160.11.1.el7.x86_64 last_occurrence: 1614761187 os_release: CentOS Linux release 7.9.2009 (Core) Message from tonight: reason: yumRepo.py:1334:_revertOldRepoXML:OSError: [Errno 2] No such file or directory cmdline: /usr/bin/python -tt /usr/bin/repoquery --qf %{repoid}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{name}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{version}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{release}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{arch}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{group}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{summary}<>~:;<>~:;<>~:;-1614761173-17392-attr-<>~:;<>~:;<>~:;%{description}<>~:;<>~:;<>~:;-1614761173-17392-pkg-<>~:;<>~:;<>~:; --whatprovides cPanel-cPAddon executable: /usr/bin/repoquery package: yum-utils-1.1.31-54.el7_8 component: yum-utils pid: 17406 hostname: ************************ count: 2 abrt_version: 2.1.11 analyzer: Python architecture: x86_64 dso_list: yum-3.4.3-168.el7.centos.noarch duphash: 064006f54b75bb9271c60312b0babdd786ec7363 event_log: kernel: 3.10.0-1160.11.1.el7.x86_64 last_occurrence: 1622617284 os_release: CentOS Linux release 7.9.2009 (Core) What is strange is that the pid is the same! How? But then I see the line "count:" has incremented, "last_occurance" has updated, and they both show the same kernel version (but current is 3.10.0-1160.25.1.el7.x86_64). So it looks like a duplicate, but why? The last time this happend was going from 92 to 94, then no issues for minor updates, then tonight after going from 96.0.8 to 96.0.9 it reports this again. Any thoughts? -Pete

June 02, 2021 13:18

Thanks for the update - could you get a ticket submitted to our team so we can check this out? Just post the number here once you've done that so I can follow along.

June 02, 2021 15:12

Ticket ID: 94331650

June 02, 2021 15:15

Thanks - I'm following along with that ticket now.

June 03, 2021 11:44

After a bit of troubleshooting our team was able to determine this was an issue with the abrtd tools on the operating system, and not a cPanel package or notification causing the problem.

11.94.0.2 UPCP errors

Comments

Didn't find what you were looking for?