[CentOS] 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
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) ___ 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 sssd issues (again).
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[root@freeipa01 ~]# yum clean all 49 files removed [root@freeipa01 ~]# yum update --refresh --skip-broken CentOS Stream 8 - AppStream 17 MB/s | 26 MB 00:01 CentOS Stream 8 - BaseOS 17 MB/s | 26 MB 00:01 CentOS Stream 8 - Extras 52 kB/s | 18 kB 00:00 CentOS Stream 8 - Extras common packages1.9 kB/s | 5.2 kB 00:02 Extra Packages for Enterprise Linux 8 - x86_64 10 MB/s | 13 MB 00:01 Extra Packages for Enterprise Linux 8 - Next - 1.9 MB/s | 1.4 MB 00:00 Last metadata expiration check: 0:00:01 ago on Wed Nov 30 13:03:26 2022. Error: 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 - package ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 requires libndr.so.2(NDR_0.0.1)(64bit), but none of the providers can be installed - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.16.4-2.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.3-0.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.4-0.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.5-0.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.5-3.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.5-4.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.5-5.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.5-8.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.16.1-0.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.16.2-1.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.16.4-1.el8.x86_64 - cannot install the best update candidate for package samba-client-libs-4.16.4-2.el8.x86_64 - cannot install the best update candidate for package ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 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 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.13.3-3.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.14.4-4.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.14.5-0.el8.x86_64 - cannot install both samba
[CentOS] CentOS Stream 8 sssd.service failing part of sssd-common-2.8.1-1.el8.x86_64 baseos package
Hello everybody, 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. What is the best way to report this issue and when can we expect an update from the sssd-common package for this regression bug? I think sssd-common is part of the baseos repository and installed even when the configuration file is not installed. If someone can also provide more details on this issue I would appreciate it. Thank you all in advance, Kind regards, Jelle de Jong # cat /var/log/dnf.log | grep sssd-common 2022-11-25T06:29:42+0100 DEBUG Upgraded: sssd-common-2.7.3-5.el8.x86_64 2022-11-25T06:29:42+0100 DDEBUG /var/cache/dnf/baseos-055ffcb2ec25a27f/packages/sssd-common-2.7.3-5.el8.x86_64.rpm removed 2022-11-26T06:08:38+0100 DEBUG Upgraded: sssd-common-2.7.3-5.0.1.el8.x86_64 2022-11-26T06:08:38+0100 DDEBUG /var/cache/dnf/baseos-055ffcb2ec25a27f/packages/sssd-common-2.7.3-5.0.1.el8.x86_64.rpm removed 2022-12-25T06:23:42+0100 DEBUG Upgraded: sssd-common-2.8.1-1.el8.x86_64 2022-12-25T06:23:43+0100 DDEBUG /var/cache/dnf/baseos-055ffcb2ec25a27f/packages/sssd-common-2.8.1-1.el8.x86_64.rpm removed # cat /etc/os-release NAME="CentOS Stream" VERSION="8" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="8" PLATFORM_ID="platform:el8" PRETTY_NAME="CentOS Stream 8" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:8" HOME_URL="https://centos.org/"; BUG_REPORT_URL="https://bugzilla.redhat.com/"; REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 8" REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream" # cat /var/log/sssd/sssd.log (2022-12-25 6:23:34): [sssd] [monitor_quit_signal] (0x3f7c0): Monitor received Terminated: terminating children (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Returned with: 0 (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Terminating [nss][302626] (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Child [nss] terminated with a signal (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Terminating [implicit_files][302625] (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Child [implicit_files] terminated with a signal [sssd] [confdb_expand_app_domains] (0x0010): No domains configured, fatal error! [sssd] [get_monitor_config] (0x0010): Failed to expand application domains [sssd] [confdb_get_domains] (0x0020): No domains configured, fatal error! [sssd] [get_monitor_config] (0x0010): No domains configured. [sssd] [main] (0x0010): SSSD couldn't load the configuration database [1432158246]: No domain is enabled # cat /var/log/sssd/sssd.log (2022-12-25 6:23:34): [sssd] [monitor_quit_signal] (0x3f7c0): Monitor received Terminated: terminating children (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Returned with: 0 (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Terminating [nss][302626] (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Child [nss] terminated with a signal (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Terminating [implicit_files][302625] (2022-12-25 6:23:34): [sssd] [monitor_quit] (0x3f7c0): Child [implicit_files] terminated with a signal [sssd] [confdb_expand_app_domains] (0x0010): No domains configured, fatal error! [sssd] [get_monitor_config] (0x0010): Failed to expand application domains [sssd] [confdb_get_domains] (0x0020): No domains configured, fatal error! [sssd] [get_monitor_config] (0x0010): No domains configured. [sssd] [main] (0x0010): SSSD couldn't load the configuration database [1432158246]: No domain is enabled # 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 Sun 2022-12-25 06:23:35 CET; 9h ago Main PID: 615303 (code=exited, status=4) ___ 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 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 -halt /etc/sssd/conf.d/ total 8.0K drwx--x--x. 2 sssd sssd 4.0K Dec 8 13:08 . drwx--. 4 sssd sssd 4.0K Dec 8 13:08 .. # ls -halZ /etc/sssd/conf.d/ total 8.0K drwx--x--x. 2 sssd sssd system_u:object_r:sssd_conf_t:s0 4.0K Dec 8 13:08 . drwx--. 4 sssd sssd system_u:object_r:sssd_conf_t:s0 4.0K Dec 8 13:08 .. # ls -halZ /etc/sssd/sssd.conf ls: cannot access '/etc/sssd/sssd.conf': No such file or directory # journalctl -u sssd.service --lines 10 -- Logs begin at Mon 2022-12-26 22:15:31 UTC, end at Fri 2022-12-30 11:05:26 UTC. -- -- No entries -- Kind regards, Jelle de Jong ___ 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 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 ___ 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 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 [root@nginx01 ~]# rpm -ivh --force sssd-common-2.8.1-1.el8.x86_64.rpm Verifying... # [100%] Preparing... # [100%] Updating / installing... 1:sssd-common-2.8.1-1.el8 # [100%] [root@nginx01 ~]# ls -hal /etc/sssd/sssd.conf Kind regards, Jelle ls: cannot access '/etc/sssd/sssd.conf': No such file or directory ___ 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 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] 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
Re: [CentOS] CentOS Stream 8 sssd.service failing part of sssd-common-2.8.1-1.el8.x86_64 baseos package
On 1/13/23 11:52, Leon Fauster via CentOS wrote: Am 13.01.23 um 05:34 schrieb Orion Poplawski: 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 -halt /etc/sssd/conf.d/ total 8.0K drwx--x--x. 2 sssd sssd 4.0K Dec 8 13:08 . drwx--. 4 sssd sssd 4.0K Dec 8 13:08 .. # ls -halZ /etc/sssd/conf.d/ total 8.0K drwx--x--x. 2 sssd sssd system_u:object_r:sssd_conf_t:s0 4.0K Dec 8 13:08 . drwx--. 4 sssd sssd system_u:object_r:sssd_conf_t:s0 4.0K Dec 8 13:08 .. # ls -halZ /etc/sssd/sssd.conf ls: cannot access '/etc/sssd/sssd.conf': No such file or directory # journalctl -u sssd.service --lines 10 -- Logs begin at Mon 2022-12-26 22:15:31 UTC, end at Fri 2022-12-30 11:05:26 UTC. -- -- No entries -- Kind regards, Jelle de Jong I don't quite understand where this: Main PID: 3953157 (code=exited, status=4) came from. As it seems like sssd was started at some point and failed. But that shouldn't have happened because: 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 It's telling you that because /etc/sssd/sssd.conf does not exist and /etc/sssd/sssd.conf.d is not empty, the service was not started because the conditions were not met. This is as expected in your case. If you don't want it to even check, just disable the service: systemctl disable sssd.service Before doing this; @OP: what's the output of: # authselect current ]# authselect current Profile ID: sssd Enabled features: None I wrote the following Ansible code to automate disabling the sssd service I still consider this a regression as it just started apearing on all the systems. - name: get sssd service status ansible.builtin.systemd: name: sssd.service register: sssd - name: disable sssd.service service status ansible.builtin.systemd: name: sssd.service enabled: false state: stopped when: - sssd.status.ActiveState is defined - sssd.status.ActiveState == "failed" - name: systemctl reset-failed command: systemctl reset-failed args: warn: false when: - sssd.status.ActiveState is defined - sssd.status.ActiveState == "failed" ___ 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 19:06, Johnny Hughes wrote: 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. These are the freeipa/samba issue I am having all other packages are updated... and the server got rebooted as well. dnf-automatic is failing because of these conflicts. ● dnf-automatic.service loaded failed failed dnf automatic [root@freeipa01 ~]# yum update --best --allowerasing --skip-broken --refresh CentOS Stream 8 - AppStream 14 kB/s | 4.4 kB 00:00 CentOS Stream 8 - BaseOS 79 kB/s | 3.9 kB 00:00 CentOS Stream 8 - Extras 11 kB/s | 2.9 kB 00:00 CentOS Stream 8 - Extras common packages 13 kB/s | 3.0 kB 00:00 Extra Packages for Enterprise Linux 8 - x86_64 43 kB/s | 26 kB 00:00 Extra Packages for Enterprise Linux 8 - Next - x86_64 69 kB/s | 32 kB 00:00 Error: Problem: cannot install the best update candidate for package ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 - problem with installed package ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 - package ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 requires libndr-nbt.so.0()(64bit), but none of the providers can be installed - package ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 requires libndr-nbt.so.0(NDR_NBT_0.0.1)(64bit), but none of the providers can be installed - package ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 requires libsamba-passdb.so.0()(64bit), but none of the providers can be installed - package ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 requires libsamba-passdb.so.0(SAMBA_PASSDB_0.2.0)(64bit), but none of the providers can be installed - package ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 requires libsamba-util.so.0()(64bit), but none of the providers can be installed - package ipa-server-trust-ad-4.9.10-6.module_el8.7.0+1209+42bcbcde.x86_64 requires libsamba-util.so.0(SAMBA_UTIL_0.0.1)(64bit), but none of
[CentOS] regression in libsmbclient-4.17.5-0.el8.x86_64 with nextcloud Kerberos smb intergration
Hello everybody,
Just reporting a regression with libsmbclient 4.17.5,
php-smbclient-1.0.6-1.el8.remi.8.1.x86_64 and nextcloud 25.0.3.2
I have not found the cause nor the solution, but for other users I am
reporting a workaround here:
[root@nextcloud01 ~]# yum downgrade libsmbclient-4.17.2-2.el8.x86_64
[root@nextcloud01 ~]# systemctl restart php-fpm.service
Kind regards,
Jelle de Jong
Error PHP Error: Undefined array key 1 at
/var/www/html/nextcloud/apps/files_external/3rdparty/icewind/smb/src/Native/NativeFileInfo.php#46
at lib/private/Log/ErrorHandler.php line 92 2023-02-11T16:09:01+01:00
0.
apps/files_external/3rdparty/icewind/smb/src/Native/NativeFileInfo.php
line 46
OC\Log\ErrorHandler::onError(
)
1.
apps/files_external/3rdparty/icewind/smb/src/Native/NativeFileInfo.php
line 69
Icewind\SMB\Native\NativeFileInfo->stat(
)
2.
apps/files_external/3rdparty/icewind/smb/src/Native/NativeShare.php line
114
Icewind\SMB\Native\NativeFileInfo->getSize(
)
3.
apps/files_external/lib/Lib/Storage/SMB.php line 191
Icewind\SMB\Native\NativeShare->stat(
)
4.
apps/files_external/lib/Lib/Storage/SMB.php line 348
OCA\Files_External\Lib\Storage\SMB->getFileInfo(
)
5.
lib/private/Files/Storage/Common.php line 462
OCA\Files_External\Lib\Storage\SMB->stat(
)
6.
apps/files_external/lib/Lib/Storage/SMB.php line 729
OC\Files\Storage\Common->test(
)
7.
apps/files_external/lib/MountConfig.php line 131
OCA\Files_External\Lib\Storage\SMB->test(
)
8.
apps/files_external/lib/Controller/StoragesController.php line 288
OCA\Files_External\MountConfig::getBackendStatus("*** sensitive
parameters replaced ***")
9.
apps/files_external/lib/Controller/UserGlobalStoragesController.php line
126
OCA\Files_External\Controller\StoragesController->updateStorageStatus("***
sensitive parameters replaced ***")
10.
lib/private/AppFramework/Http/Dispatcher.php line 225
OCA\Files_External\Controller\UserGlobalStoragesController->show(
)
11.
lib/private/AppFramework/Http/Dispatcher.php line 133
OC\AppFramework\Http\Dispatcher->executeController(
)
12. lib/private/AppFramework/App.php
line 172
OC\AppFramework\Http\Dispatcher->dispatch(
)
13. lib/private/Route/Router.php line
298
OC\AppFramework\App::main(
)
14. lib/base.php line 1047
OC\Route\Router->match(
)
15. index.php line 36
OC::handleRequest(
)
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
[CentOS] wget http://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/images/pxeboot/vmlinuz --max-redirect=0 --no-hsts
Hello everybody, I am using pxelinux to install centos stream 9 systems but this stopped working a while ago with mirror.stream.centos.org because it started forcing HTTPS and pxelinux is HTTP only. Could we please make the mirror.stream.centos.org HTTP available again please? $ wget http://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/images/pxeboot/vmlinuz --max-redirect=0 --no-hsts --2023-03-29 20:49:54-- http://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/images/pxeboot/vmlinuz Resolving mirror.stream.centos.org (mirror.stream.centos.org)... 18.173.233.69, 18.173.233.28, 18.173.233.77, ... Connecting to mirror.stream.centos.org (mirror.stream.centos.org)|18.173.233.69|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/images/pxeboot/vmlinuz [following] 0 redirections exceeded. Kind regards, Jelle de Jong ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] wget http://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/images/pxeboot/vmlinuz --max-redirect=0 --no-hsts
On 3/30/23 07:11, Gordon Messmer wrote: On 2023-03-29 11:52, Jelle de Jong wrote: I am using pxelinux to install centos stream 9 systems but this stopped working a while ago with mirror.stream.centos.org because it started forcing HTTPS and pxelinux is HTTP only. I believe the recommended configuration is to have vmlinuz and initrd.img on the same tftp server you use for the PXE boot loader. https://docs.fedoraproject.org/en-US/fedora/f36/install-guide/advanced/Network_based_Installations/ I use a lot of other distributions as well, and debian, ubuntu, all offer HTTP for their mirrors. This way an update is directly used, I used to download the vmlinux if it gets out of date it gives weird errors when loading the kernels further in the process. Thank you in advance for making the mirror.stream.centos.org work with HTTP again and letting users choose between HTTP and HTTPS. Kind regards, Jelle de Jong ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] /bin/journalctl --flush hangs on CentOS Stream release 8
Hello everybody, Somehting is causing /bin/journalctl --flush to hang on some new and existing installations of on CentOS Stream release 8 # journalctl --disk-usage Archived and active journals take up 8.0M in the file system. # journalctl --verify PASS: /run/log/journal/48651cee389b4600bf559fb29d1c2066/system.journal # /usr/bin/journalctl --flush ^C Do other users have this as well and is there a fix or update pending? Kind regards, Jelle de Jong ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Problem: cannot install the best update candidate for package pki-servlet-engine-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch
Hello everybody, What might be going wrong here? Is there an upstream bug report? How to proceed? # yum update --refresh CentOS Stream 8 - AppStream 10 kB/s | 4.4 kB 00:00 CentOS Stream 8 - BaseOS 45 kB/s | 3.9 kB 00:00 CentOS Stream 8 - Extras 11 kB/s | 2.9 kB 00:00 CentOS Stream 8 - Extras common packages 57 kB/s | 3.0 kB 00:00 CentOS Stream 8 - PowerTools 19 kB/s | 4.4 kB 00:00 Extra Packages for Enterprise Linux 8 - x86_64 113 kB/s | 32 kB 00:00 Extra Packages for Enterprise Linux 8 - Next - x86_64 422 kB/s | 32 kB 00:00 Error: Problem: 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-12.el8.noarch from appstream and tomcat-lib-1:9.0.62-12.el8.noarch from appstream obsolete pki-servlet-engine - package tomcat-jsp-2.3-api-1:9.0.62-12.el8.noarch from appstream requires tomcat-servlet-4.0-api = 1:9.0.62-12.el8, but none of the providers can be installed - package tomcat-lib-1:9.0.62-12.el8.noarch from appstream requires tomcat-servlet-4.0-api = 1:9.0.62-12.el8, but none of the providers can be installed - package tomcat-servlet-4.0-api-1:9.0.62-12.el8.noarch from appstream is filtered out by modular filtering (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Kind regards, Jelle de Jong ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problem: cannot install the best update candidate for package pki-servlet-engine-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch
Hello everybody, It has been almost a full month now and the issue with tomcat is still present. How should I report this issue and what is going on with the qa? # yum upgrade --refresh CentOS Stream 8 - AppStream 8.4 kB/s | 4.4 kB 00:00 CentOS Stream 8 - AppStream 6.9 MB/s | 33 MB 00:04 CentOS Stream 8 - BaseOS 71 kB/s | 3.9 kB 00:00 CentOS Stream 8 - BaseOS 13 MB/s | 48 MB 00:03 CentOS Stream 8 - Extras 56 kB/s | 2.9 kB 00:00 CentOS Stream 8 - Extras common packages 13 kB/s | 3.0 kB 00:00 CentOS Stream 8 - PowerTools 63 kB/s | 4.4 kB 00:00 CentOS Stream 8 - PowerTools 5.7 MB/s | 6.5 MB 00:01 Extra Packages for Enterprise Linux 8 - x86_64 37 kB/s | 14 kB 00:00 Extra Packages for Enterprise Linux 8 - x86_64 5.6 MB/s | 16 MB 00:02 Extra Packages for Enterprise Linux 8 - Next - x86_64 460 kB/s | 33 kB 00:00 Error: Problem: 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-12.el8.noarch and tomcat-lib-1:9.0.62-12.el8.noarch obsolete pki-servlet-engine - package tomcat-jsp-2.3-api-1:9.0.62-12.el8.noarch requires tomcat-servlet-4.0-api = 1:9.0.62-12.el8, but none of the providers can be installed - package tomcat-lib-1:9.0.62-12.el8.noarch requires tomcat-servlet-4.0-api = 1:9.0.62-12.el8, but none of the providers can be installed - package tomcat-servlet-4.0-api-1:9.0.62-12.el8.noarch is filtered out by modular filtering (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Kind regards, Jelle de Jong On 9/6/23 21:09, Jelle de Jong wrote: Hello everybody, What might be going wrong here? Is there an upstream bug report? How to proceed? # yum update --refresh CentOS Stream 8 - AppStream 10 kB/s | 4.4 kB 00:00 CentOS Stream 8 - BaseOS 45 kB/s | 3.9 kB 00:00 CentOS Stream 8 - Extras 11 kB/s | 2.9 kB 00:00 CentOS Stream 8 - Extras common packages 57 kB/s | 3.0 kB 00:00 CentOS Stream 8 - PowerTools 19 kB/s | 4.4 kB 00:00 Extra Packages for Enterprise Linux 8 - x86_64 113 kB/s | 32 kB 00:00 Extra Packages for Enterprise Linux 8 - Next - x86_64 422 kB/s | 32 kB 00:00 Error: Problem: 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-12.el8.noarch from appstream and tomcat-lib-1:9.0.62-12.el8.noarch from appstream obsolete pki-servlet-engine - package tomcat-jsp-2.3-api-1:9.0.62-12.el8.noarch from appstream requires tomcat-servlet-4.0-api = 1:9.0.62-12.el8, but none of the providers can be installed - package tomcat-lib-1:9.0.62-12.el8.noarch from appstream requires tomcat-servlet-4.0-api = 1:9.0.62-12.el8, but none of the providers can be installed - package tomcat-servlet-4.0-api-1:9.0.62-12.el8.noarch from appstream is filtered out by modular filtering (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Kind regards, Jelle de Jong ___ 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] Problem: cannot install the best update candidate for package pki-servlet-engine-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch
Hello everybody, On 9/30/23 17:37, Fabian Arrotin wrote: On 30/09/2023 16:08, Jelle de Jong wrote: Hello everybody, It has been almost a full month now and the issue with tomcat is still present. How should I report this issue and what is going on with the qa? # yum upgrade --refresh CentOS Stream 8 - AppStream 8.4 kB/s | 4.4 kB 00:00 CentOS Stream 8 - AppStream 6.9 MB/s | 33 MB 00:04 CentOS Stream 8 - BaseOS 71 kB/s | 3.9 kB 00:00 CentOS Stream 8 - BaseOS 13 MB/s | 48 MB 00:03 CentOS Stream 8 - Extras 56 kB/s | 2.9 kB 00:00 CentOS Stream 8 - Extras common packages 13 kB/s | 3.0 kB 00:00 CentOS Stream 8 - PowerTools 63 kB/s | 4.4 kB 00:00 CentOS Stream 8 - PowerTools 5.7 MB/s | 6.5 MB 00:01 Extra Packages for Enterprise Linux 8 - x86_64 37 kB/s | 14 kB 00:00 Extra Packages for Enterprise Linux 8 - x86_64 5.6 MB/s | 16 MB 00:02 Extra Packages for Enterprise Linux 8 - Next - x86_64 460 kB/s | 33 kB 00:00 Error: Problem: 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-12.el8.noarch and tomcat-lib-1:9.0.62-12.el8.noarch obsolete pki-servlet-engine - package tomcat-jsp-2.3-api-1:9.0.62-12.el8.noarch requires tomcat-servlet-4.0-api = 1:9.0.62-12.el8, but none of the providers can be installed - package tomcat-lib-1:9.0.62-12.el8.noarch requires tomcat-servlet-4.0-api = 1:9.0.62-12.el8, but none of the providers can be installed - package tomcat-servlet-4.0-api-1:9.0.62-12.el8.noarch is filtered out by modular filtering (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Kind regards, Jelle de Jong Tried to install on a stream8 container and it seems to work ; sudo dnf install tomcat-servlet-4.0-api Last metadata expiration check: 0:01:26 ago on Sat Sep 30 17:32:34 2023. Dependencies resolved. === Package Architecture Version Repository Size === Installing: tomcat-servlet-4.0-api noarch 1:9.0.62-14.el8 appstream 286 k Transaction Summary === Install 1 Package Total download size: 286 k Installed size: 609 k But what I see in your output is this : package tomcat-servlet-4.0-api-1:9.0.62-12.el8.noarch is filtered out by modular filtering So it seems you don't use plain/vanilla yum/dnf config for your repositories or modules ? The package seems to be conflicting with ipa-server packages. # yum update --refresh --nobest CentOS Stream 8 - AppStream 17 kB/s | 4.4 kB 00:00 CentOS Stream 8 - BaseOS 17 kB/s | 3.9 kB 00:00 CentOS Stream 8 - Extras 16 kB/s | 2.9 kB 00:00 CentOS Stream 8 - Extras common packages 13 kB/s | 3.0 kB 00:00 CentOS Stream 8 - PowerTools 67 kB/s | 4.4 kB 00:00 Extra Packages for Enterprise Linux 8 - x86_64 52 kB/s | 28 kB 00:00 Extra Packages for Enterprise Linux 8 - Next - x86_64 394 kB/s | 33 kB 00:00 Dependencies resolved. Problem: 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-12.el8.noarch from appstream and tomcat-lib-1:9.0.62-12.el8.noarch from appstream obsolete pki-servlet-engi
