Discuss November 2023

discuss@lists.centos.org

7 participants
7 discussions

Puppet from EPEL ?
by lejeczek 30 Nov '23

30 Nov '23

Hi guys. It's a bit confusing - I'm only about to start a foray into it - whether _puppet_ from EPEL is the whole-lot-server? From the look of included _puppet.service_ - this package is only agent and if not why no server bits? Looking at what comes with Puppet's own repo - those appear quite different, packages. do. How do you install/get your _puppets_? thanks, L.

2 1

possible LVM corruption?
by Gordon Messmer 28 Nov '23

28 Nov '23

While updating a hypervisor, I'm getting the following errors printed to the terminal during rpm upgrade scripts. The first line is printed 15 times, and GRUB prints a similar error at boot. "vgck" doesn't seem to find any problems. Does anyone have suggestions for diagnosing the issue? error: ../grub-core/disk/diskfilter.c:524:unknown node 'vm_ipa-data_rimage_0'. grub2-probe: error: ../grub-core/kern/disk.c:236:disk `lvmid/uhx5FA-RmdV-cPYP-ELEA-pUrn-FfHl-M2RBEV/JQKCwn-RhKX-ek4u-VJxX-ja9j-rtAD-fVUBGc' not found. "vgdisplay --verbose" output includes: --- Volume group --- VG Name VolGroup System ID Format lvm2 Metadata Areas 2 Metadata Sequence No 2053 VG Access read/write VG Status resizable MAX LV 0 Cur LV 82 Open LV 18 Max PV 0 Cur PV 2 Act PV 2 VG Size <7.28 TiB PE Size 32.00 MiB Total PE 238392 Alloc PE / Size 163262 / 4.98 TiB Free PE / Size 75130 / 2.29 TiB VG UUID uhx5FA-RmdV-cPYP-ELEA-pUrn-FfHl-M2RBEV --- Logical volume --- LV Path /dev/VolGroup/vm_ipa-data LV Name vm_ipa-data VG Name VolGroup LV UUID YSw2fz-e4cA-7i86-4ssj-5b49-7572-uNWm2p LV Write Access read/write LV Creation host, time ascension, 2023-10-26 21:31:26 -0700 LV Status available # open 1 LV Size 5.00 GiB Current LE 160 Mirrored volumes 2 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:197 # lvs -a | grep vm.ipa.data vm_ipa-data VolGroup rwi-aor--- 5.00g 100.00 [vm_ipa-data_rimage_0] VolGroup gwi-aor--- 5.00g [vm_ipa-data_rimage_0_iorig] 100.00 [vm_ipa-data_rimage_0_imeta] VolGroup ewi-ao---- 96.00m [vm_ipa-data_rimage_0_iorig] VolGroup -wi-ao---- 5.00g [vm_ipa-data_rimage_1] VolGroup gwi-aor--- 5.00g [vm_ipa-data_rimage_1_iorig] 100.00 [vm_ipa-data_rimage_1_imeta] VolGroup ewi-ao---- 96.00m [vm_ipa-data_rimage_1_iorig] VolGroup -wi-ao---- 5.00g [vm_ipa-data_rmeta_0] VolGroup ewi-aor--- 32.00m [vm_ipa-data_rmeta_1] VolGroup ewi-aor--- 32.00m

1 0

Apps moving to laptop display when switching KVM
by Michael B Allen 27 Nov '23

27 Nov '23

So I installed CentOS Stream 9 on a new Lenovo T14 Gen 4 Intel. I have a 4x1 HDMI KVM with external monitor. When switching the KVM, apps move between displays / workspaces in erratic ways. More specifically, when switching out, apps on the external display usually move to the laptop display. This sorta makes sense for a laptop with an external display. When the external display is disconnected, you want to have access to the apps. But for a KVM, the desired behavior is that the apps do NOT move. When switching back, I want all apps (terminals) to be where they were when I switched out. After much searching, I have found NO discussion of this issue. Is this a scenario that is even supposed to work? The KVM worked perfectly with the Windows 11 install that come with the machine (apps on the external display did not move when switching the KVM). Questions: Is there a GNOME window manager configuration that does not move apps when it senses the HDMI connection has changed? I actually had this mostly working with a Dell laptop running a RHEL 9 clone and selecting Xorg on the GDM screen. Apps were not moved when switching out (although depending on particular circumstances they could when switching back). Where should I be asking about this? A freedesktop.org list? Where is the code that moves windows in reaction to a change in displays? Currently the only way to reliably switch the KVM without all of the apps loosing their positions is to just suspend the machine before and resume after.

1 1

CentOS box images at Vagrant Cloud give 404
by Kees Bakker 22 Nov '23

22 Nov '23

Hi, At Vagrant Cloud there are "box" images for stream8 and stream9 [1]. At least they are supposed to be there. The download links on the detail pages, for example for stream9 20230727.1 [2] are redirected to cloud.centos.org, however they give an 404 error. Possibly the centos Vagrant Cloud page is not kept up to date with the actual box images that are now present on cloud.centos.org. Do we know who is maintaining this centos account at Vagrant Cloud? Can someone update the centos entries overthere? [1] https://app.vagrantup.com/centos/ [2] https://app.vagrantup.com/centos/boxes/stream9/versions/20230727.1 -- Kees Bakker

1 0

emulate ARM ?
by lejeczek 16 Nov '23

16 Nov '23

Hi guys. How do you emulate AMR arch - I mean, with what's in distro &| SIGs repos as oppose to do-it-yourself? many thanks, L.

2 3

can I convert a linear thin pool to raid1?
by Gordon Messmer 09 Nov '23

09 Nov '23

In the past, I've used LVM on MD RAID, and I'd like to try using LVM RAID in order to also add dm-integrity data to some LVs. I've added new PVs to my VG, and I've converted some of my LVs to raid1 types, but I also have one thin pool that I use for VMs with multiple layers of snapshots. That pool can't be converted, directly: # lvconvert --type raid1 -m 1 VolGroup/vm_pool --yes Operation not permitted on LV VolGroup/vm_pool type thinpool. Is it sufficient to simply convert the tdata and tmeta LVs to raid1 type? Should I also convert lvol0_pmspare? Is there anything else I should consider? # lvs VolGroup/vm_pool VolGroup/vm_pool_tmeta VolGroup/vm_pool_tdata VolGroup/lvol0_pmspare LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert [lvol0_pmspare] VolGroup ewi-a----- 128.00m vm_pool VolGroup twi-aotz-- 200.00g 12.83 15.93 [vm_pool_tdata] VolGroup Twi-ao---- 200.00g [vm_pool_tmeta] VolGroup ewi-ao---- 128.00m

1 0

selinux blocks rsync client in systemd service
by Kenneth Porter 03 Nov '23

03 Nov '23

I'm trying to slurp a CentOS 7's filesystem to another CentOS 7 system using rsyncd on the supplying side and rsync running as a client in a timer unit on the client side. My backup script on the backup system runs fine from the command line. When run from a systemd timer unit, rsync sends nothing to the systemd log and I see a denial in the audit log for a Unix domain socket in init_t context. I'm guessing it's trying to write to stdout which is getting redirected to systemd's log. The service unit file has StandardOutput=syslog in order to capture the list of files backed up. The following selinux rule seems to fix this: allow rsync_t init_t:unix_stream_socket { getattr read write }; I also found it necessary to add --no-devices and --no-specials to my backup script, but I can live with that. A few devices show up in chroots and postfix has some sockets in its package. Those are easily recreated if I need to do a restore. So is this selinux rule an oversight? Should there be an rsync bool for it? Or was this fixed in a more recent version of systemd?

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss November 2023