Discuss December 2022

discuss@lists.centos.org

13 participants
11 discussions

SSD for Centos SWAP /tmp & /var/ partition
by Keith Roberts 03 Sep '25

03 Sep '25

Has anyone actually used a SSD in a Centos setup? My little experiment with a s/h WD drive for /tmp and SWAP partitions kicked the bucket on Wednesday, when the poor WD drive caught the click-of-death. It was a s/h drive to start with and lasted about 4 months. But that was without the /var/log/ partition being written to it, as I mounted that back onto /var/log from the original drive. So I had to install another (WD) drive, and repartion it and rebuild my RPM package database, from the backed-up Packages file. That seems to be all OK now. I'm wondering if it would be a good idea to use a new SSD for moving all the disk i/o to, that Linux likes to do so often. Plus putting SWAP onto a decent SSD should speed things up somewhat. Here's a short video of a laptop fitted with a SSD drive booting macOS, compared to a similar laptop booting from the standard HDD. The laptop with the SSD boots and loads some apps in 28 seconds. The other one takes twice as long. http://eshop.macsales.com/shop/SSD/OWC/Mercury_Extreme_Pro_6G/?utm_source=t… Kind Regards, Keith Roberts ----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------

33 96

Problems with CentOS 8 kickstart
by Hooton, Gerard 23 Jun '25

23 Jun '25

Hi All, I am having problems with a kickstart install of CentOS 8 When I try to do a completely automated install using PXE/UEFI it get to the point where it reads the kickstart config file. Then I see the following message "kickstart install Started cancel waiting for multipath siblings for nvme0n1" This is what I have in the kickstart file # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel autopart --nohome --type=lvm --fstype=xfs ================ When I install from a USB drive it works OK and I have the following in /dev/disk/by-id lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810 -> ../../nvme0n1 lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-eui.002538b11102f46d -> ../../nvme0n1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 lvm-pv-uuid-5Dg4mg-saHa-hJJ6-n5a8-MxBS-gdFi-5jPoNn -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part2 UNG_MZVL2512HCJQ-0-> ../../nvme0n1p2 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part2 -> ../../nvme0n1p2 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part2 -> ../../nvme0n1p2 drwxr-xr-x. 2 root root 400 Jul 5 10:28 . lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKtEdtLjwJQyIdxJcSvPv8TEAjwYGMv6yU -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKAooqrczySYJyiHvUAUji9oScPN2cVi7J -> ../../dm-1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-swap -> ../../dm-1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-root -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkK5HZXbR2ow5xKGuD7jVe4UPzZm2qRLLXI -> ../../dm-2 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-home -> ../../dm-2 It's looks like that I am not doing the disk drive stuff in the config file correctly. -- Gerard Hooton. Senior Technical Officer School of Engineering. University College Cork. College Road. Cork. Ireland. Loc8: WDR-04-60G Tel: +353 21 4902296 Mobile: +353 852813491

3 7

Issues booting centos7 [dracut is failing to enable centos/root, centos/swap LVs]
by Yannis Milios 01 Feb '25

01 Feb '25

