- AlmaLinux Users - AlmaLinux List Archives

Re: Ansible version
by Gerald Vogt 08 Jul '25

08 Jul '25

On 08.07.25 16:25, Nicolas Kovacs via AlmaLinux Users wrote: > Le 08/07/2025 à 16:03, Gerald Vogt via AlmaLinux Users a écrit : >> ansible is not part of RHEL nor AlmaLinux. It's in EPEL. > > This is particularly ironic given the fact that Red Hat bought Ansible > back in 2015 if I remember correctly. Why? They have integrated ansible as package ansible-core into their system. ansible-core is part of RHEL and AlmaLinux. The package ansible, however, is from EPEL and based on the community version. Anything beyond is just names. -Gerald

1 0

Re: Ansible version
by Nicolas Kovacs 08 Jul '25

08 Jul '25

Le 08/07/2025 à 16:03, Gerald Vogt via AlmaLinux Users a écrit : > ansible is not part of RHEL nor AlmaLinux. It's in EPEL. This is particularly ironic given the fact that Red Hat bought Ansible back in 2015 if I remember correctly. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

1 0

Re: Ansible version
by Gerald Vogt 08 Jul '25

08 Jul '25

Hi, On 08.07.25 15:34, Werf, C.G. van der (Carel) via AlmaLinux Users wrote: > Does anybody know why version-numbers of packages Ansible and Ansible-core are higher from Alma 8.10 repositories, than from Alma 9.6 repositories Because RedHat did it so: https://www.redhat.com/en/blog/updates-using-ansible-core-in-rhel > Alma8 -> Ansible-core 2.16, Ansible 9.2.0 > Alma9 -> Ansible-core 2.14, Ansible 7.7.0 ansible is not part of RHEL nor AlmaLinux. It's in EPEL. What version you'll find in EPEL depends very much on the maintainer. -Gerald

1 0

Ansible version
by Werf, C.G. van der (Carel) 08 Jul '25

08 Jul '25

Hi, Does anybody know why version-numbers of packages Ansible and Ansible-core are higher from Alma 8.10 repositories, than from Alma 9.6 repositories Alma8 -> Ansible-core 2.16, Ansible 9.2.0 Alma9 -> Ansible-core 2.14, Ansible 7.7.0 Regards, Carel van der Werf

1 0

Re: XFCE Missing Volume Control Plugin on AlmaLinux 9
by John Thompson 25 Jun '25

25 Jun '25

On 6/24/25 07:26, David Eric via AlmaLinux Users wrote: > Hi everyone, > I’ve installed AlmaLinux 9 with XFCE on my notebook, but I noticed the xfce4-pulseaudio-plugin is missing. As a result, I can’t control the system volume directly—only through individual apps like Audacious or Firefox. > I checked EPEL and even enabled epel-testing, but couldn’t find the package. Should I file a request for the plugin in EPEL, or is there a better solution considering AlmaLinux 9 uses PipeWire? > As a temporary fix, I’m considering using pavucontrol, but I’d love to hear how others are handling this. > Thanks in advance! I downloaded the source code for xfce4-pulseaudio-plugin_0.4.8 and built the plugin from that. Not sure why it wasn't included by default. -- -John (JohnDThompson(a)gmail.com) Appleton, WI USA

1 0

XFCE Missing Volume Control Plugin on AlmaLinux 9
by nguyenthuu30031999＠gmail.com 24 Jun '25

24 Jun '25

Hi everyone, I’ve installed AlmaLinux 9 with XFCE on my notebook, but I noticed the xfce4-pulseaudio-plugin is missing. As a result, I can’t control the system volume directly—only through individual apps like Audacious or Firefox. I checked EPEL and even enabled epel-testing, but couldn’t find the package. Should I file a request for the plugin in EPEL, or is there a better solution considering AlmaLinux 9 uses PipeWire? As a temporary fix, I’m considering using pavucontrol, but I’d love to hear how others are handling this. Thanks in advance!

