Discuss

discuss@lists.centos.org

34729 discussions

Finding kernel builds between releases
by nathan.keyes＠hitachivantara.com 30 Jun '24

30 Jun '24

Can someone point me to where I might be able to find or recreate kernel-4.18.0 builds for c8s between the 408 and 448 releases? Is there a way to find a list of patches that make up each intermediate build? I can see a list of individual commit messages for each build in the spec file changelog, but I have not found a place to see the associated changesets.

4 6

connecting centos7 from different network
by talhakaynak96＠hotmail.com 26 Jun '24

26 Jun '24

Hello, I have no previous experience with CentOS and network administration. Therefore, I would like to emphasize that my questions may be at a basic level. I am currently working on a project and my goal is to be able to access and transfer files between my CentOS 7 computer and a Windows computer over different networks. My CentOS 7 computer is connected to the internet via ethernet via a modem, which has a static IP address (which I can provide if needed). I have also assigned a static IP address to the CentOS 7 computer. My goal is to use my Windows computer to remotely connect to my CentOS computer over different networks and transfer files. Best regards

3 4

In place upgrade from CentOS 8 Stream to CentOS 9 Stream?
by Kay Schenk 17 Jun '24

17 Jun '24

Has anyone tried the procedure recommended in this article? https://www.veeble.org/kb/upgrade-centos-8-stream-to-centos-9-stream/ -- --- MzK

1 0

reminder : CentOS Linux 7 EOL / infra services disappearing in two weeks
by Fabian Arrotin 16 Jun '24

16 Jun '24

Hi, As discussed multiple times on various lists, CentOS Linux 7 will go EOL in two weeks (end of June) and so that means that various services running on CentOS 7 will disappear too . Apart from internal build infra for centos 7 itself (non public) that will be decommissioned, here are some services that will disappear: # mirrorlist.centos.org As the whole backend/frontend infra is running on centos 7 , and that everything Stream related (and now SIGs) was migrated to use mirrormanager (hosted by Fedora infra team), there was no reason to migrate/maintain it as all content will be EOL. # forums.centos.org Per discussion with the forums moderators, it will be powered off completely (not migrated) # torrent.centos.org In the past we used to provide .torrent for various centos linux releases, but it stopped with CentOS Stream. As the trackers (ipv4 and ipv6) are on centos 7, they'll disappear also end of this month -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

1 0

CentOS Stream 8 EOL
by Fabian Arrotin 06 Jun '24

06 Jun '24

As announced multiple times (see https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-an…) , CentOS Stream 8 reached now EOL (End Of Life) That means that all content was removed from http://mirror.centos.org/centos/8-stream/ (and so from downstream third-party mirrors) earlier today. The latest compose from today was archived to Vault (https://vault.centos.org/8-stream/) and will *never* receive any more update (security or else) SIGs content was also archived to same place, and koji/buildsystem tags "locked down". To reflect that "unmaintained state", mirrorlist.centos.org started also to answer "Invalid release/repo/arch combination" , like we always did for all the previous EOL'ed releases. -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

2 2

Phantom name server
by Dave Close 24 May '24

24 May '24

I have a CentOS stream 8 system (C8) which runs its own internal name server (BIND 9). In the past, it used an external name server on another machine but that server has been stopped. The resolv.conf file on C8 has been modified to remove the reference to the old server and NetworkManager has been restarted. However, CUPS and other programs on C8 continue to send queries to the old server, all of which eventually time out (of course). The bogus queries to the old server are answered with ICMP destination/port unreachable, confirming that the old name server is not running. But these bogus queries take time and the delays are very annoying. I've also restarted CUPS without effect. There are no references to the old server in /etc/named.conf, but there are references to the subnet it was on as there are other machines there that need to use the new name server. I haven't yet rebooted C8 but I'm prepared if necessary. Is there something else I should do before rebooting C8? Is that even likely to solve the problem? -- Dave Close, Compata, Irvine CA +1 714 434 7359 dave(a)compata.com dhclose(a)alumni.caltech.edu "Fairness is a concept that was invented so kids and idiots could participate in debates." --Dogbert

5 16

No suspend after update
by Michael B Allen 22 May '24

22 May '24