Hello, I'm having a strange problem booting a new centos7 installation. Below some background on this. [I have attached the tech details at the bottom of this message] I started a new CentOS7 installation on a VM, so far all good, o/s boots fine. Then I decided to increase VM disk size (initially was 10G) to 13G. Powered off the VM, increased the vhd via the hypervisor, booted from CentOS livecd, selected "recover my centos installation". Then I used the following sequence of commands to make the new vhd size "visible" to the o/s ... - ran fdisk /dev/sda and deleted partition 2. (This is the LVM partition where the o/s is stored. The first partition is /boot [xfs] partition *non lvm*.) - created a new partition with same starting sector as before deleting it, but a different ending sector (to reflect to the increased space). - set partition type to 8e (lvm), saved settings and exit. - ran pvresize and lvresize to make new space visible to the o/s.All good, I can see the space increase on 'lvdisplay centos/root'. - ran 'mount /dev/mapper/centos-root /mnt/root' to temporarily mount the o/s partition. - ran 'xfs_growfs /mnt/root' to resize the o/s fs to the new size. It was successful and I could actually chroot to the o/s and verify new disk size. - rebooted and tried to boot from hdd this time. Grub menu shows up and loads default kernel (3.10.0-862.9.1.el7.x86_64). - after initial kernel boot up process, booting continues to initrd and then it's where the problem starts... - looks like dracut has issues locating/enabling /dev/mapper/centos-root (lv) and as a result it cannot boot to the 'real' root fs (/). - while in dracut shell, I execute the following command sequence: 1. lvm lvchange -ay /dev/centos/root 2. lvm lvchange -ay /dev/centos/swap 3. ln -s /dev/mapper/centos-root /dev/root 4. exit ...and the o/s boots fine...so looks like the pv,vg,lv is detected properly while in initrd, but somehow dracut has difficulties enabling the root,swap LVs ? - While in o/s, I rebuild initrd by using: 'dracut -f -v -a lvm' Note, I have to use '-a lvm' as for some reason, if don't, the lvm utils (lvm,lvm_scan) are not being included to the initrd, not sure why this happens. After rebooting, same thing happens, I have to manually boot the system via dracut shell. I'm a bit stuck at this point, any clues what I'm doing wrong in here ? As I previously said, this is a new installation, so I could simply reinstall the whole thing, but I would rather try to find out some answer to why is this happening ... :-) [curiosity] Some additional details: ================== I've attached /run/initramfs/rdsosreport.txt file [generated while in inird] here: https://privatebin.net/?fdc4052c0c402884#gdB/QYR3IeR55SxUbjfrkZPQfJ7jMxiUxq… o/s ver=CentOS Linux release 7.5.1804 (Core) [root@localhost ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 13G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 8:2 0 12.5G 0 part ├─centos-root 253:0 0 11.5G 0 lvm / └─centos-swap 253:1 0 1G 0 lvm [SWAP] [root@localhost ~]# cat /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rd.shell rhgb" GRUB_DISABLE_RECOVERY="true"

4 11

Apache mpm itk
by Gionatan Danti 17 May '23

17 May '23

Hi all, the EPEL repository for CentOS7 contains httpd-itk, an apache module for running different vhosts under specific user/group ID. For RHEL8 I can find it only in 3rd party repos, while I misses it entirely for RHEL9. Is the module deprecated? Can it be re-included into EPEL? Regards. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

2 3

Re: [CentOS] Trouble with kernel-3.10.0-1160.80.1.el7.x86_64
by Petko Alov 11 Mar '23

11 Mar '23

> > On 2022-11-08 15:49, Orion Poplawski wrote: > > On 11/8/22 13:12, Simon Matter wrote: > > Is anyone else experiencing trouble with > kernel-3.10.0-1160.80.1.el7.x86_64? > > I'm seeing a kernel panics in the kvm module on one of our VM hosts with > > it. > > I did notice a new libvirt update as well, but it seems to work fine with > > the > older kernel (.76.1). > > Where did you get the .80.1 kernel from? I'm a bit confused because I can > > only see .76.1 on my systems. > > Simon > > I'm actually running Scientific Linux, which seems to be a little ahead here. > > Probably not related, but vmlinuz-4.18.0-372.32.1.el8_6.x86_64 (AlmaLinux 8.6) had a kernel panic > on a Intel Xeon E5504 processor, but works fine on Xeon E56XX processors (5620 specifically in our > tests). * Believe from kernel version, the original email is for Centos 7, possible the same > change that went into the EL8 kernel went also to EL7 Triggered right after I used virsh start to > start the vm. (Caused Black Screen, and reboot. Found this in the crashed kernel logs on > /var/crash) Works fine on vmlinuz-4.18.0-372.26.1.el8_6.x86_64 and > vmlinuz-4.18.0-372.16.1.el8_6.x86_64 In fact, related - on our systems attempt to start qemu-kvm VM under kernel-3.10.0-1160.80.1.el7.x86_64 freezes any of 5 workstations with dual E5507 (all worked OK under kernel-3.10.0-1160.76.1.el7.x86_64 and any previous version). The workstations with E5-2609, E5-2650 or E5-2630 are not affected - all of them run qemu-kvm VM under kernel-3.10.0-1160.80.1.el7.x86_64 without problems. Any ideas? Regards, Petko -- Petko Alov Department of QSAR & Molecular Modelling Institute of Biophysics and Biomedical Engineering, BAS 21 G. Bontchev Str 1113 Sofia, BULGARIA

