- AlmaLinux Users - AlmaLinux List Archives

Re: Problem with VM in Azure running Almalinux 10 x86_64
by Christopher Cox 10 Nov '26

10 Nov '26

The "fix" for below was simply removing the old kernels. But how it got into the bad state ??? Anyway, for those that might see the same bad state. On 11/10/26 12:40 PM, Christopher Cox via AlmaLinux Users wrote: > I went to try and do updates to a VM in our Azure instance that is using > Almalinux 10 and got the following: > > # dnf update > Last metadata expiration check: 0:50:06 ago on Thu 05 Nov 2026 07:26:35 PM UTC. > Error: > Problem: package kernel-uki-virt-6.12.0-211.61.1.el10_2.x86_64 from @System > requires kernel-modules-core-uname-r = 6.12.0-211.61.1.el10_2.x86_64, but none > of the providers can be installed > - conflicting requests > (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use > not only best candidate packages) > > > Now, what is really weird, is I know we've applied updates before, maybe as > recently as a week or two ago. With a reboot afterwards. > > > # uname -a > Linux vm-example-usw2-001 6.12.0-211.47.1.el10_2.x86_64 #1 SMP PREEMPT_DYNAMIC > Thu Aug 13 10:40:14 EDT 2026 x86_64 GNU/Linux > > Notice the kernel that is running. > > # rpm -q -a | grep kernel-6 > kernel-6.12.0-211.47.1.el10_2.x86_64 > kernel-6.12.0-211.61.1.el10_2.x86_64 > kernel-6.12.0-211.68.1.el10_2.x86_64 > > And from dmesg: > > dmesg | grep vmlinuz > [ 0.000000] Command line: BOOT_IMAGE=(hd0,gpt3)/ > vmlinuz-6.12.0-211.47.1.el10_2.x86_64 root=UUID=472965f2-0739-4ac0- > b75a-710112ce4699 ro loglevel=3 console=tty1 console=ttyS0 earlyprintk=ttyS0 > rootdelay=300 no_timer_check nvme_core.io_timeout=240 biosdevname=0 net.ifnames=0 > [ 0.027509] Kernel command line: BOOT_IMAGE=(hd0,gpt3)/ > vmlinuz-6.12.0-211.47.1.el10_2.x86_64 root=UUID=472965f2-0739-4ac0- > b75a-710112ce4699 ro loglevel=3 console=tty1 console=ttyS0 earlyprintk=ttyS0 > rootdelay=300 no_timer_check nvme_core.io_timeout=240 biosdevname=0 net.ifnames=0 > [ 0.027673] Unknown kernel command line parameters "BOOT_IMAGE=(hd0,gpt3)/ > vmlinuz-6.12.0-211.47.1.el10_2.x86_64 biosdevname=0", will be passed to user space. > [ 1.134115] BOOT_IMAGE=(hd0,gpt3)/vmlinuz-6.12.0-211.47.1.el10_2.x86_64 > > > So, there's are really two problems. One, I can't do updates anymore because > the first issue, but the second issue is why after doing updates am I still on > an old kernel (???) I have done nothing configuration wise outside of the > defaults in that regard. I'm stumped. Suggestions? > > I'm thinking (guessing) it has to do with how boot is actually done for this in > the cloud on Azure. > > _______________________________________________ > AlmaLinux Users mailing list -- users(a)lists.almalinux.org > To unsubscribe send an email to users-leave(a)lists.almalinux.org

1 0

Problem with VM in Azure running Almalinux 10 x86_64
by Christopher Cox 05 Nov '26

05 Nov '26

