Discuss January 2022

discuss@lists.centos.org

41 participants
34 discussions

NFS Share fails to mount at boot time
by Felix Natter 15 Jan '22

15 Jan '22

hello fellow CentOS Users, on Scientific Linux 7 (_very_ similar to CentOS7), I get this when trying to mount NFS Shares (exported from Synology NAS) automatically at boot time: [root@HOST ~]# journalctl -b 0 | grep NAS[20] Jul 01 13:32:09 HOST systemd[1]: Mounting /mnt/NAS0... Jul 01 13:32:09 HOST systemd[1]: Mounting /mnt/NAS2... Jul 01 13:32:09 HOST systemd[1]: mnt-NAS0.mount mount process exited, code=exited status=32 Jul 01 13:32:09 HOST systemd[1]: Failed to mount /mnt/NAS0. Jul 01 13:32:09 HOST systemd[1]: Unit mnt-NAS0.mount entered failed state. Jul 01 13:32:09 HOST systemd[1]: mnt-NAS2.mount mount process exited, code=exited status=32 Jul 01 13:32:09 HOST systemd[1]: Failed to mount /mnt/NAS2. Jul 01 13:32:09 HOST systemd[1]: Unit mnt-NAS2.mount entered failed state. I read that enabling NetworkManager-wait-online.service can mitigate that, but it's already enabled: [root@HOST ~]# systemctl list-unit-files|grep wait chrony-wait.service disabled NetworkManager-wait-online.service enabled plymouth-quit-wait.service disabled /mnt/NAS2 is defined in /etc/fstab (/mnt/NAS0 is mounted analogously): NAS2HOST:/volume1/export/ /mnt/NAS2 nfs rw,vers=3,soft,bg,intr 0 0 This does not always occur, and it seems to be a race condition, because it did not occur a few months ago, before we moved offices (when only the networking changed slightly). Of course, once the computer is booted, I can always mount the shares without problems. Does someone have an idea? Many Thanks and Best Regards, -- Felix Natter

3 4

Possible openssl-1.0.2k-23.el7_9 issue
by Johnny Hughes 14 Jan '22

14 Jan '22

I am working to release an update set for CentOS Linux 7, it contains openssl-1.0.2k-23.el7_9, which has this bug reported: https://bugzilla.redhat.com/show_bug.cgi?id=2039993 There is also this article: https://access.redhat.com/solutions/6637201 (requires an access.redhat.com subscription) The current update set is currently in QA testing. It may fail and not be able to be released .. in which case we wouuld remove openssl and try again to get it to pass tests. I just wanted to get this out there in case anyone has issues. Thanks, Johnny Hughes

1 1

389-ds packages less up-to-date on CentOS Stream 8 than RHEL8
by Mathieu Baudier 14 Jan '22

14 Jan '22

Hello, as described here [1] we were having issues with LDAP dirsrv 389-ds in our environment where we use a mix on CentOS Stream 8 and RHEL 8 deployments. I have been surprised to notice that RHEL packages actually seems to be more up-to-date than CentOS Stream ones, while we are working for our QA processes under the assumption that CentOS Stream is upstream of RHEL. Looking at the package versions: ## RHEL 8 $ sudo dnf info 389-ds-base Name : 389-ds-base Version : 1.4.3.23 Release : 12.module+el8.5.0+13329+4096c77a $ sudo rpm -q --changelog 389-ds-base * Thu Nov 18 2021 Mark Reynolds <mreynolds(a)redhat.com> - 1.4.3.23-12 ## CentOS Stream 8 $ sudo dnf info 389-ds-base Name : 389-ds-base Version : 1.4.3.23 Release : 10.module_el8.5.0+946+51aba098 $ rpm -q --changelog 389-ds-base * Thu Aug 26 2021 Mark Reynolds <mreynolds(a)redhat.com> - 1.4.3.23-10 My understanding from discussion on this mailing-list a few months ago, is that sometimes critical issues will be patched in RHEL before CentOS Stream, which is understandable. But is it to be expected that there can be a lag of many months before CentOS Stream "catches up"? Is it recommended to use CentOS Stream for development and testing of the upcoming RHEL updates? Just to be clear, as a (tiny) Red Hat Partner, we have access to enough RHEL NFR entitlements for such purposes, so the point here is not to get something "for free", but to "see things coming" by developing and testing primarily on CentOS Stream. (Which, by the way is working great, except for these recurring 389-ds and IPA issues; I have also been using it as my workstation for months without a glitch) Thanks in advance for (constructive) comments, and for sharing your own experience! Cheers, Mathieu [1] https://lists.centos.org/pipermail/centos/2021-November/534847.html