4 5

Re: [CentOS] dnf-makecache.service failing every few days and dnf-automatic.service samba sssd issues (again).
by Jelle de Jong 09 Feb '23

09 Feb '23

Hello everybody, Could someone give me an estimate on when the repositories are resolving the right dependencies for the freeipa pacakges in CentOS Stream release 8? I have about +10 systems sending me alerts everyday that dnf-automatic.service is failing because of the freeipa dependency issues. Since freeipa is one of the security elements I would like to give people an estimate on when these issues are resolved? How can I keep track of the work that is been done as well? Is there a package tracker to be followed for this? URLs? I asked this question on the centos-devel list weeks ago, but have not received any feedback. The issues is bothering me a lot as it is an security issue that stays unresolved. Kind regards, Jelle de Jong On 11/30/22 13:06, Jelle de Jong wrote: > Hello everybody, > > I attached the dnf conflict logs with conflicting pacakges. > > Problem 1: package > ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 > requires libndr.so.2()(64bit), but none of the providers can be installed > Problem 2: package > ipa-server-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 requires > libsamba-errors.so.1(SAMBA_ERRORS_1)(64bit), but none of the providers > can be installed > Problem 3: problem with installed package > ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 > Problem 4: problem with installed package > ipa-server-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 > > Kind regards, > > Jelle > > > On 11/29/22 12:43, Jelle de Jong wrote: >> Hello everybody, >> >> 1. I got many systems with failing dnf-makecache.service because some >> mirror/repo is tried once and fails. >> >> Is there an option to make dnf more reliable, to try the mirror url a >> few times and check its availability? >> >> man yum.conf does not >> >> # cat /etc/yum.conf >> [main] >> gpgcheck=1 >> installonly_limit=3 >> clean_requirements_on_remove=True >> best=True >> skip_if_unavailable=False >> >> ExecStart=/usr/bin/dnf makecache --timer >> >> 2. I saw in the mailing list the messages about samba sssd dependency >> issues. I got lots of servers failing my dnf-automatic because of this >> when can I expect a resolution for this? >> >> Kind regards, >> >> Jelle

3 5

CentOS Stream 8 sssd.service failing part of sssd-common-2.8.1-1.el8.x86_64 baseos package
by Jelle de Jong 19 Jan '23

19 Jan '23