I went to try and do updates to a VM in our Azure instance that is using Almalinux 10 and got the following: # dnf update Last metadata expiration check: 0:50:06 ago on Thu 05 Nov 2026 07:26:35 PM UTC. Error: Problem: package kernel-uki-virt-6.12.0-211.61.1.el10_2.x86_64 from @System requires kernel-modules-core-uname-r = 6.12.0-211.61.1.el10_2.x86_64, but none of the providers can be installed - conflicting requests (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Now, what is really weird, is I know we've applied updates before, maybe as recently as a week or two ago. With a reboot afterwards. # uname -a Linux vm-example-usw2-001 6.12.0-211.47.1.el10_2.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Aug 13 10:40:14 EDT 2026 x86_64 GNU/Linux Notice the kernel that is running. # rpm -q -a | grep kernel-6 kernel-6.12.0-211.47.1.el10_2.x86_64 kernel-6.12.0-211.61.1.el10_2.x86_64 kernel-6.12.0-211.68.1.el10_2.x86_64 And from dmesg: dmesg | grep vmlinuz [ 0.000000] Command line: BOOT_IMAGE=(hd0,gpt3)/vmlinuz-6.12.0-211.47.1.el10_2.x86_64 root=UUID=472965f2-0739-4ac0-b75a-710112ce4699 ro loglevel=3 console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 no_timer_check nvme_core.io_timeout=240 biosdevname=0 net.ifnames=0 [ 0.027509] Kernel command line: BOOT_IMAGE=(hd0,gpt3)/vmlinuz-6.12.0-211.47.1.el10_2.x86_64 root=UUID=472965f2-0739-4ac0-b75a-710112ce4699 ro loglevel=3 console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 no_timer_check nvme_core.io_timeout=240 biosdevname=0 net.ifnames=0 [ 0.027673] Unknown kernel command line parameters "BOOT_IMAGE=(hd0,gpt3)/vmlinuz-6.12.0-211.47.1.el10_2.x86_64 biosdevname=0", will be passed to user space. [ 1.134115] BOOT_IMAGE=(hd0,gpt3)/vmlinuz-6.12.0-211.47.1.el10_2.x86_64 So, there's are really two problems. One, I can't do updates anymore because the first issue, but the second issue is why after doing updates am I still on an old kernel (???) I have done nothing configuration wise outside of the defaults in that regard. I'm stumped. Suggestions? I'm thinking (guessing) it has to do with how boot is actually done for this in the cloud on Azure.

1 0

Re: PHP security vulnerabilities on my AlmaLinux 9.8
by Francesco Di Nucci 22 Oct '26

22 Oct '26

