- AlmaLinux Users - AlmaLinux List Archives

Re: New to Almalinux libnghttp2 needed
by Jerry Geis 19 May '25

19 May '25

On Mon, May 19, 2025 at 10:37 AM Jonathan Wright via AlmaLinux Users < users(a)lists.almalinux.org> wrote: > You probably need to enable the `CRB` repo as that's where the package > exists. > > You can do this with `sudo dnf config-manager --enable crb` > > [jonathan@jon-home ~]$ dnf info libnghttp2-devel > Last metadata expiration check: 0:00:06 ago on Mon 19 May 2025 09:34:07 AM > CDT. > Available Packages > Name : libnghttp2-devel > Version : 1.43.0 > Release : 6.el9 > Architecture : i686 > Size : 52 k > Source : nghttp2-1.43.0-6.el9.src.rpm > Repository : crb > Summary : Files needed for building applications with libnghttp2 > URL : https://nghttp2.org/ > License : MIT > Description : The libnghttp2-devel package includes libraries and header > files needed > : for building applications with libnghttp2. > > Name : libnghttp2-devel > Version : 1.43.0 > Release : 6.el9 > Architecture : x86_64 > Size : 52 k > Source : nghttp2-1.43.0-6.el9.src.rpm > Repository : crb > Summary : Files needed for building applications with libnghttp2 > URL : https://nghttp2.org/ > License : MIT > Description : The libnghttp2-devel package includes libraries and header > files needed > : for building applications with libnghttp2. > _______________________________________________ > AlmaLinux Users mailing list -- users(a)lists.almalinux.org > To unsubscribe send an email to users-leave(a)lists.almalinux.org dnf config-manager --enable crb Updating Subscription Management repositories. Unable to read consumer identity This system is not registered with an entitlement server. You can use subscription-manager to register. The above is what I get.... Jerry

2 4

Setup of default route on multi-homed host
by James Fait 15 May '25

15 May '25

I have a system that is using Almalinux 8.10 that has several active networks for the segregation of traffic according to purpose. Whenever this machine is rebooted, it is random on which interface is selected to be the default route, with two interfaces being selected for default route, only one of which actually connects to the outside network. How can I force that the true default route is always chosen? I have attached the output of the route command before and after deleting the erroneous route. Thanks in advance for your assistance. ## Routing tables after power cycle -- no outside internet access $ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 10.57.30.1 0.0.0.0 UG 100 0 0 eno2 default pancho208 0.0.0.0 UG 101 0 0 eno4 10.57.0.0 0.0.0.0 255.255.0.0 U 100 0 0 eno2 ###.54.208.0 0.0.0.0 255.255.255.0 U 101 0 0 eno4 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 $ sudo route del default # delete the first route ## Routing tables with working outside internet $ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default pancho208 0.0.0.0 UG 101 0 0 eno4 10.57.0.0 0.0.0.0 255.255.0.0 U 100 0 0 eno2 ###.54.208.0 0.0.0.0 255.255.255.0 U 101 0 0 eno4 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0

1 0

AlmaLinux Bug fixing process
by Alessandro Baggi 13 May '25

13 May '25

Hi list, I would like to know how works bugfixes on AlmaLinux when a user report a moderate/critical bug. For example, some times ago I found a bug in Debian stable kernel relative to MD devices. I contacted the developer, helped the team with testing to reproduce the issue, testing patches. After some day patch applied on testing and unstable and after ~15 days patch was released on debian stable kernel (wit a backport) and on backports kernel. How works this on AlmaLinux? I know that I can open bugs and help but what about timing on patchs release? I can contact the "kernel team" directly like in Debian? Patch will be released during minor release update or when ready and tested? Thank you in advance. Best regards, Alessandro

1 0

Fwd: Training SIG
by Bryson 02 Apr '25

02 Apr '25

Hello everyone! I am currently gauging interest in a training SIG. Please let me know if this is something you'd want to assist with. The focus areas would be; - Beginner to advanced training courses on system administration, security, and more. - Recording and editing trainings. - Standing up an AlmaLinux OS course certifications. - Interactive labs and virtual machines to practice AlmaLinux commands and tasks. - Certification study guides and hands-on practice exams for certifications. - Community mentorship programs to help new users learn from experienced administrators. If any of these sound like something you would be interested in helping with, or you feel you would like to see this happen, please reply to this email! Feel free to suggest anything you would like to see added to the scope of this SIG.