Hello everybody, A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is causing sssd.service systemctl failures all over my CentosOS machines. What is the best way to report this issue and when can we expect an update from the sssd-common package for this regression bug? I think sssd-common is part of the baseos repository and installed even when the configuration file is not installed. If someone can also provide more details on this issue I would appreciate it. Thank you all in advance, Kind regards, Jelle de Jong # cat /var/log/dnf.log | grep sssd-common 2022-11-25T06:29:42+0100 DEBUG Upgraded: sssd-common-2.7.3-5.el8.x86_64 2022-11-25T06:29:42+0100 DDEBUG /var/cache/dnf/baseos-055ffcb2ec25a27f/packages/sssd-common-2.7.3-5.el8.x86_64.rpm removed 2022-11-26T06:08:38+0100 DEBUG Upgraded: sssd-common-2.7.3-5.0.1.el8.x86_64 2022-11-26T06:08:38+0100 DDEBUG /var/cache/dnf/baseos-055ffcb2ec25a27f/packages/sssd-common-2.7.3-5.0.1.el8.x86_64.rpm removed 2022-12-25T06:23:42+0100 DEBUG Upgraded: sssd-common-2.8.1-1.el8.x86_64 2022-12-25T06:23:43+0100 DDEBUG /var/cache/dnf/baseos-055ffcb2ec25a27f/packages/sssd-common-2.8.1-1.el8.x86_64.rpm removed # cat /etc/os-release NAME="CentOS Stream" VERSION="8" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="8" PLATFORM_ID="platform:el8" PRETTY_NAME="CentOS Stream 8" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:8" HOME_URL="https://centos.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 8" REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream" # cat /var/log/sssd/sssd.log (2022-12-25 6:23:34): [sssd] [monitor_quit_signal] (0x3f7c0): Monitor received Terminated: terminating children (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Returned with: 0 (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Terminating [nss][302626] (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Child [nss] terminated with a signal (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Terminating [implicit_files][302625] (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Child [implicit_files] terminated with a signal [sssd] [confdb_expand_app_domains] (0x0010): No domains configured, fatal error! [sssd] [get_monitor_config] (0x0010): Failed to expand application domains [sssd] [confdb_get_domains] (0x0020): No domains configured, fatal error! [sssd] [get_monitor_config] (0x0010): No domains configured. [sssd] [main] (0x0010): SSSD couldn't load the configuration database [1432158246]: No domain is enabled # cat /var/log/sssd/sssd.log (2022-12-25 6:23:34): [sssd] [monitor_quit_signal] (0x3f7c0): Monitor received Terminated: terminating children (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Returned with: 0 (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Terminating [nss][302626] (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Child [nss] terminated with a signal (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Terminating [implicit_files][302625] (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Child [implicit_files] terminated with a signal [sssd] [confdb_expand_app_domains] (0x0010): No domains configured, fatal error! [sssd] [get_monitor_config] (0x0010): Failed to expand application domains [sssd] [confdb_get_domains] (0x0020): No domains configured, fatal error! [sssd] [get_monitor_config] (0x0010): No domains configured. [sssd] [main] (0x0010): SSSD couldn't load the configuration database [1432158246]: No domain is enabled # systemctl status sssd ● sssd.service - System Security Services Daemon Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2022-12-25 06:23:35 CET; 9h ago Main PID: 615303 (code=exited, status=4)

5 13

Installing multiple rpm binary files using yum or dnf package manager.
by Kaushal Shriyan 27 Dec '22

27 Dec '22

Hi, I am running CentOS Linux release 7.9.2009 (Core) and have a few rpms inside a specific folder. I know it is possible using rpm command to install multiple rpm binary files using the below command. #cd rpmbinaries #rpm -ivh *.rpm Is there a way to install them using dnf or yum package manager? I have php81-php-pecl-zip-1.21.1-1.el7.remi.x86_64 rpm, is there a way to find the dependencies rpm required before installing? Please guide me. Thanks in advance. Best Regards, Kaushal

2 1

CentOS7 latest kernel still does not run KVM guests
by Bill Gee 27 Dec '22

27 Dec '22

The two latest kernels for CentOS7 are complete fails for running KVM and QEMU guest machines. Version 3.10.0-1160.76.1 works correctly. Both 3.10.0-1160.80.1 and 3.10.0-1160.81.1 will hang within seconds of launching any virtual machine. It is a HARD hang. I have to pull the power cord from the computer in order to regain control. Since 81.1 came out within the last few days, I assumed it would contain a fix for this problem. It does not. Does anyone know when a kernel will be released that fixed this problem? -- =============== Bill Gee

5 7

No kernel-modules for 5.14.0-210 - Centos Stream 9 Vagrant Box
by Daniel Hiller 14 Dec '22

14 Dec '22

Hi everyone, we are using https://cloud.centos.org/centos/9-stream/x86_64/images/CentOS-Stream-Vagran… together with http://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/images/pxeboot/in… http://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/images/pxeboot/vm… to create a vm inside a container. (Why we are doing this would be a longer story BTW) During the process of configuring the VM we are installing kernel-modules dnf install -y "kernel-modules-$(uname -r)" This has worked until around yesterday afternoon. Now it's failing with No match for argument: kernel-modules-5.14.0-210.el9.x86_64 Error: Unable to find a match: kernel-modules-5.14.0-210.el9.x86_64 What we noticed was that this occurred after the kernel had changed from 5.14.0-205. I suspect that this might be related to vmlinuz and/or initrd.img updates, since I've seen those having changed on 9th / 12th of Dec 2022. Does someone have an idea on how we can fix this in the short run? Or do we need to wait for "someone" to fix it, and who would that be? Thanks in advance, Daniel Hiller

1 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss December 2022