- AlmaLinux Users - AlmaLinux List Archives

Re: Install sox in 9.6
by Stephen John Smoogen 21 May '25

21 May '25

On Wed, 21 May 2025 at 08:39, Jerry Geis via AlmaLinux Users < users(a)lists.almalinux.org> wrote: > > > On Wed, May 21, 2025 at 8:15 AM Jerry Geis <jerry.geis(a)gmail.com> wrote: > >> I do the following command to install sox and get an error: >> >> yum install sox >> Last metadata expiration check: 0:13:27 ago on Wed May 21 08:00:40 2025. >> No match for argument: sox >> Error: Unable to find a match: sox >> >> what? how do I install sox ? I tried dnf also >> >> Jerry >> >> > I did this: > yum install epel-release > yum install sox > > > my apologies for the email saying to do the above.. I didn't get this email until after I sent my reply. > that seemed to work > > Jerry > > _______________________________________________ > AlmaLinux Users mailing list -- users(a)lists.almalinux.org > To unsubscribe send an email to users-leave(a)lists.almalinux.org > -- Stephen J Smoogen. Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren

1 0

Re: Install sox in 9.6
by Stephen John Smoogen 21 May '25

21 May '25

On Wed, 21 May 2025 at 08:15, Jerry Geis via AlmaLinux Users < users(a)lists.almalinux.org> wrote: > I do the following command to install sox and get an error: > > yum install sox > Last metadata expiration check: 0:13:27 ago on Wed May 21 08:00:40 2025. > No match for argument: sox > Error: Unable to find a match: sox > > what? how do I install sox ? I tried dnf also > > The package sox has not been built for the base EL operating systems but is available in the EPEL repository. Please try the following: dnf config-manager --set-enabled crb dnf install epel-release dnf install sox > Jerry > > _______________________________________________ > AlmaLinux Users mailing list -- users(a)lists.almalinux.org > To unsubscribe send an email to users-leave(a)lists.almalinux.org > -- Stephen J Smoogen. Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren

1 0

Install sox in 9.6
by Jerry Geis 21 May '25

21 May '25

I do the following command to install sox and get an error: yum install sox Last metadata expiration check: 0:13:27 ago on Wed May 21 08:00:40 2025. No match for argument: sox Error: Unable to find a match: sox what? how do I install sox ? I tried dnf also Jerry

1 1

tftp not working on almalinux 9
by Jerry Geis 20 May '25

20 May '25

Hi - I followed these steps: https://computingforgeeks.com/setup-tftp-server-on-centos-rhel-rocky-linux/ now I get this: systemctl status tftp-server.service × tftp-server.service - Tftp Server Loaded: loaded (/etc/systemd/system/tftp-server.service; enabled; preset: disabled) Active: failed (Result: resources) TriggeredBy: ○ tftp-server.socket Docs: man:in.tftpd CPU: 0 May 20 08:27:27 VMWare.lsi.com systemd[1]: tftp-server.service: Cannot add dependency job, ignoring: Unit tftp-server.socket has a bad unit file setting. May 20 08:27:28 VMWare.lsi.com systemd[1]: tftp-server.service: Got no socket. May 20 08:27:28 VMWare.lsi.com systemd[1]: tftp-server.service: Failed to run 'start' task: Invalid argument May 20 08:27:28 VMWare.lsi.com systemd[1]: tftp-server.service: Failed with result 'resources'. May 20 08:27:28 VMWare.lsi.com systemd[1]: Failed to start Tftp Server. this is my file after removing start arguments: more tftp-server.service [Unit] Description=Tftp Server Requires=tftp-server.socket Documentation=man:in.tftpd [Service] ExecStart=/usr/sbin/in.tftpd /tftpboot StandardInput=socket [Install] WantedBy=multi-user.target Also=tftp-server.socket STill does not start. What are the correct steps for setting up TFTP . Thank you. Jerry

1 0

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