June 2024 - AlmaLinux Users - AlmaLinux List Archives

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

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

23 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

RPM creation problem
by Alessandro Baggi 26 Jul '24

26 Jul '24

Hi list, I'm creating an RPM package for gocryptfs on AlmaLinux 9.3 I'm using the source with deps (vendoring) because deps are too much. During the process rpmbuild returns: gocryptfs-debugsource-2.4.0-1.el9.x86_64 error: Empty %files file /root/rpmbuild/BUILD/gocryptfs_v2.4.0_src-deps/debugsourcefiles.list To avoid this I can add: %global debug_package %{nil} and the problem is solved also if the build-id links are generated. But, here there is a problem. I read that for $arch packages a debug package will be created and if some error is reported there is something wrong on the SPEC file. Why debugsourcefiles.list is empty? What is causing this? Thank you in advance. Alessandro.

3 4

AlmaLinux 9 and XFCE sound problem
by Alessandro Baggi 02 Jul '24

02 Jul '24

Hey there, I installed Almalinux OS 9 on my notebook. I installed XFCE but I'm getting problem with audio because xfce4-pulseaudio plugin is missing and I can't change sound volume except on the specific program that play the music (In my case audacious and firefox). Currently I don't know if I must open a "please build xfce4-pulseaudio-plugin" on epel or if I should use something due to pipewire. I enabled also epel-testing to check if the package was in testing but seems missing. Someone has the same problem? Thank you in advance.

5 5

OpenSSH policies / system crypto policy equivalence
by Francesco Di Nucci 20 Jun '24

20 Jun '24

Hello, I am trying to write a crypto policy modifier to disable some kex algorithms in OpenSSH (not the one in the example, but the issue is the same). Reading //usr/share/crypto-policies/python/policygenerators/openssh.py/, I find mappings like /'ECDHE-SECP521R1-SHA2-512': 'ecdh-sha2-nistp521'/, so I tried to write in a pmod /key_exchange = -ECDHE-SECP521R1-SHA2-512/ When I try to load it with update-crypto-policies, it fails stating /Bad value of policy property `key_exchange`: `ECDHE-SECP521R1-SHA2-512`/, and in fact If I check //usr/share/crypto-policies/python/cryptopolicies/alg_lists.py, /ECDHE-SECP521R1-SHA2-512 is not defined there. So, how can I disable in OpenSSH kex/algorithms/etc that are defined in //usr/share/crypto-policies/python/policygenerators/openssh.py /but not in //usr/share/crypto-policies/python/cryptopolicies/alg_lists.py?/ Best regards Francesco Di Nucci

1 0