2 3

Kernel live patching on CentOS Stream 9
by Gionatan Danti 14 Jan '22

14 Jan '22

Dear all, is kernel live patching working for CentOS Stream 9? I know that I can enable it via cockpit or the command line, but are kernel patch files really available or do they require an active RHEL subscription? Thanks. -- 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

7 16

HP Microserver Gen 10+ video RHEL8
by Jon LaBadie 14 Jan '22

14 Jan '22

I'm considering using an HP Proliant Microserver Gen 10+ with a Xeon processor. With the lower level Pentium processor, the CPU and chipset include Intel 610 graphics. But I can not find any info on any builtin video capability of the Xeon provisioned models. Has anyone used these models with Stream (8 or 9) and can describe the video capability? I'd like to do basic X-windows for the occasional GUI admin tool. Thanks, Jon -- Jon H. LaBadie jcu(a)labadie.us

2 1

rd.lvm.lv on CentOS Stream 9 (first-boot failure)
by Gordon Messmer 14 Jan '22

14 Jan '22

I've install a CentOS Stream 9 system from a kickstart file that specified (among other things) several logical volumes: logvol / --fstype="ext4" --size=10240 --name=lv_root --vgname=VolGroup logvol /var --fstype="ext4" --size=4096 --name=lv_var --vgname=VolGroup logvol swap --fstype="swap" --size=2048 --name=lv_swap --vgname=VolGroup When that system rebooted, the kernel args did specify "rd.lvm.lv=VolGroup/lv_root rd.lvm.lv=VolGroup/lv_swap", but did not specify "rd.lvm.lv=VolGroup/lv_var", so boot failed because the filesystem required for /var couldn't be found. The dracut.cmdline documentation does record that it will only activate the LVs given as "rd.lvm.lv", but I'm confused about several things. 1: The system also includes a volume group named "BackupGroup" and that group activates on boot (post-dracut). Why are those LVs activated when rd.lvm.lv is specified? 2: Why didn't Anaconda add the "var" LV to the kernel arguments? 3: This seems like a change from earlier releases, but I can't find any documentation to that effect. Under CentOS 7, after dracut had finished, the remaining logical volumes in that group would be activated. Because they aren't, currently, libvirtd cannot start any of its guests until I manually activate the group. How can I restore the old behavior of activating all of the LVs on boot?

2 2

Moving from mdadm raid 0 to single disk
by Alexandre Leonenko 12 Jan '22

12 Jan '22

Hey all, Hopefully a quick question. I'm going to move the filesystem of a raid 0 mdadm to a single disk. The filesystem is just a data drive, can I just dd if=/dev/md0 of=/dev/sdc ? Or should I rather rsync the files directly? Regards, Alex

3 4

systemctl hoses eth port settings
by allan emord 10 Jan '22

10 Jan '22

Hi all, I recently added 2 eth ports to C7 machine via USB adapters. Set up devices with Settings - Network . While cables (and target devices) are installed, running `systemctl restart network` worked OK. If one of the devices loses connectivity (e.g. uplug eth cable) `systemctl restart network` will mix up the device assignments thereby losing connectivity to host. e.g. enp7s0, the PCI network card, gets set to parameters that belong to one of the USB adapters. This is not desired behavior. Is there something I have done incorrectly? I this normal behavior? I have looked at the scripts for if[up|down], and if run manually, works well to re-configure the enp7s0 interface but (apparently) systemctl does not use these scripts. Thanks for your consideration. Allan

1 0

Is my ssh private key already unlocked?
by Robert Nichols 10 Jan '22

10 Jan '22

When I first ssh to a system, I am asked for the password to unlock the private key file. Thereafter, that key file remains unlocked, and subsequent ssh sessions will not prompt for a password. I can always re-lock the key file by running "ssh-add -D". In a script I have that runs sshfs to mount a remote directory, I want to re-lock that key file _unless_ it was already unlocked, i.e., if I sshfs asks for a password, I want to re-lock the key file immediately after the command is run. How can I determine ahead of time whether the key file is already unlocked? In the past (Centos 6) I could examine the output from "ssh-add -l" determine that. Now, "ssh-add -l" just shows the public key whether of not the private key has been unlocked. There is also no apparent way to see whether or not sshfs asked for a password. Suggestions? -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it.

2 2

printing on C8S
by Fred 08 Jan '22

08 Jan '22

OK, I give up. How do I configure a printer on Centos 8 Stream? I can't find any tools for doing that. further, there doesn't seem to be a cups executable (which should allow setting up a printer) though there ARE a bunch of cups packages installed. Anyone got any clues for me? Thanks in advance! Fred

6 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2022