Just updated CentOS 9 Stream on a Lenovo T17 Gen 4 Intel and not it won't suspend with the following error: [ 52.604998] Restarting kernel threads ... done. [ 52.605111] OOM killer enabled. [ 52.605111] Restarting tasks ... done. [ 52.606604] random: crng reseeded on system resumption [ 52.616014] thermal thermal_zone9: failed to read out thermal zone (-61) [ 52.791625] PM: suspend exit [ 52.791733] PM: suspend entry (s2idle) [ 52.797260] Filesystems sync: 0.005 seconds [ 52.797579] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 52.799127] OOM killer disabled. [ 52.799128] Freezing remaining freezable tasks ... [ 72.805437] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0): [ 72.805450] task:NFSv4 callback state:I stack:0 pid:2191 ppid:2 flags:0x00004000 [ 72.805453] Call Trace: [ 72.805454] <TASK> [ 72.805456] __schedule+0x21b/0x550 [ 72.805463] schedule+0x2d/0x70 [ 72.805466] nfs41_callback_svc+0x186/0x190 [nfsv4] [ 72.805508] ? __pfx_autoremove_wake_function+0x10/0x10 [ 72.805512] ? __pfx_nfs41_callback_svc+0x10/0x10 [nfsv4] [ 72.805536] kthread+0xdd/0x100 [ 72.805538] ? __pfx_kthread+0x10/0x10 [ 72.805539] ret_from_fork+0x29/0x50 [ 72.805543] </TASK> Kernel: 5.14.0-404.el9.x86_64 How do I boot the previous kernel? Holding Shift down does nothing. Pressing escape brings up some kind of emergency screen that has no options other than to "Press any key to exit". Is CentOS 9 Stream considered stable enough to use as an everyday desktop? Mike

3 7

Problem 1: package resteasy-3.0.26-6.module_el8.4.0+595+e59c9af2.noarch from @System requires pki-servlet-4.0-api, but none of the providers can be installed
by Jelle de Jong 30 Apr '24

30 Apr '24

Dear CentOS members, Does someone know how to resolve this package conflict, it is creating security issues with freeipa dependencies. [root@freeipa01 ~]# yum update --refresh CentOS Stream 8 - AppStream 102 kB/s | 4.4 kB 00:00 CentOS Stream 8 - BaseOS 18 kB/s | 3.9 kB 00:00 CentOS Stream 8 - Extras 55 kB/s | 2.9 kB 00:00 CentOS Stream 8 - Extras common packages 15 kB/s | 3.0 kB 00:00 Extra Packages for Enterprise Linux 8 - x86_64 367 kB/s | 28 kB 00:00 Extra Packages for Enterprise Linux 8 - Next - x86_64 75 kB/s | 35 kB 00:00 Error: Problem 1: package resteasy-3.0.26-6.module_el8.4.0+595+e59c9af2.noarch from @System requires pki-servlet-4.0-api, but none of the providers can be installed - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from @System - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-1.module_el8.4.0+595+e59c9af2.noarch from appstream - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from appstream - cannot install the best update candidate for package resteasy-3.0.26-6.module_el8.4.0+595+e59c9af2.noarch - cannot install the best update candidate for package pki-servlet-4.0-api-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch Problem 2: cannot install the best update candidate for package pki-servlet-engine-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch - both package tomcat-el-3.0-api-1:9.0.62-30.el8.noarch from appstream and tomcat-lib-1:9.0.62-30.el8.noarch from appstream obsolete pki-servlet-engine <= 1:9.0.50 - package tomcat-1:9.0.62-30.el8.noarch from appstream requires tomcat-lib = 1:9.0.62-30.el8, but none of the providers can be installed - package tomcat-jsp-2.3-api-1:9.0.62-30.el8.noarch from appstream requires tomcat-servlet-4.0-api = 1:9.0.62-30.el8, but none of the providers can be installed - package tomcat-lib-1:9.0.62-30.el8.noarch from appstream requires tomcat-servlet-4.0-api = 1:9.0.62-30.el8, but none of the providers can be installed - package tomcatjss-7.7.1-1.module_el8.6.0+1038+e795ee4b.noarch from @System requires pki-servlet-engine >= 1:9.0.7, but none of the providers can be installed - package pki-servlet-engine-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from @System requires pki-servlet-4.0-api = 1:9.0.30-3.module_el8.5.0+854+e1c92b81, but none of the providers can be installed - package pki-servlet-engine-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from appstream requires pki-servlet-4.0-api = 1:9.0.30-3.module_el8.5.0+854+e1c92b81, but none of the providers can be installed - package pki-servlet-engine-1:9.0.30-1.module_el8.4.0+595+e59c9af2.noarch from appstream requires pki-servlet-4.0-api = 1:9.0.30-1.module_el8.4.0+595+e59c9af2, but none of the providers can be installed - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from @System - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-1.module_el8.4.0+595+e59c9af2.noarch from appstream - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from appstream - cannot install the best update candidate for package tomcatjss-7.7.1-1.module_el8.6.0+1038+e795ee4b.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

2 1

Fwd: [clamav-users] ClamAV 1.0.X for EPEL 7 & 8
by Kenneth Porter 27 Apr '24

27 Apr '24

------------------------------------------------------------------------ *From:* Orion Poplawski via clamav-users [mailto:clamav-users@lists.clamav.net] *Sent:* Friday, April 26, 2024 at 5:05 PM *To:* ClamAV users ML *Cc:* Orion Poplawski *Subject:* [clamav-users] ClamAV 1.0.X for EPEL 7 & 8 With the help of John Sullivan and Sérgio M. Basto we have gotten the Fedora ClamAV 1.0.X package in shape to be built for EPEL 7 and 8. We have a COPR available now with builds of 1.0.6 ready for testing here: https://copr.fedorainfracloud.org/coprs/g/clamav/clamav-1.0/ We will likely push this to EPEL proper just after RHEL 8.10 is released, presumably in May. But testing and feedback of the COPR builds before that would be welcome. Orion -- Orion Poplawski he/him/his - surely the least important thing about me IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Laneorion(a)nwra.com Boulder, CO 80301https://www.nwra.com/

1 0

RDO Caracal 2024.1 Released
by Amy Marrich 24 Apr '24

24 Apr '24

RDO Caracal 2024.1 Released The RDO community is pleased to announce the general availability of the RDO build for OpenStack 2024.1 Caracal for RPM-based distributions, CentOS Stream and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Caracal is the 29th release from the OpenStack project, which is the work of more than 1,000 contributors from around the world. The release is already available for CentOS Stream 9 on the CentOS mirror network in: http://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-caraca… The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Stream and is a member of the CentOS Cloud SIG. The Cloud SIG focuses on delivering a great user experience for CentOS users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. The highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/caracal/highlights.html but here are some highlights: - Drivers with inactive CI were marked unsupported including Windows iSCSI Driver, Windows SMB Driver, Dell SC Series Storage Driver (iSCSI, FC), Dell VNX Storage Driver (FC, iSCSI) and Dell XtremeIO Storage Driver (iSCSI, FC). - New driver features were added, notably, Fujitsu ETERNUS DX extend volume on RAID group, Pure Storage synchronous replication, NetApp iSCSI LUN space allocation, Dell PowerFlex Active-Active support, Dell PowerMax configurable SRDF snapshots. - Designate now supports Catalog Zones (RFC 9432). This can improve the scalability of Designate pools managing a large number of zones and significantly reduce the provisioning time when adding additional DNS servers to a Designate pool. - Horizon now uses Django 4.2 as default and dropped Django 3.2 support. - Ironic has enabled RBAC support by default by changing the default values of [oslo_policy]enforce_scope and [oslo_policy]enforce_new_defaults to True. Additionally, we added [DEFAULT]rbac_service_project_name to define a project where users in that project are treated as having a service role. Please see Ironic release notes for full details. - Ironic has added the ability to drain active tasks from a conductor before shutdown. Sending a SIGUSR2 signal to an ironic-conductor will now attempt to complete running tasks with a timeout of [DEFAULT]drain_shutdown_timeout. No new tasks will be started on the conductor while it’s draining. - Support was added for the external-gateway-multihoming API extension. The L3 service plugins supporting it can now create multiple gateway ports per router. It is currently limited to the L3 OVN plugin. OpenStack Caracal is marked as Skip Level Upgrade Release Process or SLURP. According to this model ( https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad…) this means that upgrades will only be supported from the Antelope 2023.1 release. RDO Caracal 2024.1 has been built and tested with the recently released Ceph 18.2.0 Reef version (https://docs.ceph.com/en/latest/releases/reef/) which has been published by the CentOS Storage SIG in the official CentOS repositories. *Note:* Follow the instructions in [RDO documentation]( https://www.rdoproject.org/install/install-with-ceph/) to install OpenStack and Ceph services in the same host. During Caracal cycle, some projects have been retired or declared inactive upstream. As such, the following packages for some projects are not present in the RDO Caracal 2024.1 release: - cinderlib - dib-utils - ec2api-tempest-plugin - ec2api - murano - murano-agent - muranoclient - murano-dashboard - murano-tempest-plugin - sahara - sahara-dashboard - sahara-image-elements - sahara-plugin-ambari - sahara-plugin-cdh - sahara-plugin-mapr - sahara-plugin-spark - sahara-plugin-storm - sahara-plugin-vanilla - sahara-tests - senlin - senlinclient - puppet-ec2api - puppet-etcd - puppet-haproxy - puppet-module-data - puppet-murano - puppet-qdr - puppet-rsyslog - puppet-sahara During the next release we will continue working on retiring inactive packages in order to ensure RDO content quality and security. Contributors: - During the Caracal cycle, we saw the following new RDO contributors: - Marihan Girgis - Balazs Gibizer - Fiorella Yanac Welcome to all of you and Thank You So Much for participating! But we wouldn’t want to overlook anyone. A super massive Thank You to all 47 contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and rdo-website repositories: - Ade Lee - Alfredo Moralejo Alonso - Amy Marrich (spotz) - Arx Cruz - Balazs Gibizer - Bernard Cafarelli - Bohdan Dobrelia - Chandan Kumar - Cyril Roelandt - Daniel Pawlik - Douglas Viroel - Emma Foley - Fabricio Aguiar - Fiorella Yanac - Gregory Thiemonge - Grzegorz Grasza - Harald Jensås - Jiří Podivín - Joan Francesc Gilabert - Joel Capitao - Karolina Kula - Lewis Denny - Lon Hohberger - Luigi Toscano - Luis Tomas Bolivar - Lukáš Piwowarski - Maor Blaustein - Marihan Girgis - Marios Andreou - Martin Kopec - Martin Magr - Mathieu Bultel - Michael Johnson - Nate Johnston - Pablo Rodríguez Nava - Priscila Gutierres - Rabi Mishra - Roberto Alfieri - Ronelle Landy - Shreshtha Joshi - Soniya Vyas - Szymon Datko - Takashi Kajinami - Tobias Urdin - Tristan De Cacqueray - Yatin Karel - Zane Bitter The Next Release Cycle At the end of one release, focus shifts immediately to the next release i.e Dalmatian. Get Started To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation. You can run RDO on a single node to get a feel for how it works. For those that do not have any hardware or physical resources, there is the OpenStack Global Passport Program. This is a collaborative effort between OpenStack public cloud providers to let you experience the freedom, performance and interoperability of open source infrastructure. You can quickly and easily gain access to OpenStack infrastructure via trial programs from participating OpenStack public cloud providers around the world. Get Help The RDO Project has our users(a)lists.rdoproject.org for RDO-specific users and operators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org. You can also find extensive documentation on RDOproject.org. The #rdo channel on OFTC IRC is also an excellent place to find and give help. We also welcome comments and requests on the CentOS devel mailing list and the CentOS IRC channels (#centos, #centos-cloud, #centos-devel in Libera.Chat network), however we have a more focused audience within the RDO venues. Get Involved To get involved in the OpenStack RPM packaging effort, check out the RDO contribute pages, peruse the CentOS Cloud SIG page, and inhale the RDO packaging documentation. Join us in #rdo and on the OFTC IRC network and follow us on Twitter @RDOCommunity. You can also find us on Facebook and YouTube. *Amy Marrich* She/Her/Hers Principal Technical Marketing Manager - Cloud Platforms Red Hat, Inc <https://www.redhat.com/> amy(a)redhat.com Mobile: 954-818-0514 Slack: amarrich IRC: spotz

1 0

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