• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved [PPPM-13304] Update failed Almalinux 8.4 -> 8.5

J

JulianDot

Basic Pleskian
automatic updates failes on all servers with latest Plesk and Almalinux 8.4

2021-11-13 08:10:14 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2021-11-13 08:10:14 INFO: Librepo version: 1.14.0 with CURL_GLOBAL_ACK_EINTR support (libcurl/7.61.1 OpenSSL/1.1.1k zlib/1.2.11 brotli/1.0.6 libidn2/2.2.0 libpsl/0.20.2 (+libidn2/2.2.0) libssh/0.9.4/openssl/zlib nghttp2/1.33.0)
2021-11-13 08:10:14 INFO: --- logging initialized ---
2021-11-13 08:10:14 DEBUG: User-Agent: constructed: 'libdnf (AlmaLinux 8.5; generic; Linux.x86_64)'
2021-11-13 08:10:14 INFO: Librepo version: 1.14.0 with CURL_GLOBAL_ACK_EINTR support (libcurl/7.61.1 OpenSSL/1.1.1k zlib/1.2.11 brotli/1.0.6 libidn2/2.2.0 libpsl/0.20.2 (+libidn2/2.2.0) libssh/0.9.4/openssl/zlib nghttp2/1.33.0)
2021-11-13 08:10:14 DEBUG: repo: using cache for: baseos
2021-11-13 08:10:14 DEBUG: baseos: using metadata from Fri Nov 12 19:43:21 2021.
2021-11-13 08:10:14 DEBUG: repo: using cache for: appstream
2021-11-13 08:10:14 DEBUG: appstream: using metadata from Fri Nov 12 17:55:33 2021.
2021-11-13 08:10:14 DEBUG: repo: using cache for: extras
2021-11-13 08:10:14 DEBUG: extras: using metadata from Thu Nov 11 16:40:51 2021.
2021-11-13 08:10:14 DEBUG: repo: using cache for: epel
2021-11-13 08:10:14 DEBUG: epel: using metadata from Sat Nov 13 01:29:09 2021.
2021-11-13 08:10:14 DEBUG: repo: using cache for: epel-modular
2021-11-13 08:10:14 DEBUG: epel-modular: using metadata from Sat Nov 13 01:09:01 2021.
2021-11-13 08:10:14 DEBUG: repo: using cache for: PLESK_18_0_39-extras
2021-11-13 08:10:15 DEBUG: PLESK_18_0_39-extras: using metadata from Fri Oct 15 02:45:50 2021.
2021-11-13 08:10:15 DEBUG: repo: using cache for: PLESK_17_PHP74
2021-11-13 08:10:15 DEBUG: PLESK_17_PHP74: using metadata from Mon Oct 25 07:40:30 2021.
2021-11-13 08:10:15 DEBUG: repo: using cache for: plesk-ext-grafana
2021-11-13 08:10:15 DEBUG: plesk-ext-grafana: using metadata from Wed Nov 3 09:44:00 2021.
2021-11-13 08:10:15 DEBUG: repo: using cache for: plesk-ext-panel-migrator
2021-11-13 08:10:15 DEBUG: plesk-ext-panel-migrator: using metadata from Mon Feb 10 11:41:46 2020.
2021-11-13 08:10:15 INFO: Last metadata expiration check: 3:47:57 ago on Sat Nov 13 04:22:17 2021.
2021-11-13 08:10:15 DDEBUG: timer: sack setup: 783 ms
2021-11-13 08:10:15 DDEBUG: timer: depsolve: 31 ms
2021-11-13 08:10:15 DDEBUG: Cleaning up.
2021-11-13 08:10:15 DDEBUG: timer: sack setup: 164 ms
2021-11-13 08:10:15 ERROR: 'NoneType' object has no attribute 'run_sack'
2021-11-13 08:10:15 ERROR: Exited with returncode 1.
Click to expand...
 
what is the output when you run "yum update" manually?

During the manual update I had an error regarding "nothing provides jasper-devel needed by ImageMagick-devel-6.9.10.86-1.el8.x86_64"

but after activating powertools "yum config-manager --set-enabled powertools" the problem was also eliminated.
 
Hi,
I have same issue on Plesk Obsidian 18.0.39 and AlmaLinux 8.5 (Arctic Sphynx).
I ran yum update manually. Some updates were completed without problem.
But, when I re-run

# plesk sbin pum --list --repo-info --json

I get the same error. What should I do ?

