Discuss

discuss@lists.centos.org

1 participants
34732 discussions

CentOS 7 Installer Dual Stack via Kernel Params
by fetch＠posteo.nl 02 Aug '24

02 Aug '24

Hi all, I know I'm a bit late to ask this, but did the CentOS 7 installer kernel (here now https://vault.centos.org/7.9.2009/os/x86_64/images/pxeboot/) ever support setting an IPv4 AND an IPv6 address on the same interface? I've done some testing in a VM where setting EITHER IPv4 OR IPv6 works, but not both on the same interface, but is it possible to have dual stack settings applied to one interface via the kernel parameters? Assume that I have no ability to have a kickstart file locally, otherwise this could be worked around :/ Thanks

3 3

problems with 8 stream vault?
by Aleksandar Ivanisevic 30 Jul '24

30 Jul '24

Hi, currently im getting a 502 trying to get AppStream/repomd.xml, but some other files are fine, like repomd.asc, see below is this an outage or it is gone forever? ~$ curl 'https://vault.centos.org/centos/8-stream/AppStream/x86_64/os/repodata/repom…' <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>502 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> CloudFront wasn't able to connect to the origin. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: ZdkR1vn61GyMwUbRuoWv6MZULUJ2HyUNwwwsWi6xVY9v27hMZ8uZQA== </PRE> <ADDRESS> </ADDRESS> </B ~$ curl 'https://vault.centos.org/centos/8-stream/AppStream/x86_64/os/repodata/repom…' <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>502 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> CloudFront wasn't able to connect to the origin. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: ZdkR1vn61GyMwUbRuoWv6MZULUJ2HyUNwwwsWi6xVY9v27hMZ8uZQA== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>~$ ~$ curl 'https://vault.centos.org/centos/8-stream/AppStream/x86_64/os/repodata/repom…' -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABCAAGBQJmXXXxAAoJEAW1VbOEg8ZdCTQP/RpadNlDi2Vk+AnKBz6pATni YK6sCSxnSuWl/bIlMW6SnvKkrr98rMkHr6j6fH2YOGEenb8WPAUaa5+EPrqXAUBI Wr6pirbEjmwqLr2BUh59otjWiNIxK4D02cqKnuGMBUh0N4ZhF6/Qsr3twlJSmDCl WoRAB3ZTzavJmF3XGtUl8OuzyZDswZTUjP1ULGFMihBLWWPrLX2fSDvURle3Prcx z+XbES18OuI2uhyTPqb+q1iIL3m9/JZFQceUNHDXXEu0PlLp+ROq4NTrsFxmmn+Z +4y2ZJiRNIR3UlMDJhh6bRhSn7xOZr18yljwwkidtqrqxSJANLq0MGupiyT0gRAB cmfSAjHd5yXODyiiCUGFZA0A4bGXp6tFyE1nLk5P6rehL8AQuPVKb1GKA6yP9StS HTOeK/MSfyHrCvLXzCD7+9ryEdgpgQBCuJJGm46ppRPqkCvuTgmbQUd6zIK7PcaB JR7qqPpG77K0k7Sp7p2+e5I/vBn0o5v3+LshLZq3otF1ueQM5zhR54xgs4gwUARG gIE/cbO97yZzR97keGKGHMRCPNhMbwtTz0b+IeOsVEY5NEiwiFQCG/bvS6r6QnoA JVOH8AfpDay/fRY6fLfaPatn6zE9vV+Mqel/BLl9Hdky53cMw2PjE+MtJHIZLjmT 9JuOUkap7kzW8PXeeAa1 =6YJB -----END PGP SIGNATURE-----

2 2

Issue with yum - "Could not resolve host: mirrorlist.centos.org"
by NISHITH GEEDH 24 Jul '24

24 Jul '24

Dear CentOS Community, I am experiencing an issue when attempting to install packages using yum on CentOS 7. When I run the command yum install vim -y, I receive the following error message: Loaded plugins: fastestmirror Determining fastest mirrors Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error" One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Cannot find a valid baseurl for repo: base/7/x86_64 It seems there is an issue with the baseurl for the repository. I have already checked my network connection and it is working properly. I also tried updating the DNS configuration and clearing the yum cache, but the issue persists. Could someone please provide guidance on how to resolve this issue or point me to the correct repository configuration? Any help would be greatly appreciated. Thank you for your assistance. Best regards, Nishith

6 5

mariadb update... mysql-community ?
by ian.diddams＠celebrus.com 10 Jul '24

10 Jul '24

CentOS Linux release 7.9.2009 (Core) Just running a yum update on a server and this month we see this Dependencies Resolved ============================================================================================================================================================================================================================================= Package Arch Version Repository Size ============================================================================================================================================================================================================================================= Installing: MariaDB-client x86_64 10.4.34-1.el7.centos Default_Organization_mariadb_el7_repo_mariadb_el7_x86-64 12 M replacing mariadb.x86_64 1:5.5.68-1.el7 MariaDB-compat x86_64 10.4.34-1.el7.centos Default_Organization_mariadb_el7_repo_mariadb_el7_x86-64 2.2 M replacing mariadb-libs.x86_64 1:5.5.68-1.el7 mysql-community-client x86_64 5.7.44-1.el7 Default_Organization_mysql-5_7_x86-64_mysql-5_7_el7_x86-64 31 M replacing mariadb.x86_64 1:5.5.68-1.el7 mysql-community-libs x86_64 5.7.44-1.el7 Default_Organization_mysql-5_7_x86-64_mysql-5_7_el7_x86-64 3.0 M replacing mariadb-libs.x86_64 1:5.5.68-1.el7 mysql-community-libs-compat x86_64 5.7.44-1.el7 Default_Organization_mysql-5_7_x86-64_mysql-5_7_el7_x86-64 1.2 M replacing mariadb-libs.x86_64 1:5.5.68-1.el7 Soi why is mysql-community replacing mariadb ? And then we get Transaction check error: file /usr/share/mysql/charsets/Index.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/armscii8.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/ascii.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/cp1250.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/cp1251.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/cp1256.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/cp1257.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/cp850.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/cp852.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/cp866.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/dec8.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/geostd8.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/greek.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/hebrew.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/hp8.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/keybcs2.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/koi8r.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/koi8u.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/latin1.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/latin2.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/latin5.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/latin7.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/macce.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/macroman.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/share/mysql/charsets/swe7.xml conflicts between attempted installs of mysql-community-common-5.7.44-1.el7.x86_64 and MariaDB-common-10.4.34-1.el7.centos.x86_64 file /usr/bin/mysql conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 file /usr/bin/mysqladmin conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 file /usr/bin/mysqlbinlog conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 file /usr/bin/mysqlcheck conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 file /usr/bin/mysqldump conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 file /usr/bin/mysqlimport conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 file /usr/bin/mysqlshow conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 file /usr/bin/mysqlslap conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 file /usr/share/man/man1/mysql.1.gz conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 file /usr/share/man/man1/mysqladmin.1.gz conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 file /usr/share/man/man1/mysqlbinlog.1.gz conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 file /usr/share/man/man1/mysqlcheck.1.gz conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 file /usr/share/man/man1/mysqldump.1.gz conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 file /usr/share/man/man1/mysqlimport.1.gz conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 file /usr/share/man/man1/mysqlshow.1.gz conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 file /usr/share/man/man1/mysqlslap.1.gz conflicts between attempted installs of MariaDB-client-10.4.34-1.el7.centos.x86_64 and mysql-community-client-5.7.44-1.el7.x86_64 anyone any idea what on earth is going on? didds

1 0

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss