Discuss January 2023

discuss@lists.centos.org

36 participants
23 discussions

CentOS9 vs. s-nail
by Bill Gee 20 Jan '23

20 Jan '23

Now that I have a test CentOS9 system set up, I am trying to get it to send me logwatch reports via email. S-nail is proving very frustrating. It almost works ... But not quite! The main problem is bogus characters in the logwatch report. Here is a section of the report I get through email: ================== =20 ################### Logwatch 7.5.5 (01/22/21) ####################=20 Processing Initiated: Thu Jan 19 13:31:57 2023 Date Range Processed: yesterday ( 2023-Jan-18 ) Period is day. Detail Level of Output: 5 Type of Output/Format: email / text Logfiles for Host: centos7.billgee.local ##################################################################=20 =20 --------------------- Kernel Audit Begin ------------------------=20 Number of audit daemon starts: 1=20 =20 **Unmatched Entries** audit: type=3D1403 audit(1674073255.247:3): auid=3D4294967295 ses=3D429= 4967295 lsm=3Dselinux res=3D1: 1 Time(s) auditd[517]: audit dispatcher initialized with q_depth=3D1200 and 1 act= ive plugins: 1 Time(s) =20 ---------------------- Kernel Audit End -------------------------=20 =20 --------------------- Chrony report Begin ------------------------=20 MS Name/IP address Stratum Poll Reach LastRx Last sample = =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D ^* server3.17.168.192.IN-AD> 4 6 377 42 -16us[ -23us] ± 9= 716us Name/IP Address NP NR Span Frequency Freq Skew Offset Std= Dev ================================ What are all those =20 and =30 strings for? How do I make them go away? I have been experimenting with a line in /etc/s-nail.rc. set ttycharset=utf-8 That is the only value for this that produces anything useful. If I set it to charset-7bit or charset-8bit, then s-nail complains about invalid syntax on the "set mta=" line. What???? I just don't get it. Can someone shed some light on this? For what it is worth, a test CentOS8 system using mailx (the REAL mailx!) works perfectly. So do all of my CentOS7 and Fedora systems. -- =============== Bill Gee

3 3

Re: [CentOS] CentOS9 as VBox guest - kernel panic
by Bill Gee 19 Jan '23

19 Jan '23

There were no replies to this question. After digging in a bit, I found a way to make it work. I made two changes, and it is not clear whether one or the other - or both - were needed. Change one - Upgrade to VirtualBox 7.0.6. Among the items listed in the changelog for this version is compatibility with RHEL 9 guests. Change two - In the Settings - Basic screen of the guest I changed its type from "RedHat 64-bit" to "RHEL 9.x 64-bit." The ISO for network install booted and ran through with no errors. Hopefully others can benefit from my experience. =============== Bill Gee On 1/15/23 14:29, Bill Gee wrote: > It is time for me to start figuring out how to get all my C7 machines > upgraded. It is obvious that C7 is pretty much an afterthought anymore ... > > My starting point is to set up a C9 machine as a VirtualBox guest. I > have a VBox machine (currently 6.0.40) which runs C8 Stream on the metal > and has been running well for over a year. It has many different guests > on it including Fedora 37, CentOS7, FreeDOS, Windows and others. > > I downloaded the network installer ISO file for C9, then set up a VB > guest to run it. It boots the ISO for about 5 seconds then gives a > kernel panic. I am attaching a screen shot and hope it survives the > transit through this email list. It is not possible to scrape this as > text and I do not trust myself to type it all correctly. > > Did I miss something bloody obvious in the guest configuration? >

1 0

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

Perhaps trivial problem but important to me
by jefflpost＠twc.com 18 Jan '23

18 Jan '23

I have two computers: CentOS 7 (KDE 4) and CentOS 8 (KDE 5). I'm also an avid Doom player (yeah, I'm an old geezer). On C7 using prboom v 2.5.0 and a graphical interface I wrote to select a wad file to play without using the command line, everything works fine. On C8, using the same prboom 2.5.0, graphical interface, and the same SDL libraries, the video is "jerky" - every 2 seconds or so the video stops for a fraction of a second and then restarts. This makes game play a bit irritating. This problem does not occur when playing videos with mplayer, also using a graphical interface I wrote to select files to play. I've looked at system settings, checked process usage using ps and can find no reason why there is a difference between playing Doom in C7 and C8. Any suggestions will be greatly appreciated. Jeff

