Discuss

discuss@lists.centos.org

34729 discussions

Problem 2: Can't uninstall tigervnc-server-minimal.x86_64 without forcing removal of anaconda!
by Kay Schenk 23 Apr '24

23 Apr '24

Dear all --- I DO NOT want tigervnc on my system! I've done what I can changing dnf parameters on uninstall. If I try to deinstall it, it absolutely, positively wants to UNINSTALL anaconda no matter what options I provide. Running CentOS 8, one of the 4.18 xxxxx Any solutions? -- --- Kay Schenk

2 1

Figure out why kdump is not producing dmesg in CentOS stream 8
by public1020 13 Apr '24

13 Apr '24

I created a CentOS 8 stream machine on aws, and configured crashkernel in grub ``` $ cat /proc/cmdline BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-4.18.0-552.el8.x86_64 root=UUID=e52ef623-609b-4202-9b2c-ac7aba5c3bee ro console=ttyS0,115200n8 no_timer_check net.ifnames=0 nvme_core.io_timeout=4294967295 nvme_core.max_retries=10 crashkernel=128M ``` Then I installed and verified kdump is functioning ``` # systemctl status kdump ● kdump.service - Crash recovery kernel arming Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: enabled) Active: active (exited) since Sat 2024-04-13 08:42:55 UTC; 40s ago Process: 808 ExecStart=/usr/bin/kdumpctl start (code=exited, status=0/SUCCESS) Main PID: 808 (code=exited, status=0/SUCCESS) Apr 13 08:42:43 ip-172-31-2-139.ap-east-1.compute.internal dracut[1101]: *** Install squash loader *** Apr 13 08:42:43 ip-172-31-2-139.ap-east-1.compute.internal dracut[1101]: *** Stripping files *** Apr 13 08:42:44 ip-172-31-2-139.ap-east-1.compute.internal dracut[1101]: *** Stripping files done *** Apr 13 08:42:44 ip-172-31-2-139.ap-east-1.compute.internal dracut[1101]: *** Squashing the files inside the initramfs *** Apr 13 08:42:54 ip-172-31-2-139.ap-east-1.compute.internal dracut[1101]: *** Squashing the files inside the initramfs done *** Apr 13 08:42:54 ip-172-31-2-139.ap-east-1.compute.internal dracut[1101]: *** Creating image file '/boot/initramfs-4.18.0-552.el8.x86_64kdump.img' *** Apr 13 08:42:55 ip-172-31-2-139.ap-east-1.compute.internal dracut[1101]: *** Creating initramfs image file '/boot/initramfs-4.18.0-552.el8.x86_64kdump.img' done *** Apr 13 08:42:55 ip-172-31-2-139.ap-east-1.compute.internal kdumpctl[814]: kdump: kexec: loaded kdump kernel Apr 13 08:42:55 ip-172-31-2-139.ap-east-1.compute.internal kdumpctl[814]: kdump: Starting kdump: [OK] Apr 13 08:42:55 ip-172-31-2-139.ap-east-1.compute.internal systemd[1]: Started Crash recovery kernel arming. ``` Now I need to mimic kernel crash, so I used sysrq to do that ``` echo c > /proc/sysrq-trigger ``` However, after reboot, I didn't see a dmesg file in /var/crash as in CentOS 7.X ``` # ls /var/crash - nothing, empty folder - ``` The only thing I can see is /var/log/kdump.log ``` + 2024-04-13 08:35:56 /usr/bin/kdumpctl@679: ret=0 + 2024-04-13 08:35:56 /usr/bin/kdumpctl@680: set +x + 2024-04-13 08:42:55 /usr/bin/kdumpctl@675: /sbin/kexec -s -d -p '--command-line=BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-4.18.0-552.el8.x86_64 ro console=ttyS0,115200n8 no_timer_check net.ifnames=0 nvme_core.io_timeout=4294967295 nvme_core.max_retries=10 irqpoll nr_cpus=1 reset_devices cgroup_disable=memory mce=off numa=off udev.children-max=2 panic=10 rootflags=nofail acpi_no_memhotplug transparent_hugepage=never nokaslr novmcoredd hest_disable disable_cpu_apicid=0' --initrd=/boot/initramfs-4.18.0-552.el8.x86_64kdump.img /boot/vmlinuz-4.18.0-552.el8.x86_64 Try gzip decompression. Try LZMA decompression. + 2024-04-13 08:42:55 /usr/bin/kdumpctl@679: ret=0 + 2024-04-13 08:42:55 /usr/bin/kdumpctl@680: set +x + 2024-04-13 08:44:31 /usr/bin/kdumpctl@675: /sbin/kexec -s -d -p '--command-line=BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-4.18.0-552.el8.x86_64 ro console=ttyS0,115200n8 no_timer_check net.ifnames=0 nvme_core.io_timeout=4294967295 nvme_core.max_retries=10 irqpoll nr_cpus=1 reset_devices cgroup_disable=memory mce=off numa=off udev.children-max=2 panic=10 rootflags=nofail acpi_no_memhotplug transparent_hugepage=never nokaslr novmcoredd hest_disable disable_cpu_apicid=0' --initrd=/boot/initramfs-4.18.0-552.el8.x86_64kdump.img /boot/vmlinuz-4.18.0-552.el8.x86_64 Try gzip decompression. Try LZMA decompression. + 2024-04-13 08:44:31 /usr/bin/kdumpctl@679: ret=0 + 2024-04-13 08:44:31 /usr/bin/kdumpctl@680: set +x ``` I need the dmesg to understand what's causing the crash. How can I do that? P.S I have a kernel module that triggers a crash but I don't know why, and to demonstrated the problem with kdump, I use sysrq so anyone want to help can easily reproduce it.

