- AlmaLinux Users - AlmaLinux List Archives

Autofs: too many open files issue
by Carles Acosta Silva 25 Nov '24

25 Nov '24

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

4 4

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

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

Almalinux 9.4 import LVM VG bug?
by Alessandro Baggi 08 Sep '24

08 Sep '24

Hi list, on my Almalinux 9.4 I tried to import LVM Volume Group from another system. When I attached disks on my workstation, pvscan or vgimport does not found any lvm devices. Reading here: https://discussion.fedoraproject.org/t/lvm-operations-might-fail-on-a-fedor… seems that renaming /etc/lvm/devices/system.devices permits the system to read lvm devices and able to import an existing volume. This is a bug or a wanted behaviour? File system.devices is required? I should restore it? Thank you in advance Alessandro.

2 2

Where are the archives for: users@lists.almalinux.org ?
by Mike Schleif 29 Aug '24

29 Aug '24

I just signed up and I want to see if my questions are already answered. TY

2 1

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

there is a strange delay in my work on the Almalinux forum - what should I do?
by Mikhail Kuzminsky 02 Jul '24

02 Jul '24

I registered on the forum yesterday and sent a message. Today I go to the forum (general) - my message has not appeared yet. And I cannot answer to the message (from another forum user) about a problem: I don't see any answer icon. My username on the forum is mbkus (with my other e-mail). I don't see any way to contact the forum manager. Mikhail

2 1

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