2 1

About rdma service in Almalinux9
by Patrick Bégou 28 Mar '25

28 Mar '25

Hi, I'm deploying a small cluster based on Almalinux9 using a dedicated cluster environment. When deploying infiniband support, the provided Ansible scripts try to launch the rdma service and it fails. In my old CentOS8 cluster, rdma-core provides the rdma service startup file /usr/lib/systemd/system/rdma.service in rdma-core-26.0-8.el8 to launch the rdma service In my new Almalinux9 cluster this file is no more provided by rdma-core-51.0-1.el9 And I'm unable to understand if it is no more necessary ("automagically" activated) or if I need an other package by looking at various documentations and https://github.com/linux-rdma/rdma-core. But I'm not very familiar with this stack as usually it works out of the box (so I never delved deeply into the documentation before) Could someone help me to clarify this ? Thanks Patrick

1 0

Cannot install drivers for NVIDIA
by Angel Campoverde 25 Feb '25

25 Feb '25

Hi, I am trying to install NVIDIA drivers following https://wiki.almalinux.org/series/system/SystemSeriesA03R9.html#%F0%9F%8C%9… but I see: Last metadata expiration check: 0:00:04 ago on Tue 25 Feb 2025 05:34:12 PM CST. Error: Problem 1: package nvidia-kmod-common-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 requires nvidia-kmod = 3:570.86.15, but none of the providers can be installed - cannot install the best candidate for the job - package kmod-nvidia-latest-dkms-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 is filtered out by modular filtering - package kmod-nvidia-open-dkms-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 is filtered out by modular filtering Problem 2: package nvidia-driver-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 requires nvidia-kmod-common = 3:570.86.15, but none of the providers can be installed - package nvidia-kmod-common-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 requires nvidia-kmod = 3:570.86.15, but none of the providers can be installed - cannot install the best candidate for the job - package kmod-nvidia-latest-dkms-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 is filtered out by modular filtering - package kmod-nvidia-open-dkms-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 is filtered out by modular filtering Problem 3: package nvidia-driver-cuda-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 requires nvidia-kmod-common = 3:570.86.15, but none of the providers can be installed - package nvidia-kmod-common-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 requires nvidia-kmod = 3:570.86.15, but none of the providers can be installed - cannot install the best candidate for the job - package kmod-nvidia-latest-dkms-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 is filtered out by modular filtering - package kmod-nvidia-open-dkms-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 is filtered out by modular filtering Problem 4: package nvidia-driver-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 requires nvidia-kmod-common = 3:570.86.15, but none of the providers can be installed - package nvidia-settings-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 requires nvidia-driver(x86-64) = 3:570.86.15, but none of the providers can be installed - package nvidia-kmod-common-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 requires nvidia-kmod = 3:570.86.15, but none of the providers can be installed - cannot install the best candidate for the job - package kmod-nvidia-latest-dkms-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 is filtered out by modular filtering - package kmod-nvidia-open-dkms-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 is filtered out by modular filtering Problem 5: package xorg-x11-nvidia-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 requires nvidia-driver(x86-64) = 3:570.86.15, but none of the providers can be installed - package nvidia-driver-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 requires nvidia-kmod-common = 3:570.86.15, but none of the providers can be installed - package nvidia-xconfig-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 requires xorg-x11-nvidia(x86-64) >= 3:570.86.15, but none of the providers can be installed - package nvidia-kmod-common-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 requires nvidia-kmod = 3:570.86.15, but none of the providers can be installed - cannot install the best candidate for the job - package kmod-nvidia-latest-dkms-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 is filtered out by modular filtering - package kmod-nvidia-open-dkms-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 is filtered out by modular filtering (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) What should I do about it? Cheers.

2 3

Libvirt SEV support in Kitten
by Teodor Pripoae 24 Feb '25

24 Feb '25