The Alma blog post (https://almalinux.org/blog/2026-10-21-php2shell-cve-2026-109618-cve-2026-10…) lists the package versions with the fixes (quote below). Check the package versions and eventually update: /AlmaLinux 8 php:7.2 stream: php-7.2.24-1.module_el8.10.0+4315+7b734bf3.alma.1 php:7.3 stream: php-7.3.20-1.module_el8.10.0+4316+90ea5fe5.alma.1 php:7.4 stream: php-7.4.33-8.module_el8.10.0+4321+cf5fd4bb (Red Hat’s update, released directly to production) php:8.0 stream: php-8.0.30-1.module_el8.10.0+4319+26f10322.alma.1 php:8.2 stream: php-8.2.33-1.module_el8.10.0+4320+c30d6dbb.alma.1 AlmaLinux 9 Default (PHP 8.0): php-8.0.30-8.el9_8.alma.1 php:8.1 stream: php-8.1.32-1.module_el9.8.0+326+528679fc.alma.1 php:8.2 stream: php-8.2.33-1.module_el9.8.0+327+37dfd4b4.alma.1 php:8.3 stream: php-8.3.33-1.module_el9.8.0+328+1fdeb728.alma.1 AlmaLinux 10 Default (PHP 8.3): php-8.3.33-1.el10_2.alma.1 PHP 8.4 (php8.4 packages): php8.4-8.4.24-1.el10_2.alma.1 AlmaLinux Kitten 10 The fix will ride along in the next regular PHP update, so no separate build is being made./ -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email:francesco.dinucci@na.infn.it On 22/10/26 15:23, Turritopsis Dohrnii Teo En Ming via AlmaLinux Users wrote: > Subject: PHP security vulnerabilities on my AlmaLinux 9.8 > > Good day from Singapore, > > Can I check and confirm with you whether the PHP security > vulnerabilities disclosed on 21 Oct 2026 have been fixed in my > AlmaLinux 9.8? > > [root@ns1 ~]# cat /etc/os-release > NAME="AlmaLinux" > VERSION="9.8 (Olive Jaguar)" > ID="almalinux" > ID_LIKE="rhel centos fedora" > VERSION_ID="9.8" > PLATFORM_ID="platform:el9" > PRETTY_NAME="AlmaLinux 9.8 (Olive Jaguar)" > ANSI_COLOR="0;34" > LOGO="fedora-logo-icon" > CPE_NAME="cpe:/o:almalinux:almalinux:9::baseos" > HOME_URL="https://almalinux.org/" > DOCUMENTATION_URL="https://wiki.almalinux.org/" > BUG_REPORT_URL="https://bugs.almalinux.org/" > > ALMALINUX_MANTISBT_PROJECT="AlmaLinux-9" > ALMALINUX_MANTISBT_PROJECT_VERSION="9.8" > REDHAT_SUPPORT_PRODUCT="AlmaLinux" > REDHAT_SUPPORT_PRODUCT_VERSION="9.8" > SUPPORT_END=2032-06-01 > [root@ns1 ~]# rpm -qa | grep -i '^php' > php-pecl-zip-1.19.2-6.el9.x86_64 > php-pear-1.10.14-1.el9.noarch > php-pspell-8.0.30-3.el9.x86_64 > php-common-8.0.30-8.el9_8.alma.1.x86_64 > php-pdo-8.0.30-8.el9_8.alma.1.x86_64 > php-mysqlnd-8.0.30-8.el9_8.alma.1.x86_64 > php-cli-8.0.30-8.el9_8.alma.1.x86_64 > php-fpm-8.0.30-8.el9_8.alma.1.x86_64 > php-gd-8.0.30-8.el9_8.alma.1.x86_64 > php-intl-8.0.30-8.el9_8.alma.1.x86_64 > php-mbstring-8.0.30-8.el9_8.alma.1.x86_64 > php-opcache-8.0.30-8.el9_8.alma.1.x86_64 > php-process-8.0.30-8.el9_8.alma.1.x86_64 > php-xml-8.0.30-8.el9_8.alma.1.x86_64 > [root@ns1 ~]# dnf updateinfo list --security > Last metadata expiration check: 2:09:59 ago on Thu 22 Oct 2026 > 11:46:51 AM +08. > [root@ns1 ~]# dnf updateinfo info --cve CVE-2026-109618 > Last metadata expiration check: 2:10:22 ago on Thu 22 Oct 2026 > 11:46:51 AM +08. > > [root@ns1 ~]# dnf updateinfo info --cve CVE-2026-109619 > Last metadata expiration check: 2:10:35 ago on Thu 22 Oct 2026 > 11:46:51 AM +08. > > [root@ns1 ~]# systemctl status httpd > ● httpd.service - The Apache HTTP Server > Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; > preset: disabled) > Drop-In: /usr/lib/systemd/system/httpd.service.d > └─php-fpm.conf > Active: active (running) since Thu 2026-10-22 07:18:37 +08; 6h ago > Docs: man:httpd.service(8) > Main PID: 1081 (httpd) > Status: "Total requests: 2945; Idle/Busy workers > 100/0;Requests/sec: 0.123; Bytes served/sec: 1.5KB/sec" > Tasks: 231 (limit: 74628) > Memory: 54.8M (peak: 56.5M) > CPU: 45.196s > CGroup: /system.slice/httpd.service > ├─1081 /usr/sbin/httpd -DFOREGROUND > ├─1183 /usr/sbin/httpd -DFOREGROUND > ├─1188 /usr/sbin/httpd -DFOREGROUND > ├─1194 /usr/sbin/httpd -DFOREGROUND > ├─1212 /usr/sbin/httpd -DFOREGROUND > ├─1224 /usr/sbin/httpd -DFOREGROUND > └─7507 /usr/sbin/httpd -DFOREGROUND > > Oct 22 07:18:37 ns1.example.com systemd[1]: Starting The Apache HTTP > Server... > Oct 22 07:18:37 ns1.example.com systemd[1]: Started The Apache HTTP > Server. > Oct 22 07:18:37 ns1.example.com httpd[1081]: Server configured, > listening on: port 443, port 80 > [root@ns1 ~]# systemctl status php-fpm > ● php-fpm.service - The PHP FastCGI Process Manager > Loaded: loaded (/usr/lib/systemd/system/php-fpm.service; enabled; > preset: disabled) > Drop-In: /etc/systemd/system/php-fpm.service.d > └─00-virtualmin.conf > Active: active (running) since Thu 2026-10-22 13:53:38 +08; 4min > 23s ago > Main PID: 132343 (php-fpm) > Status: "Processes active: 0, idle: 35, Requests: 0, slow: 0, > Traffic: 0req/sec" > Tasks: 36 (limit: 74628) > Memory: 39.1M (peak: 39.8M) > CPU: 495ms > CGroup: /system.slice/php-fpm.service > ├─132343 "php-fpm: master process (/etc/php-fpm.conf)" > ├─132400 "php-fpm: pool 163465190630155" > ├─132401 "php-fpm: pool 163465190630155" > ├─132402 "php-fpm: pool 163465190630155" > ├─132403 "php-fpm: pool 16351709215424" > ├─132404 "php-fpm: pool 16351709215424" > ├─132405 "php-fpm: pool 16351709215424" > ├─132406 "php-fpm: pool 163595484830302" > ├─132407 "php-fpm: pool 163595484830302" > ├─132408 "php-fpm: pool 163595484830302" > ├─132409 "php-fpm: pool 163620624410460" > ├─132410 "php-fpm: pool 163620624410460" > ├─132411 "php-fpm: pool 163620624410460" > ├─132412 "php-fpm: pool 163620750817631" > ├─132413 "php-fpm: pool 163620750817631" > ├─132414 "php-fpm: pool 163620750817631" > ├─132415 "php-fpm: pool 166853132123059" > ├─132416 "php-fpm: pool 166853132123059" > ├─132417 "php-fpm: pool 166853132123059" > ├─132418 "php-fpm: pool 17676128142092182" > ├─132419 "php-fpm: pool 17676128142092182" > ├─132420 "php-fpm: pool 17676128142092182" > ├─132422 "php-fpm: pool 17676224502138583" > ├─132423 "php-fpm: pool 17676224502138583" > ├─132424 "php-fpm: pool 17676224502138583" > ├─132425 "php-fpm: pool 17676233702148934" > ├─132426 "php-fpm: pool 17676233702148934" > ├─132427 "php-fpm: pool 17676233702148934" > ├─132428 "php-fpm: pool 17676246675678" > ├─132429 "php-fpm: pool 17676246675678" > ├─132430 "php-fpm: pool 17676246675678" > ├─132432 "php-fpm: pool www" > ├─132433 "php-fpm: pool www" > ├─132434 "php-fpm: pool www" > ├─132435 "php-fpm: pool www" > └─132436 "php-fpm: pool www" > > Oct 22 13:53:37 ns1.example.com systemd[1]: Starting The PHP FastCGI > Process Manager... > Oct 22 13:53:37 ns1.example.com php-fpm[132343]: [22-Oct-2026 > 13:53:37] NOTICE: PHP message: PHP Warning: Module "intl" is already > loaded in Unknown on line 0 > Oct 22 13:53:37 ns1.example.com php-fpm[132343]: [22-Oct-2026 > 13:53:37] NOTICE: PHP message: PHP Warning: Module "pspell" is > already loaded in Unknown on line 0 > Oct 22 13:53:37 ns1.example.com php-fpm[132343]: [22-Oct-2026 > 13:53:37] NOTICE: PHP message: PHP Warning: Module "zip" is already > loaded in Unknown on line 0 > Oct 22 13:53:38 ns1.example.com systemd[1]: Started The PHP FastCGI > Process Manager. > > Please advise. > > Thank you. > > Regards, > > Mr. Turritopsis Dohrnii Teo En Ming > Republic of Singapore > 22 Oct 2026 Thursday 7.47 pm Singapore Time > > > _______________________________________________ > AlmaLinux Users mailing list --users(a)lists.almalinux.org > To unsubscribe send an email tousers-leave(a)lists.almalinux.org

2 2

Re: Problems with kernels 42.1 and 44.1
by Francesco Di Nucci 22 Oct '26

22 Oct '26

Are you using the latest available RPMs from RDO (aka Epoxy)? -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email: francesco.dinucci(a)na.infn.it On 22/10/26 15:24, Adrian P. van Bloois via AlmaLinux Users wrote: > Hi Listers, > We have problems with Almalinux running on Openstack with kernels 42.1 > and 44.1. After 1 or two days the system hangs and is no longer > bootable with that kernel. We're now running 41.1 kernel. On systems > running on the HW directlyu everything goes well. > The last message in messages was: > Sep 15 07:00:14 XXX kernel: [TTM] Buffer eviction failed > > When running ossec we were flooded with these messages. > Is this a known problem? > > > Adrian > > > > >

1 0

PHP security vulnerabilities on my AlmaLinux 9.8
by Turritopsis Dohrnii Teo En Ming 22 Oct '26

22 Oct '26

Subject: PHP security vulnerabilities on my AlmaLinux 9.8 Good day from Singapore, Can I check and confirm with you whether the PHP security vulnerabilities disclosed on 21 Oct 2026 have been fixed in my AlmaLinux 9.8? [root@ns1 ~]# cat /etc/os-release NAME="AlmaLinux" VERSION="9.8 (Olive Jaguar)" ID="almalinux" ID_LIKE="rhel centos fedora" VERSION_ID="9.8" PLATFORM_ID="platform:el9" PRETTY_NAME="AlmaLinux 9.8 (Olive Jaguar)" ANSI_COLOR="0;34" LOGO="fedora-logo-icon" CPE_NAME="cpe:/o:almalinux:almalinux:9::baseos" HOME_URL="https://almalinux.org/" DOCUMENTATION_URL="https://wiki.almalinux.org/" BUG_REPORT_URL="https://bugs.almalinux.org/" ALMALINUX_MANTISBT_PROJECT="AlmaLinux-9" ALMALINUX_MANTISBT_PROJECT_VERSION="9.8" REDHAT_SUPPORT_PRODUCT="AlmaLinux" REDHAT_SUPPORT_PRODUCT_VERSION="9.8" SUPPORT_END=2032-06-01 [root@ns1 ~]# rpm -qa | grep -i '^php' php-pecl-zip-1.19.2-6.el9.x86_64 php-pear-1.10.14-1.el9.noarch php-pspell-8.0.30-3.el9.x86_64 php-common-8.0.30-8.el9_8.alma.1.x86_64 php-pdo-8.0.30-8.el9_8.alma.1.x86_64 php-mysqlnd-8.0.30-8.el9_8.alma.1.x86_64 php-cli-8.0.30-8.el9_8.alma.1.x86_64 php-fpm-8.0.30-8.el9_8.alma.1.x86_64 php-gd-8.0.30-8.el9_8.alma.1.x86_64 php-intl-8.0.30-8.el9_8.alma.1.x86_64 php-mbstring-8.0.30-8.el9_8.alma.1.x86_64 php-opcache-8.0.30-8.el9_8.alma.1.x86_64 php-process-8.0.30-8.el9_8.alma.1.x86_64 php-xml-8.0.30-8.el9_8.alma.1.x86_64 [root@ns1 ~]# dnf updateinfo list --security Last metadata expiration check: 2:09:59 ago on Thu 22 Oct 2026 11:46:51 AM +08. [root@ns1 ~]# dnf updateinfo info --cve CVE-2026-109618 Last metadata expiration check: 2:10:22 ago on Thu 22 Oct 2026 11:46:51 AM +08. [root@ns1 ~]# dnf updateinfo info --cve CVE-2026-109619 Last metadata expiration check: 2:10:35 ago on Thu 22 Oct 2026 11:46:51 AM +08. [root@ns1 ~]# systemctl status httpd ● httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; preset: disabled) Drop-In: /usr/lib/systemd/system/httpd.service.d └─php-fpm.conf Active: active (running) since Thu 2026-10-22 07:18:37 +08; 6h ago Docs: man:httpd.service(8) Main PID: 1081 (httpd) Status: "Total requests: 2945; Idle/Busy workers 100/0;Requests/sec: 0.123; Bytes served/sec: 1.5KB/sec" Tasks: 231 (limit: 74628) Memory: 54.8M (peak: 56.5M) CPU: 45.196s CGroup: /system.slice/httpd.service ├─1081 /usr/sbin/httpd -DFOREGROUND ├─1183 /usr/sbin/httpd -DFOREGROUND ├─1188 /usr/sbin/httpd -DFOREGROUND ├─1194 /usr/sbin/httpd -DFOREGROUND ├─1212 /usr/sbin/httpd -DFOREGROUND ├─1224 /usr/sbin/httpd -DFOREGROUND └─7507 /usr/sbin/httpd -DFOREGROUND Oct 22 07:18:37 ns1.example.com systemd[1]: Starting The Apache HTTP Server... Oct 22 07:18:37 ns1.example.com systemd[1]: Started The Apache HTTP Server. Oct 22 07:18:37 ns1.example.com httpd[1081]: Server configured, listening on: port 443, port 80 [root@ns1 ~]# systemctl status php-fpm ● php-fpm.service - The PHP FastCGI Process Manager Loaded: loaded (/usr/lib/systemd/system/php-fpm.service; enabled; preset: disabled) Drop-In: /etc/systemd/system/php-fpm.service.d └─00-virtualmin.conf Active: active (running) since Thu 2026-10-22 13:53:38 +08; 4min 23s ago Main PID: 132343 (php-fpm) Status: "Processes active: 0, idle: 35, Requests: 0, slow: 0, Traffic: 0req/sec" Tasks: 36 (limit: 74628) Memory: 39.1M (peak: 39.8M) CPU: 495ms CGroup: /system.slice/php-fpm.service ├─132343 "php-fpm: master process (/etc/php-fpm.conf)" ├─132400 "php-fpm: pool 163465190630155" ├─132401 "php-fpm: pool 163465190630155" ├─132402 "php-fpm: pool 163465190630155" ├─132403 "php-fpm: pool 16351709215424" ├─132404 "php-fpm: pool 16351709215424" ├─132405 "php-fpm: pool 16351709215424" ├─132406 "php-fpm: pool 163595484830302" ├─132407 "php-fpm: pool 163595484830302" ├─132408 "php-fpm: pool 163595484830302" ├─132409 "php-fpm: pool 163620624410460" ├─132410 "php-fpm: pool 163620624410460" ├─132411 "php-fpm: pool 163620624410460" ├─132412 "php-fpm: pool 163620750817631" ├─132413 "php-fpm: pool 163620750817631" ├─132414 "php-fpm: pool 163620750817631" ├─132415 "php-fpm: pool 166853132123059" ├─132416 "php-fpm: pool 166853132123059" ├─132417 "php-fpm: pool 166853132123059" ├─132418 "php-fpm: pool 17676128142092182" ├─132419 "php-fpm: pool 17676128142092182" ├─132420 "php-fpm: pool 17676128142092182" ├─132422 "php-fpm: pool 17676224502138583" ├─132423 "php-fpm: pool 17676224502138583" ├─132424 "php-fpm: pool 17676224502138583" ├─132425 "php-fpm: pool 17676233702148934" ├─132426 "php-fpm: pool 17676233702148934" ├─132427 "php-fpm: pool 17676233702148934" ├─132428 "php-fpm: pool 17676246675678" ├─132429 "php-fpm: pool 17676246675678" ├─132430 "php-fpm: pool 17676246675678" ├─132432 "php-fpm: pool www" ├─132433 "php-fpm: pool www" ├─132434 "php-fpm: pool www" ├─132435 "php-fpm: pool www" └─132436 "php-fpm: pool www" Oct 22 13:53:37 ns1.example.com systemd[1]: Starting The PHP FastCGI Process Manager... Oct 22 13:53:37 ns1.example.com php-fpm[132343]: [22-Oct-2026 13:53:37] NOTICE: PHP message: PHP Warning: Module "intl" is already loaded in Unknown on line 0 Oct 22 13:53:37 ns1.example.com php-fpm[132343]: [22-Oct-2026 13:53:37] NOTICE: PHP message: PHP Warning: Module "pspell" is already loaded in Unknown on line 0 Oct 22 13:53:37 ns1.example.com php-fpm[132343]: [22-Oct-2026 13:53:37] NOTICE: PHP message: PHP Warning: Module "zip" is already loaded in Unknown on line 0 Oct 22 13:53:38 ns1.example.com systemd[1]: Started The PHP FastCGI Process Manager. Please advise. Thank you. Regards, Mr. Turritopsis Dohrnii Teo En Ming Republic of Singapore22 Oct 2026 Thursday 7.47 pm Singapore Time

1 0

Request for python module with higher version
by Adrian P. van Bloois 13 Oct '26

13 Oct '26

See Subject. I would be interessted in a configuration with python as a module and then hight version of it than we have now. Adrian -- Adri P. van Bloois It's never too late for early music!!!

1 0

Re: AlmaLinux 9.7 update question:
by Paul Graff 12 Oct '26

12 Oct '26

On 10/11/26 3:51 PM, Akemi Yagi via AlmaLinux Users wrote: > On Sun, Oct 11, 2026 at 9:28 AM Paul Graff via AlmaLinux Users > <users(a)lists.almalinux.org> wrote: >> >> Hi, for a few weeks now there are a couple of packages libheif-freeworld >> and vlc-plugins-freeworld that seem to be problematic. >> >> [root@ThinkCentre-72e ~]# dnf upgrade >> Last metadata expiration check: 1:34:39 ago on Sat 03 Oct 2026 09:39:52 >> AM CDT. >> Error: >> Problem 1: cannot install the best update candidate for package >> libheif-freeworld-1.16.1-1.el9.x86_64 >> - nothing provides libheif(x86-64) = 1.23.5 needed by >> libheif-freeworld-1.23.5-1.el9.x86_64 from rpmfusion-free-updates >> Problem 2: cannot install the best update candidate for package >> vlc-plugins-freeworld-3.0.23-1.el9.x86_64 >> - nothing provides vlc-libs(x86-64) >= 1:3.0.24 needed by >> vlc-plugins-freeworld-3.0.24-1.el9.x86_64 from rpmfusion-free-updates >> (try to add '--skip-broken' to skip uninstallable packages or '--nobest' >> to use not only best candidate packages) >> >> So I have been passing 'dnf upgrade --nobest' as shown below. In order >> to complete the update. >> >> [root@ThinkCentre-72e ~]# dnf upgrade --nobest >> Last metadata expiration check: 1:35:13 ago on Sat 03 Oct 2026 09:39:52 >> AM CDT. >> Dependencies resolved. >> >> Problem 1: cannot install the best update candidate for package >> libheif-freeworld-1.16.1-1.el9.x86_64 >> - nothing provides libheif(x86-64) = 1.23.5 needed by >> libheif-freeworld-1.23.5-1.el9.x86_64 from rpmfusion-free-updates >> Problem 2: cannot install the best update candidate for package >> vlc-plugins-freeworld-3.0.23-1.el9.x86_64 >> - nothing provides vlc-libs(x86-64) >= 1:3.0.24 needed by >> vlc-plugins-freeworld-3.0.24-1.el9.x86_64 from rpmfusion-free-updates > (snip) >> >> Is this something that will correct itself? What is the best course of >> action to take? >> >> -Greatest Hopes > > Maybe it's been corrected by now? If not, wait a little longer until > the repository site you are accessing gets fully updated. > > Akemi Thank you for your response. Today I performed an update on the machine and everything seemed to go fine. -Thanks

1 0

Re: AlmaLinux 9.7 update question:
by Akemi Yagi 11 Oct '26

11 Oct '26

On Sun, Oct 11, 2026 at 9:28 AM Paul Graff via AlmaLinux Users <users(a)lists.almalinux.org> wrote: > > Hi, for a few weeks now there are a couple of packages libheif-freeworld > and vlc-plugins-freeworld that seem to be problematic. > > [root@ThinkCentre-72e ~]# dnf upgrade > Last metadata expiration check: 1:34:39 ago on Sat 03 Oct 2026 09:39:52 > AM CDT. > Error: > Problem 1: cannot install the best update candidate for package > libheif-freeworld-1.16.1-1.el9.x86_64 > - nothing provides libheif(x86-64) = 1.23.5 needed by > libheif-freeworld-1.23.5-1.el9.x86_64 from rpmfusion-free-updates > Problem 2: cannot install the best update candidate for package > vlc-plugins-freeworld-3.0.23-1.el9.x86_64 > - nothing provides vlc-libs(x86-64) >= 1:3.0.24 needed by > vlc-plugins-freeworld-3.0.24-1.el9.x86_64 from rpmfusion-free-updates > (try to add '--skip-broken' to skip uninstallable packages or '--nobest' > to use not only best candidate packages) > > So I have been passing 'dnf upgrade --nobest' as shown below. In order > to complete the update. > > [root@ThinkCentre-72e ~]# dnf upgrade --nobest > Last metadata expiration check: 1:35:13 ago on Sat 03 Oct 2026 09:39:52 > AM CDT. > Dependencies resolved. > > Problem 1: cannot install the best update candidate for package > libheif-freeworld-1.16.1-1.el9.x86_64 > - nothing provides libheif(x86-64) = 1.23.5 needed by > libheif-freeworld-1.23.5-1.el9.x86_64 from rpmfusion-free-updates > Problem 2: cannot install the best update candidate for package > vlc-plugins-freeworld-3.0.23-1.el9.x86_64 > - nothing provides vlc-libs(x86-64) >= 1:3.0.24 needed by > vlc-plugins-freeworld-3.0.24-1.el9.x86_64 from rpmfusion-free-updates (snip) > > Is this something that will correct itself? What is the best course of > action to take? > > -Greatest Hopes Maybe it's been corrected by now? If not, wait a little longer until the repository site you are accessing gets fully updated. Akemi

1 0

AlmaLinux 9.7 update question:
by Paul Graff 11 Oct '26

11 Oct '26

Hi, for a few weeks now there are a couple of packages libheif-freeworld and vlc-plugins-freeworld that seem to be problematic. [root@ThinkCentre-72e ~]# dnf upgrade Last metadata expiration check: 1:34:39 ago on Sat 03 Oct 2026 09:39:52 AM CDT. Error: Problem 1: cannot install the best update candidate for package libheif-freeworld-1.16.1-1.el9.x86_64 - nothing provides libheif(x86-64) = 1.23.5 needed by libheif-freeworld-1.23.5-1.el9.x86_64 from rpmfusion-free-updates Problem 2: cannot install the best update candidate for package vlc-plugins-freeworld-3.0.23-1.el9.x86_64 - nothing provides vlc-libs(x86-64) >= 1:3.0.24 needed by vlc-plugins-freeworld-3.0.24-1.el9.x86_64 from rpmfusion-free-updates (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) So I have been passing 'dnf upgrade --nobest' as shown below. In order to complete the update. [root@ThinkCentre-72e ~]# dnf upgrade --nobest Last metadata expiration check: 1:35:13 ago on Sat 03 Oct 2026 09:39:52 AM CDT. Dependencies resolved. Problem 1: cannot install the best update candidate for package libheif-freeworld-1.16.1-1.el9.x86_64 - nothing provides libheif(x86-64) = 1.23.5 needed by libheif-freeworld-1.23.5-1.el9.x86_64 from rpmfusion-free-updates Problem 2: cannot install the best update candidate for package vlc-plugins-freeworld-3.0.23-1.el9.x86_64 - nothing provides vlc-libs(x86-64) >= 1:3.0.24 needed by vlc-plugins-freeworld-3.0.24-1.el9.x86_64 from rpmfusion-free-updates ==================================================================================================================================================================================================== Package Architecture Version Repository Size ==================================================================================================================================================================================================== Installing: kernel x86_64 5.14.0-687.53.1.el9_8 baseos 1.0 M kernel-core x86_64 5.14.0-687.53.1.el9_8 baseos 17 M kernel-devel x86_64 5.14.0-687.53.1.el9_8 appstream 18 M kernel-modules x86_64 5.14.0-687.53.1.el9_8 baseos 40 M kernel-modules-core x86_64 5.14.0-687.53.1.el9_8 baseos 31 M kernel-modules-extra x86_64 5.14.0-687.53.1.el9_8 baseos 1.5 M Upgrading: bootc x86_64 1.16.4-2.el9_8 appstream 6.0 M distribution-gpg-keys noarch 1.123-1.el9 epel 773 k ghostscript x86_64 9.54.0-19.el9_8.1 appstream 36 k ghostscript-tools-fonts x86_64 9.54.0-19.el9_8.1 appstream 11 k ghostscript-tools-printing x86_64 9.54.0-19.el9_8.1 appstream 11 k gvfs x86_64 1.48.1-8.el9_8.1 appstream 345 k gvfs-client x86_64 1.48.1-8.el9_8.1 appstream 735 k gvfs-fuse x86_64 1.48.1-8.el9_8.1 appstream 27 k gvfs-goa x86_64 1.48.1-8.el9_8.1 appstream 67 k gvfs-gphoto2 x86_64 1.48.1-8.el9_8.1 appstream 59 k gvfs-mtp x86_64 1.48.1-8.el9_8.1 appstream 60 k gvfs-smb x86_64 1.48.1-8.el9_8.1 appstream 39 k kernel-headers x86_64 5.14.0-687.53.1.el9_8 appstream 2.6 M kernel-tools x86_64 5.14.0-687.53.1.el9_8 baseos 1.3 M kernel-tools-libs x86_64 5.14.0-687.53.1.el9_8 baseos 1.0 M libgs x86_64 9.54.0-19.el9_8.1 appstream 3.1 M libpcap x86_64 14:1.10.0-4.el9_8.1 baseos 170 k openssh x86_64 9.9p1-12.el9_8.alma.1 baseos 422 k openssh-clients x86_64 9.9p1-12.el9_8.alma.1 baseos 769 k openssh-server x86_64 9.9p1-12.el9_8.alma.1 baseos 545 k python3-perf x86_64 5.14.0-687.53.1.el9_8 appstream 2.6 M Removing: kernel x86_64 5.14.0-687.48.1.el9_8 @baseos 0 kernel-core x86_64 5.14.0-687.48.1.el9_8 @baseos 68 M kernel-devel x86_64 5.14.0-687.48.1.el9_8 @appstream 71 M kernel-modules x86_64 5.14.0-687.48.1.el9_8 @baseos 38 M kernel-modules-core x86_64 5.14.0-687.48.1.el9_8 @baseos 29 M kernel-modules-extra x86_64 5.14.0-687.48.1.el9_8 @baseos 429 k Skipping packages with broken dependencies: libheif-freeworld x86_64 1.23.5-1.el9 rpmfusion-free-updates 68 k vlc-plugins-freeworld x86_64 3.0.24-1.el9 rpmfusion-free-updates 122 k Transaction Summary ==================================================================================================================================================================================================== Install 6 Packages Upgrade 21 Packages Remove 6 Packages Skip 2 Packages Total download size: 129 M Is this ok [y/N]: Is this something that will correct itself? What is the best course of action to take? -Greatest Hopes

1 0

Problems with kernels 42.1 and 44.1
by Adrian P. van Bloois 05 Oct '26

05 Oct '26

Hi Listers, We have problems with Almalinux running on Openstack with kernels 42.1 and 44.1. After 1 or two days the system hangs and is no longer bootable with that kernel. We're now running 41.1 kernel. On systems running on the HW directlyu everything goes well. The last message in messages was: Sep 15 07:00:14 XXX kernel: [TTM] Buffer eviction failed When running ossec we were flooded with these messages. Is this a known problem? Adrian -- Adri P. van Bloois It's never too late for early music!!!

1 0