1 0

Autofs: too many open files issue
by Carles Acosta Silva 31 May '25

31 May '25

Hi, We are running AlmaLinux 9.3 on several nodes that normally use autofs to mount different kinds of remote directories. Since the last week, we are seeing these errors: automount[2150866]: open_pipe:161: failed to open pipe: Too many open files And automount stops working. It does not seem that any user has arrived at the maximum number of open files. Do you have any idea where we can look to find a solution? Thank you in advance. Best regards, Carles

5 5

Re: tftp not working on almalinux 9
by Gerald Vogt 31 May '25

31 May '25

On 20.05.25 15:31, Jerry Geis via AlmaLinux Users wrote: > Hi - > > I followed these steps: > https://computingforgeeks.com/setup-tftp-server-on-centos-rhel-rocky- > linux/ <https://computingforgeeks.com/setup-tftp-server-on-centos-rhel- > rocky-linux/> Don't do that. Those instructions are often from people who really don't understand what they are doing. Step 2 messes everything totally up. Someone doesn't understand how systemd works and how to overwrite unit files... > 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 <http://VMWare.lsi.com> systemd[1]: tftp- > server.service: Cannot add dependency job, ignoring: Unit tftp- > server.socket has a bad unit file setting. As the error says: your tftp-server.socket is broken. Which probably comes because of step 2 above. # systemctl cat tftp-server.socket will show the content of the active configuration. > May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- > server.service: Got no socket. > May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- > server.service: Failed to run 'start' task: Invalid argument > May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- > server.service: Failed with result 'resources'. > May 20 08:27:28 VMWare.lsi.com <http://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. Yes. Changing that file doesn't make sense either. The tftp-server.socket unit is broken. > What are the correct steps for setting up TFTP . The correct steps are fairly simple: # dnf -y install tftp-server # systemctl enable --now tftp.socket That's all what is necessary to get it running. After it's running, make necessary changes if you need something different. But that's done via the standard systemd overrides and not by putting different files with different names into /etc/systemd/system... I would recommend in your current setup to remove those copied files # /bin/rm /etc/systemd/system/tftp-server.service # /bin/rm /etc/systemd/system/tftp-server.socket # systemctl daemon-reload # systemctl enable --now tftp.socket And then check if you can access it... -Gerald

2 1

Re: Virtualbox fail with new almalinux kernel
by John Thompson 22 May '25

22 May '25

On 5/22/25 11:45, John Thompson via AlmaLinux Users wrote: > My almalinux-9.6 just updated to kernel 5.14.0-570.12.1.el9_6.x86_64 #1 > and Virtualbox can no longer load my virtual machines, failing with this > error: > > VirtualBox can't operate in VMX root mode. Please disable the KVM kernel > extension, recompile your kernel and reboot > > Anybody else seeing this? Following up on this, using rmmod to unload the kvm and kvm_intel kernel modules allows VirtualBox to load my virtual machines, but that still begs the question "why did this happen?" Looking at the .config files for the current and older kernels I have on my almalinux machine (5.14.0-503.38.1.el9_5.x86_64, 5.14.0-503.40.1.el9_5.x86_64, and 5.14.0-570.12.1.el9_6.x86_64), I see that CONFIG_X86_VMX_FEATURE_NAMES=y and CONFIG_VMXNET3=m are set in all of them, so why does it fail with VirtualBox only in the latest kernel? And does almalinux support a module blacklist in /etc/modprobe.d to prevent the kvm modules from loading in future reboots? -- -John (JohnDThompson(a)gmail.com) Appleton, WI USA

1 0

Virtualbox fail with new almalinux kernel
by John Thompson 22 May '25

22 May '25

My almalinux-9.6 just updated to kernel 5.14.0-570.12.1.el9_6.x86_64 #1 and Virtualbox can no longer load my virtual machines, failing with this error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot Anybody else seeing this? -- -John Thompson (johndthompson(a)gmail.com) Appleton WI USA

1 0