Hello, I have been testing Alma Linux Kitten and libvirt is not properly detecting SEV capabilities. Is Libvirt/QEMU compiled without SEV support ? $ dmesg | grep -i sev [ 1.821468] ccp 0000:45:00.1: sev enabled [ 53.414679] kvm_amd: SEV enabled (ASIDs 250 - 509) [ 53.414701] kvm_amd: SEV-ES enabled (ASIDs 1 - 249) [ 53.414720] kvm_amd: SEV-SNP disabled (ASIDs 1 - 249) $ virsh domcapabilities | grep -i sev <sev supported='no'/> $ virt-host-validate QEMU: Checking for hardware virtualization : PASS QEMU: Checking if device '/dev/kvm' exists : PASS QEMU: Checking if device '/dev/kvm' is accessible : PASS QEMU: Checking if device '/dev/vhost-net' exists : PASS QEMU: Checking if device '/dev/net/tun' exists : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for device assignment IOMMU support : PASS QEMU: Checking if IOMMU is enabled by kernel : PASS QEMU: Checking for secure guest support : PASS QEMU: Checking for AMD Secure Encrypted Virtualization-Encrypted State (SEV-ES): PASS QEMU: Checking for AMD Secure Encrypted Virtualization-Secure Nested Paging (SEV-SNP): PASS

2 2

AlmaLinux 9.3 and libvirtd problem
by Alessandro Baggi 22 Oct '24

22 Oct '24

Hi list, I'm running AlmaLinux 9.3 and I'm running several virtual machines using qemu-kvm and libvirtd ( and virt-manager). 3 VMs starts during system boot (configured with "virsh autostart VMNAME"). All works as expected until I loaded a old vm config file. When I tried to run "systemctl reload libvirtd" I got: "libvirtd.service is not active, cannot reload." It is enable on boot and running "systemctl status libvirtd" I get: Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled) Active: inactive (dead) since Thu 2024-01-25 16:32:40 CET; 4min 55s ago Duration: 5min 14.530s It reports that it is inactive (really dead) because I can't find it inside process table. Rebooting the system, I found libvirtd process with argument "--timeout=120" and after 120 seconds it dies. Reading libvirtd systemd unit I found Environment=LIBVIRTD_ARGS="--timeout 120" and from the man page I get: "t, --timeout *SECONDS* Exit after timeout period (in seconds), provided there are neither any client connections nor any running domains." Here I found something strange. On boot I have 3 running domains but libvirtd dies after 120 seconds. To load new configuration I need to run restart and virt-manager works without problem also if libvirtd is not running. This is a misconfiguration or it is a bug? Thank you in advance. Alessandro.

2 4

Cannot login to user account
by Angel Campoverde 22 Oct '24

22 Oct '24

Hi, I am seeing some problems with my alma9 installation. 1. I locked the machine with superkey + l, then I came back and unlocked it. 2. I saw that the upper case keys were on by default and I had to turn on caps-lock to turn back on the lower case keys. 3. The number pad did not show numbers, but the signs you get when you press shift, i.e. !@#$... 4. The arrow keys did not do the arrow thing, but they showed upper case letters, A, F, I do not remember the others. So I restarted. Then I tried to log in but: 1. When I put the right password, It looks like it will log in, because the screen goes black, however it comes back to the login screen without telling me anything else. 2. I know this is not a password issue, because when I put a wrong password, it tells me that the password is wrong. 3. I can log in as root. 4. I can do su - username and log in from there with my normal password. I do not recall doing anything special with the computer. Do you know what might be happening? Cheers.

2 1

Kickstart installs with isolinux (insecure boot) fails, same Kickstart works with EFI(secureboot)
by fait＠uga.edu 10 Sep '24

10 Sep '24

I have been working with AlmaLinux 8 for a couple of years using various iterations AlmaLinux 8, with my systems(5 of them) currently using 8.10. I am now in the process of validating install media to move to version 9.4, using kickstart to manage the initial configuration of these hosts. The kickstart file sets up the network,decides the host name, and sets up a complex partitioning scenario. Initially I tested this using secure boot, without any issue. I repeated the same install, on the same hardware, using the same kickstart file, only this time using the legacy boot (insecure). I have verified that this is an issue with insecure boot, as I then did a manual install of a server+graphics, along with development tools, and then took the resulting kickstart file, made the required changes so that the partitioning would work, and then attempted to do a kickstart install using this minimal kickstart, with the same results of success for the EFI boot, and failure with the isolinux boot. I did check, and the two commands to the kernel appear to be identical, but the insecure boot is not able to find the kickstart file. Has anyone else seen this behavior? Anyone found a work-around?

1 0