2 4

Out-Of-Office
by Sivaramakrishna Polepalli 13 Apr '24

13 Apr '24

Hello, I will be OOO traveling from 03/28 to 05/06 returning back on 05/07. Please expect delays in my email responses. Please contact Aurus support prodsupport(a)aurusinc.com / Yogesh Baviskar ybaviskar(a)aurusinc.com for any support needs. Thanks Siva Polepalli +1 575-404-3272

1 0

None
by None 05 Apr '24

05 Apr '24

blank" do you not understand? ;) If you do not believe there is any problem, consider the complexity of Johnny Hughes's solution! If Johnny Hughes's solution works for him and he is happy with it, that is great -- more power to him. (The FAQ includes a write up of Johnny's solution.) I have two replies. 1) Back a couple of months ago, as a test, I tried his solution, and the screen on my Mag DX1495 still went blank with the two nVIDIA cards that I tested. 2) I would rather just plug in a card which works right out of the box on a standard, SUPPORTED kernel, than to go through all the complicated steps in Johnny's solution. But this is just my personal preference. I can use the nVIDIA cards in Linux with compatible monitors or in Windows with any monitor (as far as I know). BTW, the computer on which I am writing this email runs CentOS, and with this Acer 77c monitor, I am using an nVIDIA GeForce display card -- it works fine with THIS hardware. Rick Message: 7 Date: Tue, 21 Sep 2004 23:17:26 -0400 From: Christopher Blume <godsmoke(a)godsmoke.com> To: centos(a)caosity.org Subject: Re: [Centos] nVIDIA on CentOS 3.3 Hello Rick, I have to say, I found your notice of nVidia cards "not working" as a little odd. To begin with -- drivers *generally* do not vary between distributions of linux. So, the fact that your card "doesn't work" with CentOS means that something else went wrong -- not that the drivers don't exist, or don't function properly. First of all, I'd be interested to see where your conclusion that your monitor doesn't work with an nVidia card in linux came from -- what exactly did you experience/test to come to this statement? I don't know anything about Kudzu, but, let me tell you, the nVidia Riva TNT 2 is ABSOLUTELY supported by the linux kernel -- and XFree86 ABSOLUTELY runs on it. If it's not working on your system, instead of making conclusions about Linux as a whole, understand that there are probably issues with the configuration files you either manually wrote, or the programs CentOS/RHEL bundles with the distro did. nVidia cards have the absolute best support under linux of any video card -- and I highly doubt what you experienced was a driver issue -- if it was, it was because of some mangled patch that RedHat applied, because the driver for nVidia TNTs is used by tens of thousands of Linux users. Thank You, Christopher Blume

1 0

Out-Of-Office
by Sivaramakrishna Polepalli 04 Apr '24

04 Apr '24