1 0

CentOS Stream 9 virt-install via loop-mounted ISO fails
by Jos Vos 17 Jan '23

17 Jan '23

Hi, I've loop-mounted the latest CentOS Stream 9 DVD ISO and try to do a virt-install (2.0.x for some reason) as non-root user (libvirt group member) using --location with the mount path, but then I come across the problem decribed here: https://bugzilla.redhat.com/show_bug.cgi?id=2022630 That is, I see on the console "Starting dracut initqueue hook...", then it stalls for a while, and then I get all the timeouts described in the bug report. Any suggestions for a workaround (with virt-install 2.0.x and as non-root user)? Background: Dor some reason I need to use virt-install 2.0.x as non-root to install CentOS Stream 9. The "normal" way, specifying a URL with --location, does not work because it fails with permission denied for losetup. It looks like virt-install 3.2.x does not have this problem anymore. Thanks, -- -- Jos Vos <jos(a)xos.nl> -- X/OS Experts in Open Systems BV | Office: +31 20 6938364 -- Amsterdam, The Netherlands | Mobile: +31 6 26216181

2 2

Upgrading system from non-RAID to RAID1
by H 15 Jan '23

15 Jan '23

I plan to upgrade an existing C7 computer which currently has one 256 GB SSD to use mdadmin software RAID1 after adding two 4 TB M2. SSDs, the rest of the system remaining the same. The system also has one additional internal and one external harddisk but these should not be touched. The system will continue to run C7. If I remember correctly, the existing SSD does not use a M2. slot so they should be available for the new 4GB SSDs while the old SSD remains in place. If I read the output from gparted correctly, this existing SSD is partitioned as follows: - EFI system partition 260 MB and mounted as /boot/efi (formatted as FAT32). - boot partition 1 GB and mounted as /boot (formatted as xfs). - /root, swap and /home seem to coexist on a LUKS encrypted partitition using LVM2 PV. My current plan is to: - Use clonezilla to make individual backups of all partitions above. - Install the two M2. SSDs. - Use an external disk tool to partition the two new M2. SSDs as follows: -- Create a RAID1 partition for /boot - same size as current, ie 260 MB -- Create a RAID1 partition for /boot/efi - same size as current, ie 1 GB -- Create a RAID1 partition for LVM2 and LUKS - the rest of the 4 TB SSD Questions: - I do not see any benefit to breaking up the LVM2/LUKS partition containing /root, /swap and /home into more than one RAID1 partition or am I wrong? If the SSD fails, the entire SSD would fail and break the system, hence I might as well keep it as one single RAID1 partition, or? - Is the next step after the RAID1 partitioning above then to do a minimal install of C7 followed by using clonezilla to restoring the LVM2/LUKS partition?? - Any advice on using clonezilla? Or the external partitioning tool? - Finally, since these new SSDs are huge, perhaps I should take the opportunity to increase the space for both /root and /swap? - /root is 50 GB - should I increase it to eg 100 GB? - The system currently has 32 GB of memory but I will likely upgrade it to 64 GB (or even 128 GB), perhaps I should at this time already increase the /swap space to 64 GB/128 GB? Looking forward to advice and suggestions!

5 15

Centos Stream 9 module list
by Jos Vos 14 Jan '23

14 Jan '23

Hi, When I do "dnf module list --all" on CentOS Stream 8, I also see the stream versions installed by default, e.g. postgresql 10. But on CentOS Stream 9, I only see the newer stream version, like postgresql 15 and nodejs 18 (and not postgresql 13 and nodejs 16). Can anyone explain what's happening here? Thanks, -- -- Jos Vos <jos(a)xos.nl> -- X/OS Experts in Open Systems BV | Office: +31 20 6938364 -- Amsterdam, The Netherlands | Mobile: +31 6 26216181

4 6

failed: Could not start storage pool: cannot open directory: ... No such file or directory
by Kaushal Shriyan 14 Jan '23

14 Jan '23

Hi, # cat /etc/redhat-release CentOS Linux release 7.9.2009 (Core) #virt-install --version 1.5.0 # # ls -l /var/lib/libvirt/isos/ total 8302356 -rw-r--r--. 1 root root 4712300544 Aug 31 2021 CentOS-7-x86_64-DVD-2009.iso -rw-r--r--. 1 qemu qemu 990904320 Aug 11 2021 ubuntu-18.04.5-live-server-amd64.iso -rw-r--r--. 1 qemu qemu 1331691520 Feb 23 2022 ubuntu-20.04.4-live-server-amd64.iso -rw-r--r--. 1 qemu qemu 1466714112 Jun 28 2022 ubuntu-22.04-live-server-amd64.iso # virt-install --name demoreactui --ram 8096 --disk path=/linuxkvmguestosdisk/demoreactui.img,size=20 --vcpus 2 --os-variant ubuntu20.04 --network bridge=br0 --graphics none --console pty,target_type=serial --location /var/lib/libvirt/isos/ubuntu-20.04.4-live-server-amd64.iso,kernel=casper/vmlinuz,initrd=casper/initrd --extra-args 'console=ttyS0,115200n8 serial' ERROR Error validating install location: Validating install media '/var/lib/libvirt/isos/ubuntu-20.04.4-live-server-amd64.iso,kernel=casper/vmlinuz,initrd=casper/initrd' failed: Could not start storage pool: cannot open directory '/var/lib/libvirt/isos/ubuntu-20.04.4-live-server-amd64.iso,kernel=casper/vmlinuz,initrd=casper': No such file or directory Any clue and I look forward to hearing from you. Thanks in advance. Best Regards, Kaushal

4 6

Re: [CentOS] Looking for a RAID1 box
by Robert Moskowitz 12 Jan '23

12 Jan '23

I have found a: HPE 873830-S01 ProLiant MicroServer Gen10 for <$300 without drives. If I can believe the seller, it has a AMD Opteron X3216 Dual-core (2 Core) 1.6GHz and 8GB Installed. It has 4 3.5" bays. and 1? "Media" bay? https://www.servertechsupply.com/873830-s01/ this could well be acceptable. Got to find out power draw. Looks like ~40W. Any input on issues of OS install? Do I go with separate OS and data RAID1 sets? Also HPE is ClearOS. I ran ClearOS6 for years before going with QNAP turnkey. Perhaps current ClearOS is better, but it does not handle multi-domain email as I need. Or it did not. So I am going to install my own CentOS variant and iRedMail... thanks On 1/5/23 13:08, Jon LaBadie wrote: > On Thu, Jan 05, 2023 at 08:18:08AM -0500, Robert Moskowitz wrote: >> Proliant gen8 does NOT have UEFI. >> >> So I think this means I better move up to the gen10... >> > > I'm pleased with my Gen 10+ (Plus). Pricer than I thought > you want. > > I like the "no power supply", just an external brick. > Quiet. I put in a PCI card to use 2 NVMe sticks, one for > system and one for /home. You can also boot from an internal > usb port like a thumb drive permanently installed. > > Carriers for 2.5inch SSD drives work fine so with few fans, > no drive motors, could be quite low power. > > Mine acts as email server, local caching DNS server (dnsmasq) > and Amanda backup server. > > Jon >

6 12

Help with an HP Proliant gen10 plus?
by Robert Moskowitz 10 Jan '23

10 Jan '23

Just starting and trying to boot off the SPP firmware update ISO image on a USB stick. I made the stick with: # mkfs.vfat /dev/sdb # dd bs=4M if=P52581_001_gen10spp-2022.09.01.00-SPP2022090100.2022_0930.1.iso of=/dev/sdb status=progress The usb drive is 16GB and the iso is 9GB. seem to boot from it and go into auto install of firmware then died with starting initrd... warning!!! Unable to mount the file system [cdrom] warning!!! Unable to mount the file system Preboot maintence mode /bin/ash: can't access tty: job control turned off and at # prompt. There is no cdrom on the gen10 plus. Only in internal bootable usb port.

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2023