# plesk sbin pum --list --repo-info --json
2021-11-14 23:35:28 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2021-11-14 23:35:28 INFO: Librepo version: 1.14.0 with CURL_GLOBAL_ACK_EINTR support (libcurl/7.61.1 OpenSSL/1.1.1k zlib/1.2.11 brotli/1.0.6 libidn2/2.2.0 libpsl/0.20.2 (+libidn2/2.2.0) libssh/0.9.4/openssl/zlib nghttp2/1.33.0)
2021-11-14 23:35:28 INFO: --- logging initialized ---
2021-11-14 23:35:28 DEBUG: User-Agent: constructed: 'libdnf (AlmaLinux 8.5; generic; Linux.x86_64)'
2021-11-14 23:35:29 INFO: Librepo version: 1.14.0 with CURL_GLOBAL_ACK_EINTR support (libcurl/7.61.1 OpenSSL/1.1.1k zlib/1.2.11 brotli/1.0.6 libidn2/2.2.0 libpsl/0.20.2 (+libidn2/2.2.0) libssh/0.9.4/openssl/zlib nghttp2/1.33.0)
2021-11-14 23:35:29 DEBUG: repo: using cache for: baseos
2021-11-14 23:35:29 DEBUG: baseos: using metadata from Sat Nov 13 04:43:21 2021.
2021-11-14 23:35:29 DEBUG: repo: using cache for: appstream
2021-11-14 23:35:29 DEBUG: appstream: using metadata from Sat Nov 13 02:55:33 2021.
2021-11-14 23:35:29 DEBUG: repo: using cache for: extras
2021-11-14 23:35:29 DEBUG: extras: using metadata from Fri Nov 12 01:40:51 2021.
2021-11-14 23:35:29 DEBUG: repo: using cache for: epel
2021-11-14 23:35:29 DEBUG: epel: using metadata from Sun Nov 14 12:57:51 2021.
2021-11-14 23:35:29 DEBUG: repo: using cache for: epel-modular
2021-11-14 23:35:29 DEBUG: epel-modular: using metadata from Sat Nov 13 10:09:01 2021.
2021-11-14 23:35:29 DEBUG: repo: using cache for: PLESK_18_0_39-extras
2021-11-14 23:35:29 DEBUG: PLESK_18_0_39-extras: using metadata from Fri Oct 15 11:45:50 2021.
2021-11-14 23:35:29 DEBUG: repo: using cache for: PLESK_17_PHP73
2021-11-14 23:35:29 DEBUG: PLESK_17_PHP73: using metadata from Thu Oct 28 20:51:11 2021.
2021-11-14 23:35:29 DEBUG: repo: using cache for: PLESK_17_PHP74
2021-11-14 23:35:29 DEBUG: PLESK_17_PHP74: using metadata from Mon Oct 25 16:40:30 2021.
2021-11-14 23:35:29 DEBUG: repo: using cache for: plesk-ext-grafana
2021-11-14 23:35:29 DEBUG: plesk-ext-grafana: using metadata from Wed Nov 3 18:44:00 2021.
2021-11-14 23:35:29 INFO: Last metadata expiration check: 0:03:23 ago on Sun Nov 14 23:32:06 2021.
2021-11-14 23:35:29 DDEBUG: timer: sack setup: 777 ms
2021-11-14 23:35:29 DDEBUG: timer: depsolve: 22 ms
2021-11-14 23:35:29 DDEBUG: Cleaning up.
2021-11-14 23:35:29 DDEBUG: timer: sack setup: 339 ms
2021-11-14 23:35:29 ERROR: 'NoneType' object has no attribute 'run_sack'
2021-11-14 23:35:29 ERROR: Exited with returncode 1.
exit status 1
 
Hi,
same issue.
In plesk panel shows Updates for 184 packages are available.
When run yum update, it seems everything is updated.
 
please check that powertools repository is available and emabled at your instance
 
right now, the only issue seem to be the warning that say " XXX package avilable"

yum update have nothing to update

the server say its almalinux 8.5 already
 
I had opened a ticket with Plesk this morning on this. We had converted a CentOS 8 to AlmaLinux on Friday and get the error daily since then, though I can install updates via yum just fine, and in fact installed two today just to prove it worked.

re: the number of updates not being correct, 1) this Plesk shows its last check for updates was Friday morning, so that's the last info it has, and 2) there's been a long standing bug where after you install updates (at least, via yum command line), Plesk will continue to send the email reminder of the pending updates for a while afterwards. We get the reminder weekly so I think it's a couple weeks give or take. I had reported that bug early this year I think it was...don't recall exactly, offhand.
 
Hi all

Plesk support just confirmed:
We have already been reported about this issue on AlmaLinux 8.5 - we're working on it to see what might be causing it and will update you as soon as possible.
Click to expand...
 
to address this problem we are going to release Plesk 18.0.39.2 hotfix today (2021-11-18)

thank your for you patience.
 
You must log in or register to reply here.

Similar threads

B
Resolved Plesk SysUpdates Error on trying to update from 18.0.41 on Alma 8.7
Replies
13
Views
3K
Kaspar
K
C
Issue pum is called with arguments: ['--list', '--repo-info', '--json']
Replies
4
Views
2K
VNick
V
brainforge
Resolved System updates have started failing.
Replies
2
Views
338
brainforge
brainforge
A
Resolved package updating failed
Replies
1
Views
860
arjanvr
A
E.BlackStone
Resolved ERROR: 'NoneType' object has no attribute 'run_sack'
Replies
4
Views
2K
websavers
websavers
Back
Top