Hello, I will be OOO traveling from 03/28 to 05/06 returning back on 06/07. Please expect delays in my email responses. Please contact Aurus support prodsupport(a)aurusinc.com / Yogesh Baviskar ybaviskar(a)aurusinc.com for any support needs. Thanks Siva Polepalli +1 575-404-3272

2 1

CentOS-announce Digest, Vol 219, Issue 2
by centos-announce-request＠centos.org 04 Apr '24

04 Apr '24

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2024:1486 Critical CentOS 7 firefox Security Update (Johnny Hughes) 2. CESA-2024:1498 Moderate CentOS 7 thunderbird Security Update (Johnny Hughes) 3. CEBA-2024:1540 CentOS 7 redhat-support-lib-python BugFix Update (Johnny Hughes) 4. CEBA-2024:1540 CentOS 7 redhat-support-tool BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 3 Apr 2024 14:00:43 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2024:1486 Critical CentOS 7 firefox Security Update Message-ID: <20240403140043.GA18050(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2024:1486 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2024:1486 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 33dd225ef7b01c077e7d0977782fa69f3d8fd4cea6363f4cde213cc37694b3a2 firefox-115.9.1-1.el7.centos.i686.rpm 2f160bf3a57455fd82821ea858e6ab2789596f1ae502a2b3968383670f17296f firefox-115.9.1-1.el7.centos.x86_64.rpm Source: 3267298df86f1f220840ce663243282de3bd1cdbe0eabd1485f3f01ad1ae07ec firefox-115.9.1-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 3 Apr 2024 14:01:39 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2024:1498 Moderate CentOS 7 thunderbird Security Update Message-ID: <20240403140139.GA18446(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2024:1498 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2024:1498 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: de56cf10dbbabd9a55f388bacf02eb1f5bb04b430bbad9a217d6dc57141aaeb5 thunderbird-115.9.0-1.el7.centos.x86_64.rpm Source: 2a36182ee2aeb5bbdb7c973d6d48bc6a4a929f8d3a3b0c8ffd8e35debc2ce22f thunderbird-115.9.0-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 3 Apr 2024 14:07:07 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2024:1540 CentOS 7 redhat-support-lib-python BugFix Update Message-ID: <20240403140707.GA19944(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2024:1540 Upstream details at : https://access.redhat.com/errata/RHBA-2024:1540 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 623f1a82453fc1bd44617826a88974cd43fbbb30a2d72e47bd706b0deb895254 redhat-support-lib-python-0.14.0-1.el7_9.noarch.rpm Source: 4492c7df1e69f89395e1347815fd9bafe952d299b2b29541c850ad72a553939e redhat-support-lib-python-0.14.0-1.el7_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Wed, 3 Apr 2024 14:07:51 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2024:1540 CentOS 7 redhat-support-tool BugFix Update Message-ID: <20240403140751.GA20389(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2024:1540 Upstream details at : https://access.redhat.com/errata/RHBA-2024:1540 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 096e36a0f28a54f5ad7c593b2efd58ee933bf7f9c314927179a6d0244e0a596a redhat-support-tool-0.14.0-1.el7_9.noarch.rpm Source: a470b95be4f9036778b3805dd90ad0bc8b196f7a847826345e04fb9da5e963dd redhat-support-tool-0.14.0-1.el7_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 219, Issue 2 ***********************************************

1 0

None
by None 03 Apr '24

03 Apr '24

1 0

[Infra] - Planned outage : lists.centos.org (migration to mailman3) : please read
by Fabian Arrotin 02 Apr '24

02 Apr '24

Due to a needed upgrade , we'll have to move the existing CentOS mailman instance (aka https://lists.centos.org) to a new server/host. Migration is scheduled for """"Tuesday April 8th, 7:00 am UTC time"""". You can convert to local time with $(date -d '2024-04-08 07:00 UTC') The expected "downtime" is estimated to ~60 minutes , time needed to : - take last mailman2 backup - reimport / convert mailman2 archives to mailman3 DB - DNS propagation for A/AAAA/MX records Here are also some important information about the mailman2 => mailman3 migration : # Renamed lists Worth knowing that, based on open discussion on the centos-devel list (see whole thread at https://lists.centos.org/pipermail/centos-devel/2024-March/165576.html), existing lists will be *renamed* , so while we'll put aliases for incoming mails, each list member will start receiving list mails from new list name. So start updating your filters if you filter on email address instead of "subject:" Here is the overview of the new lists names : arm-dev at centos.org => arm-dev at lists.centos.org centos at centos.org => discuss at lists.centos.org centos-devel at centos.org => devel at lists.centos.org centos-announce at centos.org => announce at lists.centos.org centos-automotive-sig at centos.org => automotive-sig at lists.centos.org centos-{cz,de,es,fr,nl,pt-br,zh}(a)centos.org => discuss-{cz,de,es,fr,nl,pt-br,zh}(a)lists.centos.org ci-users at centos.org => ci-users at lists.centos.org centos-gsoc: => gsoc at lists.centos.org centos-mirror at centos.org => mirror at lists.centos.org centos-mirror-announce at centos.org => mirror-announce at lists.centos.org centos-newsletter at centos.org => newsletter at lists.centos.org centos-promo at centos.org => promo at lists.centos.org centos-virt at centos.org => virt at lists.centos.org # Authentication Mailman2 had no real concept of authentication so you could just subscribe to one or more lists, and have a password associated with your email address for that/these subscription(s). Mailman3 itself is split into "core" and "webui" components, so when we'll import mailman2 lists/config into mailman3, your existing subscriptions will continue to work *but* not your password. Mailman3 will be configured to support SSO, and so if you already have a FAS/ACO account (https://accounts.centos.org) you'll be able to login directly into new webui and manage your settings/subscriptions *if* your ACO email address of course matches the one you initially subscribed with for lists.centos.org. If that's not the case, either create an ACO/FAS account that will match and you'll be then able to "link" your mailman3 account with FAS and so manage your settings/subscriptions. If you don't want to, there is always the documented process : https://docs.mailman3.org/en/latest/userguide.html#making-a-mailman-account Thanks for your understanding and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

2 1

Out-Of-Office
by Sivaramakrishna Polepalli 02 Apr '24

02 Apr '24

1 0

CentOS 7/8s EOL : infrastructure impacts (please read)
by Fabian Arrotin 02 Apr '24

02 Apr '24

Hi all, As you're all aware (we sent multiple mails in the last year about this), CentOS 7 and Stream 8 will go EOL soon : https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-an… Let's lists some things that will happen on the CentOS Infrastructure as we'll be approching (or passed) these dates : # CentOS 7/8s content itself Usual process : content will be archived to https://vault.centos.org and removed from mirror.centos.org completely, with just a simple readme file dropped here (for example http://mirror.centos.org/centos/8/readme for already EOL'ed version). Worth knowing that some SIGs are still building for RHEL8, still supported for SIGs through https://cbs.centos.org so such kind of content will continue to be available there as long as SIGs can build against/for it # CBS/koji (https://cbs.centos.org) No impact on CBS env itself ( not running centos 7 nor 8s for a long time now) but the various build tag reflecting centos 7 and 8s will be locked so that nobody would be able to build content anymore : that would even be impossible as content itself will have been removed from mirror.centos.org (internally used for cbs build tags) # CentOS Forums (https://forums.centos.org) : still running on centos 7 and even if that's easy to migrate to newer/supported EL version, it was decided to just shutdown the service (based on discussion with the actual moderation team). An option (to be announced on forums.centos.org ?) is to eventually start moving thread/discussions on Fedora discourse (There is already a CentOS category there : https://discussion.fedoraproject.org/c/neighbors/centos/71) So the plan is just to shutdown forums.centos.org and remove A/AAAA records from DNS # mirrorlist.centos.org service : Starting from Stream 9 (and above), deployed CentOS instance ares using Fedora infra mirrormanager instance for metalink= instead of mirrorlist= in .repo files. We'll just decommission our mirror crawler (also running with a mix of perl/python2 code), so not validating any mirror for legacy/EOL releases. mirrorlist.centos.org A/AAAA records will be removed in the following weeks after c7 will be EOL'ed. That means that people still running CentOS 7 or 8-stream will not have functional yum/dnf stack, except if they point to either vault or have internal mirror but at least people would be aware that distro itself is EOL and that they shouldn't expect to receive any update anymore # CentOS mailing-lists Currently running on mailman2 stack, on top of CentOS 7 linux : there is WIP to port everything to up2date mailman3 stack, actually packaged for EPEL9. We have successfully imported archives into mailman3 and same for lists config but let's start a different/separate thread to discuss changes (like renaming lists, see next coming thread) Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

2 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss