Re: [CentOS] CentOS Stream 8 sssd.service failing part of sssd-common-2.8.1-1.el8.x86_64 baseos package
> > > On 1/9/23 17:45, Simon Matter wrote: >>> On 1/3/23 13:41, Simon Matter wrote: > On 1/3/23 05:17, Orion Poplawski wrote: >> On 12/30/22 04:06, Jelle de Jong wrote: >>> On 12/27/22 22:55, Gordon Messmer wrote: On 2022-12-25 07:44, Jelle de Jong wrote: > 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. ... > [sssd] [confdb_expand_app_domains] (0x0010): No domains > configured, > fatal error! Were you previously using sssd? Or is the problem merely that it is now reporting an error starting a service that you don't use? Are there any files in /etc/sssd/conf.d, or does /etc/sssd/sssd.conf exist? If so, what are the contents of those files? What are the contents of /usr/lib/systemd/system/sssd.service? If you run "journalctl -u sssd.service", are there any log entries older than the package update? >>> >>> I got a monitoring system for failing services and I sudenly >>> started >>> getting dozens of notifications for all my CentOS systems that sssd >>> was failing. This is after the sssd package updates, causing this >>> regression. SSSD services where not really in use but some of the >>> common libraries are used. >>> >>> # 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 Sat 2022-12-24 >>> 06:14:10 >>> UTC; 6 days ago >>> Condition: start condition failed at Fri 2022-12-30 11:02:01 UTC; >>> 4s >>> ago >>> ├─ ConditionPathExists=|/etc/sssd/sssd.conf was not >>> met >>> └─ ConditionDirectoryNotEmpty=|/etc/sssd/conf.d was >>> not >>> met >>> Main PID: 3953157 (code=exited, status=4) >>> >>> Warning: Journal has been rotated since unit was started. Log >>> output >>> is incomplete or unavailable. >> >> >>> # ls -halZ /etc/sssd/sssd.conf >>> ls: cannot access '/etc/sssd/sssd.conf': No such file or directory >> >> Looks like you need to figure out what happened to your >> /etc/sssd/sssd.conf file. FWIW - I've updated my one CS8 machine to >> 2.8.1-1 and it seems to be fine. > > I did not do anything specific to the configuration file. I tried to > reinstall the new sssd-common pacakge, but it will not install the > /etc/sssd/sssd.conf file. I can not remove the package because it > will > remove a lot of packages that I do need. I still think something is > wrong with the new sssd packages.. > > [root@nginx01 ~]# rpm -qplc sssd-common-2.8.1-1.el8.x86_64.rpm > /etc/logrotate.d/sssd > /etc/pam.d/sssd-shadowutils > /etc/rwtab.d/sssd > /etc/sssd/sssd.conf Most likely the file /etc/sssd/sssd.conf is a ghost file and therefore it's not installed but only recognized as being part of the package. Simon >>> >>> I do not get this. There has nog been an /etc/sssd/sssd.conf on my >>> system before as it only installed sssd-common due to dependencies for >>> other libaries. I do not use the sssd service. The package gets an >>> update and now my systemd status is failing on a lot of systems and I >>> am >>> being tolled I should get /etc/sssd/sssd.conf sorted? >>> >>> Can you fix the sssd package by either not enabling the sssd systemd >>> service or some other solution that does not make systemd status fail? >>> >>> This is a regression and it is going to cause me a lot of time now to >>> write ansible code for the disabling of the sssd service on all systems >>> that have it installed due to dependencies but do not use it. >>> >>> sssd.services failing regressions and dfn-automatic.serivces failing >>> regressions due to freeipa/sssd/samba conflicts for months now. >> >> Do you have a file /etc/sssd/sssd.conf? IIRC you said you don't have >> such >> a file, which is fine. > > no file is there. > >> Do you have any file in /etc/sssd/conf.d/? This directory should be >> empty >> but it's possible that another package puts something there. > > no files are there. Maybe you can check for a difference in sssd.service from the older package and the current one. It seems that there was a change which results in the behavior you see. Regards, Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Help with an HP Proliant gen10 plus?
On Mon, 9 Jan 2023, Robert Moskowitz wrote: Yeah. Going to work on it some more today. Plus got a finish a paper for a symposium. I give up on learning tex; I found a word template that can create the right pdf, so pull out all my writing in tex and start over. And I DO use the IETF's xml format for creating Internet Drafts, so I am teachable on this stuff despite my age... Are you trying to use tex directly? Latex is written on top of tex and might be easier. -- Michael henne...@mail.cs.ndsu.nodak.edu "Occasionally irrational explanations are required" -- Luke Roman ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] centos 8-Streams kernel?
On Mon, Jan 9, 2023 at 7:34 AM Johnny Hughes wrote: > > One thing to note is, we are currently working on moving the c8s process > to use the same workflow as the c9s process. That will happen later > this year. Right now, I only build what releases to git.centos.org for > the c8s branch for the kernel. They are looking to get me a new kernel > now. > Excellent news! Thank you. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS Stream 8 sssd.service failing part of sssd-common-2.8.1-1.el8.x86_64 baseos package
On 1/9/23 17:45, Simon Matter wrote: On 1/3/23 13:41, Simon Matter wrote: On 1/3/23 05:17, Orion Poplawski wrote: On 12/30/22 04:06, Jelle de Jong wrote: On 12/27/22 22:55, Gordon Messmer wrote: On 2022-12-25 07:44, Jelle de Jong wrote: 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. ... [sssd] [confdb_expand_app_domains] (0x0010): No domains configured, fatal error! Were you previously using sssd? Or is the problem merely that it is now reporting an error starting a service that you don't use? Are there any files in /etc/sssd/conf.d, or does /etc/sssd/sssd.conf exist? If so, what are the contents of those files? What are the contents of /usr/lib/systemd/system/sssd.service? If you run "journalctl -u sssd.service", are there any log entries older than the package update? I got a monitoring system for failing services and I sudenly started getting dozens of notifications for all my CentOS systems that sssd was failing. This is after the sssd package updates, causing this regression. SSSD services where not really in use but some of the common libraries are used. # 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 Sat 2022-12-24 06:14:10 UTC; 6 days ago Condition: start condition failed at Fri 2022-12-30 11:02:01 UTC; 4s ago ├─ ConditionPathExists=|/etc/sssd/sssd.conf was not met └─ ConditionDirectoryNotEmpty=|/etc/sssd/conf.d was not met Main PID: 3953157 (code=exited, status=4) Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. # ls -halZ /etc/sssd/sssd.conf ls: cannot access '/etc/sssd/sssd.conf': No such file or directory Looks like you need to figure out what happened to your /etc/sssd/sssd.conf file. FWIW - I've updated my one CS8 machine to 2.8.1-1 and it seems to be fine. I did not do anything specific to the configuration file. I tried to reinstall the new sssd-common pacakge, but it will not install the /etc/sssd/sssd.conf file. I can not remove the package because it will remove a lot of packages that I do need. I still think something is wrong with the new sssd packages.. [root@nginx01 ~]# rpm -qplc sssd-common-2.8.1-1.el8.x86_64.rpm /etc/logrotate.d/sssd /etc/pam.d/sssd-shadowutils /etc/rwtab.d/sssd /etc/sssd/sssd.conf Most likely the file /etc/sssd/sssd.conf is a ghost file and therefore it's not installed but only recognized as being part of the package. Simon I do not get this. There has nog been an /etc/sssd/sssd.conf on my system before as it only installed sssd-common due to dependencies for other libaries. I do not use the sssd service. The package gets an update and now my systemd status is failing on a lot of systems and I am being tolled I should get /etc/sssd/sssd.conf sorted? Can you fix the sssd package by either not enabling the sssd systemd service or some other solution that does not make systemd status fail? This is a regression and it is going to cause me a lot of time now to write ansible code for the disabling of the sssd service on all systems that have it installed due to dependencies but do not use it. sssd.services failing regressions and dfn-automatic.serivces failing regressions due to freeipa/sssd/samba conflicts for months now. Do you have a file /etc/sssd/sssd.conf? IIRC you said you don't have such a file, which is fine. no file is there. Do you have any file in /etc/sssd/conf.d/? This directory should be empty but it's possible that another package puts something there. no files are there. Kind regards, Jelle de Jong ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS cloud images, cloud-init
Hello List, At this link, https://cloud.centos.org/altarch/7/images/ I'm trying to use the latest image CentOS-7-x86_64-GenericCloud.qcow2c I cannot log in to the VM because cloud-init did not run. vSphere says open-vm-tools is not running. After having broken into the VM, I see open-vm-tools is installed but not enabled. Does anyone know why/why not? I could be mistaken, but I'm thinking maybe that's why cloud-init doesn't run. Jack ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] dnf-makecache.service failing every few days and dnf-automatic.service samba freeipa issues (again).
On 1/9/23 10:16, Jelle de Jong wrote: Hello everybody, What is the status of the freeipa/sssd and samba conflicts in the repositories? I can not wrap my mind around that two big packages are not getting security updates anymore, because they are conflicting. I will go to FOSDEM in Belgium this year to figure out more, but I am considering moving my centos systems to rockylinux. Kind regards, Jelle de Jong On 12/16/22 16:59, Jelle de Jong wrote: Hello everybody, Could someone give me an estimate on when the repositories are resolving the right dependencies for the freeipa pacakges in CentOS Stream release 8? I have about +10 systems sending me alerts everyday that dnf-automatic.service is failing because of the freeipa dependency issues. Since freeipa is one of the security elements I would like to give people an estimate on when these issues are resolved? How can I keep track of the work that is been done as well? Is there a package tracker to be followed for this? URLs? I asked this question on the centos-devel list weeks ago, but have not received any feedback. The issues is bothering me a lot as it is an security issue that stays unresolved. Kind regards, Jelle de Jong On 11/30/22 13:06, Jelle de Jong wrote: Hello everybody, I attached the dnf conflict logs with conflicting pacakges. Problem 1: package ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 requires libndr.so.2()(64bit), but none of the providers can be installed Problem 2: package ipa-server-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 requires libsamba-errors.so.1(SAMBA_ERRORS_1)(64bit), but none of the providers can be installed Problem 3: problem with installed package ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 Problem 4: problem with installed package ipa-server-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 Kind regards, Jelle On 11/29/22 12:43, Jelle de Jong wrote: Hello everybody, 1. I got many systems with failing dnf-makecache.service because some mirror/repo is tried once and fails. Is there an option to make dnf more reliable, to try the mirror url a few times and check its availability? man yum.conf does not # cat /etc/yum.conf [main] gpgcheck=1 installonly_limit=3 clean_requirements_on_remove=True best=True skip_if_unavailable=False ExecStart=/usr/bin/dnf makecache --timer 2. I saw in the mailing list the messages about samba sssd dependency issues. I got lots of servers failing my dnf-automatic because of this when can I expect a resolution for this? There should not be freeipa/sssd dependency issues in the latest release. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] dnf-makecache.service failing every few days and dnf-automatic.service samba freeipa issues (again).
Am 09.01.23 um 17:16 schrieb Jelle de Jong: Hello everybody, What is the status of the freeipa/sssd and samba conflicts in the repositories? I can not wrap my mind around that two big packages are not getting security updates anymore, because they are conflicting. I will go to FOSDEM in Belgium this year to figure out more, but I am considering moving my centos systems to rockylinux. Kind regards, Jelle de Jong CentOS Stream is an upstream project now. Distro composes will have a state that does not addresses the expectations of the old CentOS project. Further more if security is a concern, then a different OS should be chosen. Some general details about updates here: https://lists.centos.org/pipermail/centos-devel/2021-July/119645.html https://blog.centos.org/2022/09/how-updates-work-in-centos/ and more useful links in the list archives. -- Leon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS Stream 8 sssd.service failing part of sssd-common-2.8.1-1.el8.x86_64 baseos package
> On 1/3/23 13:41, Simon Matter wrote: >>> On 1/3/23 05:17, Orion Poplawski wrote: On 12/30/22 04:06, Jelle de Jong wrote: > On 12/27/22 22:55, Gordon Messmer wrote: >> On 2022-12-25 07:44, Jelle de Jong wrote: >>> 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. >> ... >>> [sssd] [confdb_expand_app_domains] (0x0010): No domains configured, >>> fatal error! >> >> >> Were you previously using sssd? Or is the problem merely that it is >> now reporting an error starting a service that you don't use? >> >> Are there any files in /etc/sssd/conf.d, or does /etc/sssd/sssd.conf >> exist? If so, what are the contents of those files? >> >> What are the contents of /usr/lib/systemd/system/sssd.service? >> >> If you run "journalctl -u sssd.service", are there any log entries >> older than the package update? > > I got a monitoring system for failing services and I sudenly started > getting dozens of notifications for all my CentOS systems that sssd > was failing. This is after the sssd package updates, causing this > regression. SSSD services where not really in use but some of the > common libraries are used. > > # 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 Sat 2022-12-24 06:14:10 > UTC; 6 days ago > Condition: start condition failed at Fri 2022-12-30 11:02:01 UTC; 4s > ago > ├─ ConditionPathExists=|/etc/sssd/sssd.conf was not met > └─ ConditionDirectoryNotEmpty=|/etc/sssd/conf.d was not > met > Main PID: 3953157 (code=exited, status=4) > > Warning: Journal has been rotated since unit was started. Log output > is incomplete or unavailable. > # ls -halZ /etc/sssd/sssd.conf > ls: cannot access '/etc/sssd/sssd.conf': No such file or directory Looks like you need to figure out what happened to your /etc/sssd/sssd.conf file. FWIW - I've updated my one CS8 machine to 2.8.1-1 and it seems to be fine. >>> >>> I did not do anything specific to the configuration file. I tried to >>> reinstall the new sssd-common pacakge, but it will not install the >>> /etc/sssd/sssd.conf file. I can not remove the package because it will >>> remove a lot of packages that I do need. I still think something is >>> wrong with the new sssd packages.. >>> >>> [root@nginx01 ~]# rpm -qplc sssd-common-2.8.1-1.el8.x86_64.rpm >>> /etc/logrotate.d/sssd >>> /etc/pam.d/sssd-shadowutils >>> /etc/rwtab.d/sssd >>> /etc/sssd/sssd.conf >> >> Most likely the file /etc/sssd/sssd.conf is a ghost file and therefore >> it's not installed but only recognized as being part of the package. >> >> Simon > > I do not get this. There has nog been an /etc/sssd/sssd.conf on my > system before as it only installed sssd-common due to dependencies for > other libaries. I do not use the sssd service. The package gets an > update and now my systemd status is failing on a lot of systems and I am > being tolled I should get /etc/sssd/sssd.conf sorted? > > Can you fix the sssd package by either not enabling the sssd systemd > service or some other solution that does not make systemd status fail? > > This is a regression and it is going to cause me a lot of time now to > write ansible code for the disabling of the sssd service on all systems > that have it installed due to dependencies but do not use it. > > sssd.services failing regressions and dfn-automatic.serivces failing > regressions due to freeipa/sssd/samba conflicts for months now. Do you have a file /etc/sssd/sssd.conf? IIRC you said you don't have such a file, which is fine. Do you have any file in /etc/sssd/conf.d/? This directory should be empty but it's possible that another package puts something there. Regards, Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS Stream 8 sssd.service failing part of sssd-common-2.8.1-1.el8.x86_64 baseos package
On 1/3/23 13:41, Simon Matter wrote: On 1/3/23 05:17, Orion Poplawski wrote: On 12/30/22 04:06, Jelle de Jong wrote: On 12/27/22 22:55, Gordon Messmer wrote: On 2022-12-25 07:44, Jelle de Jong wrote: 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. ... [sssd] [confdb_expand_app_domains] (0x0010): No domains configured, fatal error! Were you previously using sssd? Or is the problem merely that it is now reporting an error starting a service that you don't use? Are there any files in /etc/sssd/conf.d, or does /etc/sssd/sssd.conf exist? If so, what are the contents of those files? What are the contents of /usr/lib/systemd/system/sssd.service? If you run "journalctl -u sssd.service", are there any log entries older than the package update? I got a monitoring system for failing services and I sudenly started getting dozens of notifications for all my CentOS systems that sssd was failing. This is after the sssd package updates, causing this regression. SSSD services where not really in use but some of the common libraries are used. # 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 Sat 2022-12-24 06:14:10 UTC; 6 days ago Condition: start condition failed at Fri 2022-12-30 11:02:01 UTC; 4s ago ├─ ConditionPathExists=|/etc/sssd/sssd.conf was not met └─ ConditionDirectoryNotEmpty=|/etc/sssd/conf.d was not met Main PID: 3953157 (code=exited, status=4) Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. # ls -halZ /etc/sssd/sssd.conf ls: cannot access '/etc/sssd/sssd.conf': No such file or directory Looks like you need to figure out what happened to your /etc/sssd/sssd.conf file. FWIW - I've updated my one CS8 machine to 2.8.1-1 and it seems to be fine. I did not do anything specific to the configuration file. I tried to reinstall the new sssd-common pacakge, but it will not install the /etc/sssd/sssd.conf file. I can not remove the package because it will remove a lot of packages that I do need. I still think something is wrong with the new sssd packages.. [root@nginx01 ~]# rpm -qplc sssd-common-2.8.1-1.el8.x86_64.rpm /etc/logrotate.d/sssd /etc/pam.d/sssd-shadowutils /etc/rwtab.d/sssd /etc/sssd/sssd.conf Most likely the file /etc/sssd/sssd.conf is a ghost file and therefore it's not installed but only recognized as being part of the package. Simon I do not get this. There has nog been an /etc/sssd/sssd.conf on my system before as it only installed sssd-common due to dependencies for other libaries. I do not use the sssd service. The package gets an update and now my systemd status is failing on a lot of systems and I am being tolled I should get /etc/sssd/sssd.conf sorted? Can you fix the sssd package by either not enabling the sssd systemd service or some other solution that does not make systemd status fail? This is a regression and it is going to cause me a lot of time now to write ansible code for the disabling of the sssd service on all systems that have it installed due to dependencies but do not use it. sssd.services failing regressions and dfn-automatic.serivces failing regressions due to freeipa/sssd/samba conflicts for months now. Jelle ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] dnf-makecache.service failing every few days and dnf-automatic.service samba freeipa issues (again).
Hello everybody, What is the status of the freeipa/sssd and samba conflicts in the repositories? I can not wrap my mind around that two big packages are not getting security updates anymore, because they are conflicting. I will go to FOSDEM in Belgium this year to figure out more, but I am considering moving my centos systems to rockylinux. Kind regards, Jelle de Jong On 12/16/22 16:59, Jelle de Jong wrote: Hello everybody, Could someone give me an estimate on when the repositories are resolving the right dependencies for the freeipa pacakges in CentOS Stream release 8? I have about +10 systems sending me alerts everyday that dnf-automatic.service is failing because of the freeipa dependency issues. Since freeipa is one of the security elements I would like to give people an estimate on when these issues are resolved? How can I keep track of the work that is been done as well? Is there a package tracker to be followed for this? URLs? I asked this question on the centos-devel list weeks ago, but have not received any feedback. The issues is bothering me a lot as it is an security issue that stays unresolved. Kind regards, Jelle de Jong On 11/30/22 13:06, Jelle de Jong wrote: Hello everybody, I attached the dnf conflict logs with conflicting pacakges. Problem 1: package ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 requires libndr.so.2()(64bit), but none of the providers can be installed Problem 2: package ipa-server-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 requires libsamba-errors.so.1(SAMBA_ERRORS_1)(64bit), but none of the providers can be installed Problem 3: problem with installed package ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 Problem 4: problem with installed package ipa-server-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 Kind regards, Jelle On 11/29/22 12:43, Jelle de Jong wrote: Hello everybody, 1. I got many systems with failing dnf-makecache.service because some mirror/repo is tried once and fails. Is there an option to make dnf more reliable, to try the mirror url a few times and check its availability? man yum.conf does not # cat /etc/yum.conf [main] gpgcheck=1 installonly_limit=3 clean_requirements_on_remove=True best=True skip_if_unavailable=False ExecStart=/usr/bin/dnf makecache --timer 2. I saw in the mailing list the messages about samba sssd dependency issues. I got lots of servers failing my dnf-automatic because of this when can I expect a resolution for this? Kind regards, Jelle ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] centos 8-Streams kernel?
On 1/7/23 13:41, Aleksandar Ivanisevic wrote: Heh, Your sentiments on the website very much mirror my own, although I’m more focused on server applications rather than on desktop (we use Macs and Ubuntu for that). When Red Hat announced Streams, I was terrified at first and my first instinct was to switch to Rocky or a similar 1:1 distro, but then thought there might be something good coming out of the whole ordeal. And indeed it did, we used to run centos on test and RHEL on live systems and having packages (especially kernel) on test a bit in front of the live systems (instead of a bit behind like with the old centos) turned out to be very useful. We were able to catch a nasty lockup bug in a series of kernels around RHEL 8.6, report it, follow its resolution, and although Red Hat did end up releasing an official RHEL kernel with the bug for whatever reason, we were able to avoid it in production, and all was good. Exactly what you want from a distro like Streams. Exactly what Red Hat would expect to get from a distro like Streams, right? However, now that streams kernel has been behind RHEL for months, I begin to wonder, is it a symptom of something? What? Change of direction or simple lack of resources (recession and quiet quitting and all that jazz)? Is it time to switch to the old way (i.e. Rocky) again? One thing to note is, we are currently working on moving the c8s process to use the same workflow as the c9s process. That will happen later this year. Right now, I only build what releases to git.centos.org for the c8s branch for the kernel. They are looking to get me a new kernel now. On 7. Jan 2023, at 20:05, Steven Rosenberg wrote: If you want to follow CentOS Stream development, I have two websites that grab CentOS-supplied XML and publish blog entries of updated packages whenever that happens: https://centos.passthejoe.net/ https://passthejoe.tilde.institute/centos/ Both websites have the same content. Frustration with CentOS Stream 8 development and security -- especially the kernel -- drove me to create this site so progress in both distros (8 Stream and 9 Stream) would be easier to follow. Red Hat employees promised that Stream 9 would solve many of the issues that are troubling in Stream 8, and so far that has been true. On Fri, Jan 6, 2023 at 12:58 PM Aleksandar Ivanisevic < aleksandar.ivanise...@2e-systems.com> wrote: Hi, Does anyone know what is happening with centos 8-Streams kernel? It has been behind RHEL for months now, RHEL8.7 has 4.18.0-425.3.1.el8 built in December and Streams has 4.18.0-408.el8 built all the way back in end October. Is there some policy somewhere that I missed that says that 9 will be now getting the focus or whatnot? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Help with an HP Proliant gen10 plus?
> > > On 1/9/23 01:37, Simon Matter wrote: >>> 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 >> >> Why create an MS-DOS filesystem on the stick which gets immediately >> overwritten in the next step? > > I think the idea is to get that first 4MB set up for booting, as the dd > skips that space. No, what you've set is a dd block size of 4MB. > >> >> >>> # dd bs=4M >>> if=P52581_001_gen10spp-2022.09.01.00-SPP2022090100.2022_0930.1.iso >>> of=/dev/sdb status=progress >> Is this what HPE says how to create the stick? If yes then you may ask >> HPE >> how to get it to work. > > HP gives no instructions. At least I can't find it on the support > pages. I do have a support account. You should be able to simply do dd if=P52581_001_gen10spp-2022.09.01.00-SPP2022090100.2022_0930.1.iso of=/dev/sdb of even simpler cat P52581_001_gen10spp-2022.09.01.00-SPP2022090100.2022_0930.1.iso > /dev/sdb If that's not working I don't know what to do else. Otherwise you could search for an USB disk image instead of an ISO image, I don't know if HPE provides such a thing. BTW, if this server has an HPE ILO, you can upgrade firmware directly from there. Regards, Simon > > You should just 'know' how to build a bootable device from a 9GB iso > image. > > >> >>> 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. >> That's usually fine because the cdrom can be mounted as loop device. No >> need for a real cdrom. > > Yeah. Going to work on it some more today. Plus got a finish a paper > for a symposium. I give up on learning tex; I found a word template > that can create the right pdf, so pull out all my writing in tex and > start over. And I DO use the IETF's xml format for creating Internet > Drafts, so I am teachable on this stuff despite my age... > > I do vaguely recall working with tex for writing back around '78, but > that was it. > >> >> Regards, >> Simon >> >> ___ >> CentOS mailing list >> CentOS@centos.org >> https://lists.centos.org/mailman/listinfo/centos > > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Help with an HP Proliant gen10 plus?
On 1/9/23 01:37, Simon Matter wrote: 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 Why create an MS-DOS filesystem on the stick which gets immediately overwritten in the next step? I think the idea is to get that first 4MB set up for booting, as the dd skips that space. # dd bs=4M if=P52581_001_gen10spp-2022.09.01.00-SPP2022090100.2022_0930.1.iso of=/dev/sdb status=progress Is this what HPE says how to create the stick? If yes then you may ask HPE how to get it to work. HP gives no instructions. At least I can't find it on the support pages. I do have a support account. You should just 'know' how to build a bootable device from a 9GB iso image. 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. That's usually fine because the cdrom can be mounted as loop device. No need for a real cdrom. Yeah. Going to work on it some more today. Plus got a finish a paper for a symposium. I give up on learning tex; I found a word template that can create the right pdf, so pull out all my writing in tex and start over. And I DO use the IETF's xml format for creating Internet Drafts, so I am teachable on this stuff despite my age... I do vaguely recall working with tex for writing back around '78, but that was it. Regards, Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RAID1 setup
On Mon, Jan 09, 2023 at 07:32:02AM +0100, Simon Matter wrote: Hi Continuing this thread, and focusing on RAID1. I got an HPE Proliant gen10+ that has hardware RAID support. (can turn it off if I want). What exact model of RAID controller is this? If it's a S100i SR Gen10 then it's not hardware RAID at all. Yes it is the S100i SR. For HW RAID there is a e208i-p card available that can use the single PCI slot. jl -- Jon H. LaBadie j...@labadie.us ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
