- ARCHIVED: Uyuni Users

Error "installation medium unavailable" when using autoinstall distro based on tftpboot-installation (SLE-15-SP4-x86_64)
by Heiner W. 25 Aug '22

25 Aug '22

Hi List, for autoinstalling SLES15-SP4 i tried to use the Data from tftpboot-installation package as stated in Uyuni Client Config Documentation "Distribution Based on a RPM Package." (https://www.uyuni-project.org/uyuni-docs/en/uyuni/client-configuration/auto…) i queried RPM "tftpboot-installation-SLE-15-SP4-x86_64-16.57.20-150400.1.18.noarch.rpm" on my uyuni Server and found out it installs into "/usr/share/tftpboot-installation" My autoinstall distro files are stored in "/var/autoinstall" where i have plenty of space, so i symlinked: ln -s /var/autoinstall/tftpboot-installation /usr/share/tftpboot-installation After "zypper install"ing said RPM i found this content in "/var/autoinstall/tftpboot-installation/SLE-15-SP4-x86_64/": EFI README boot net In uyuni gui i created my autoinstall distro using tree path "/var/autoinstall/tftpboot-installation/SLE-15-SP4-x86_64" and created matching profile and activation key. I found no special instructions in documentation when using tftpboot-installation instead of full ISO, so i sticked to the defaults. Cobbler shows my new autoinstall distro/profile. When trying to install a System it is able to load linuxrc but says "installation medium unavailable". Uyuni Tomcat logs this: 2022-08-24 15:39:44,266 [ajp-nio-0:0:0:0:0:0:0:1-8009-exec-1] ERROR com.redhat.rhn.frontend.action.common.DownloadFile - //var/autoinstall/tftpboot-installation/SLE-15-SP4-x86_64/content Not Found .. 404! 2022-08-24 15:39:44,272 [ajp-nio-0:0:0:0:0:0:0:1-8009-exec-8] ERROR com.redhat.rhn.frontend.action.common.DownloadFile - //var/autoinstall/tftpboot-installation/SLE-15-SP4-x86_64/repodata/repomd.xml Not Found .. 404! 2022-08-24 15:39:44,278 [ajp-nio-0:0:0:0:0:0:0:1-8009-exec-3] ERROR com.redhat.rhn.frontend.action.common.DownloadFile - //var/autoinstall/tftpboot-installation/SLE-15-SP4-x86_64/media.1/products Not Found .. 404! It seems like i must set a special path to further Data (media/repos) that isn't included in tftpboot-installation but i don't know what to configure where. For older SLES SPs i downloaded the full 12GB install iso (like "SLE-15-SP3-Full-x86_64-GM-Media1"), unpacked it and put all files into uyuni "tree path" directory of its autoinstall distro. It would be great if i wouldn't need that extra space for SP4 as all RPMs are already stored within my synced Upstream/Product and CLM Repos. Any hint is much appreciated! Thanks, Heiner

1 1

Uyuni 2022.08 is released!
by Julio Gonzalez 24 Aug '22

24 Aug '22

VERY IMPORTANT: 2022.08 requires special procedures if you are not already using Uyuni 2022.06! The configuration files for the proxy on containers also needs to be updated. Make sure you read the release notes before updating! We are happy to announce the availability of Uyuni 2022.08. Most openSUSE mirrors should already have 2022.08, but if you do not see it yet, wait a few hours until your local openSUSE mirror is synced. At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2022.08, including the release notes, documentation, requirements and setup instructions. This is the list of highlights for this release: - Ubuntu 22.04 as client - GPG key handling in Uyuni - Disabling locally defined repositories - Technology Preview: Helm chart to deploy containerized Uyuni Proxy and Retail Branch Server Remember that Uyuni will follow a rolling release planning, so the next version will contain bugfixes for this one and any new features. There will be no maintenance of 2022.08 As always, we hope you will enjoy Uyuni 2022.08 and we invite everyone of you to send us your feedback [1] and of course your patches, if you can contribute. Happy hacking! [1] https://www.uyuni-project.org/pages/contact.html -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

6 18

[uyuni-users] Fresh Install uyuni 2020.05 Error generating bootstrap repo
by Thomas Weis 24 Aug '22

24 Aug '22

Hello everyone we are configuring a fresh installation of Uyuni 2020.05 After a successful reposync of SUSE Linux Enterprise Server 15 SP1 x86_64 we get an error message: Type: Creating Bootstrap Repository failed Summary: Error generating bootstrap repo for: SLE-15-SP1-x86_64 show details said: ERROR: package 'hwdata' not found ERROR: package 'python3-hwdata' not found ERROR: package 'python3-rhnlib' not found ERROR: package 'spacewalk-check' not found ERROR: package 'spacewalk-client-setup' not found ERROR: package 'spacewalk-client-tools' not found ERROR: package 'python3-spacewalk-check' not found ERROR: package 'python3-spacewalk-client-setup' not found ERROR: package 'python3-spacewalk-client-tools' not found ERROR: package 'python3-uyuni-common-libs' not found ERROR: none of 'mgr-daemon', 'spacewalksd' found ERROR: package 'suseRegisterInfo' not found ERROR: package 'python3-suseRegisterInfo' not found ERROR: package 'zypp-plugin-spacewalk' not found ERROR: package 'python3-zypp-plugin-spacewalk' not found The installation was error-free, we proceeded exactly according to the documentation. What is our mistake? thanks for suggestions Regards Thomas-- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

3 2

IMPORTANT: Problems creating the bootstrap repository for Ubuntu 22.04
by Julio Gonzalez 17 Aug '22

17 Aug '22

Hello, There's a bug affecting Uyuni 2022.08 and the bootstrap repository creating for Ubuntu 22.04. Please check https://github.com/uyuni-project/uyuni/issues/5764#issuecomment-1217969673 for all the information about the problem, and how apply the fix Uyuni for 2022.08. The fix will be part of Uyuni 2022.09. Thanks to kyle-aas, Lukas Magauer (lumarel) and Chri (chr78) for the bug report and all the help provided for debugging the issue. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

AW: RE: Subtask mgr-update-reporting failed.
by Crefeld, Tobias LKV Bayern e.V. 16 Aug '22

16 Aug '22

Hi Robert, "ping lkv-srvapp39" and "host lkv-srvapp39" work as expected. A request with psql works fine, too: uyuni@lkv-srvapp39:~> psql -h lkv-srvapp39 Passwort für Benutzer uyuni: psql (14.3) SSL-Verbindung (Protokoll: TLSv1.3, Verschlüsselungsmethode: TLS_AES_256_GCM_SHA384, Bits: 256, Komprimierung: aus) Geben Sie »help« für Hilfe ein. uyuni=# How can I add the short name to the "TLS SAN"? Where can I configure the host name the application is using? I don't know if It is important, but according to the status of systemctl Uyuni's applications connect to the DB-server via 127.0.0.1 which resolves to localhost: lkv-srvapp39:/var/lib/pgsql/data # systemctl status postgresql ● postgresql.service - PostgreSQL database server Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2022-08-02 10:41:35 CEST; 2 weeks 0 days ago Process: 2357 ExecStart=/usr/share/postgresql/postgresql-script start (code=exited, status=0/SUCCESS) Main PID: 2388 (postgres) Tasks: 43 (limit: 4915) CGroup: /system.slice/postgresql.service ├─ 828 "postgres: uyuni uyuni 127.0.0.1(49822) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 829 "postgres: uyuni uyuni 127.0.0.1(49824) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 830 "postgres: uyuni uyuni 127.0.0.1(49826) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 2388 /usr/lib/postgresql14/bin/postgres -D /var/lib/pgsql/data ├─ 2430 "postgres: logger " "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ""> ├─ 2445 "postgres: checkpointer " "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 2446 "postgres: background writer " "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 2447 "postgres: walwriter " "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 2448 "postgres: autovacuum launcher " "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 2451 "postgres: archiver last was 00000001000000CD000000B0" "" "" "" "" "" ├─ 2452 "postgres: stats collector " "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 2453 "postgres: logical replication launcher " "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 2926 "postgres: uyuni uyuni ::1(39194) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 4397 "postgres: uyuni uyuni 127.0.0.1(48680) idle in transaction" ├─ 4403 "postgres: uyuni uyuni 127.0.0.1(48688) idle in transaction" ├─ 4472 "postgres: uyuni uyuni 127.0.0.1(48692) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5145 "postgres: uyuni uyuni 127.0.0.1(48694) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5146 "postgres: uyuni uyuni 127.0.0.1(48696) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5147 "postgres: uyuni uyuni 127.0.0.1(48700) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5148 "postgres: uyuni uyuni 127.0.0.1(48702) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5149 "postgres: uyuni uyuni 127.0.0.1(48704) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5150 "postgres: uyuni uyuni 127.0.0.1(48706) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5151 "postgres: uyuni uyuni 127.0.0.1(48708) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5152 "postgres: uyuni uyuni 127.0.0.1(48710) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5153 "postgres: uyuni uyuni 127.0.0.1(48712) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5155 "postgres: uyuni uyuni 127.0.0.1(48714) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5156 "postgres: uyuni uyuni 127.0.0.1(48716) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5157 "postgres: uyuni uyuni 127.0.0.1(48718) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5159 "postgres: uyuni uyuni 127.0.0.1(48720) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5160 "postgres: uyuni uyuni 127.0.0.1(48722) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5161 "postgres: uyuni uyuni 127.0.0.1(48724) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5226 "postgres: uyuni uyuni 127.0.0.1(48740) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5227 "postgres: uyuni uyuni 127.0.0.1(48738) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─ 5228 "postgres: uyuni uyuni 127.0.0.1(48736) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─12183 "postgres: uyuni uyuni ::1(39198) idle in transaction" "" "" "" "" "" ├─17094 "postgres: uyuni uyuni 127.0.0.1(48018) idle in transaction" ├─18174 "postgres: uyuni uyuni 127.0.0.1(48204) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─22694 "postgres: uyuni uyuni 127.0.0.1(50300) idle in transaction" ├─22915 "postgres: uyuni uyuni 127.0.0.1(48214) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─25894 "postgres: uyuni uyuni 127.0.0.1(52958) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─25895 "postgres: uyuni uyuni 127.0.0.1(52960) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ├─26392 "postgres: uyuni uyuni 127.0.0.1(52962) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" └─26670 "postgres: uyuni uyuni 127.0.0.1(48228) idle" "" "" "" "" "" "" "" "" "" "" "" "" "" "" Notice: journal has been rotated since unit was started, output may be incomplete. BTW: Meanwhile the number of Taskomatic jobs that fail is increasing and since 3 days Uyuni stopped to check patch and config status of its clients. Just as it happened to the ssh clients since the update of Uyuni. No configuration changes since last week. Maybe it's better to recover the system to a version before the update. Regards, Tobias. -----Ursprüngliche Nachricht----- Von: Robert Paschedag [mailto:robert.paschedag@web.de] org.postgresql.util.PSQLException: The hostname lkv-srvapp39 could not be verified by hostnameverifier PgjdbcHostnameVerifier. This sounds to me, that you configuration is using the "short" name to access PostgreSQL. Try from your server, if this is resolvable. Maybe you're missing a proper "search" DNS config option. If the internal connection to your PostgreSQL is TLS encrypted, then the short name also needs to be added to the TLS SAN (Subject Alternative Name) the PostgreSQL is running, of the default TLS verification options are used 1. As mentioned... Is a simple "ping lkv-srvapp39" resolvable from within your uyuni server? 2. Try to change the host setting that defines your PostgreSQL and change it to use the full FQDN. Robert

2 1

Promoting new Version in CLM Project Environment: How long should it normally take? ("Waiting for repositories data to be generated")
by Heiner W. 08 Aug '22

08 Aug '22

Hi List, we wanted to apply latest available SP2 updates and patches before migrating to SP3. 3.5 hours ago i triggered a final "promote" for the current SLES15 SP2 CLM Project Environment/stage (containing base, packagehub, Server-Applications, Public-Cloud15 and a few small custom repos). Now we are waiting impatiently (WebGUI still says "Waiting for repositories data to be generated") and affected systems aren't aware of new package Versions when calling zypper ref && zypper up. What are your experiences how long repo data regeneration "normally" takes? How can it be tuned? - Which config parameters should we change? - should we increase CPU or Memory? Uyuni VM currently runs on 4x2.2GHz and 32GB Memory We have 65 managed Systems running sles15 sp2 or sp3 in 3 CLM Projects we are running on default values: # java.taskomatic_channel_repodata_workers=2 # taskomatic.java.maxmemory=4096 # taskomatic.java.initmemory=256 # ps -efa|grep tasko root 14974 1 0 Jul28 ? 00:00:00 /bin/sh /usr/sbin/taskomatic root 14989 14974 1 Jul28 ? 04:38:51 /usr/bin/java -Djava.library.path=/usr/lib:/usr/lib64 -classpath /usr/share/rhn/classes:/usr/share/rhn/lib/spacewalk-asm.jar:/usr/share/rhn/lib/rhn.jar:/usr/share/rhn/lib/java-branding.jar:/usr/share/spacewalk/taskomatic/* -Dibm.dst.compatibility=true -Dfile.encoding=UTF-8 -Xms256m -Xmx4096m --add-modules java.annotation,com.sun.xml.bind --add-exports java.annotation/javax.annotation.security=ALL-UNNAMED --add-opens java.annotation/javax.annotation.security=ALL-UNNAMED com.redhat.rhn.taskomatic.core.TaskomaticDaemon Current Load: top - 12:37:44 up 25 days, 58 min, 2 users, load average: 0.00, 0.18, 0.46 Tasks: 369 total, 1 running, 368 sleeping, 0 stopped, 0 zombie %Cpu(s): 23.1 us, 1.5 sy, 0.0 ni, 75.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 32107.11+total, 1894.559 free, 9224.531 used, 20988.02+buff/cache MiB Swap: 0.000 total, 0.000 free, 0.000 used. 18222.20+avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 24611 postgres 20 0 4175884 156508 146952 S 53.33 0.476 0:36.23 postgres 13345 tomcat 20 0 5006136 1.317g 23912 S 40.00 4.202 60:20.16 java 14979 root 20 0 4267224 288120 20300 S 6.667 0.876 27:11.55 java Thanks, Heiner

1 0

AW: Subtask mgr-update-reporting failed.
by Crefeld, Tobias LKV Bayern e.V. 08 Aug '22

08 Aug '22

Hi Simon, thanks for your hints! I followed them and received a lot of messages but actually I'm no java developer. I tried to reduce the log output by leaving out the "at"-lines but it is still large. Hope that no one gets annoyed too much: 2022-08-02 09:56:00,022 [DefaultQuartzScheduler_Worker-18] WARN org.hibernate.orm.deprecation - HHH90000022: Hibernate's legacy org.hibernate.Criteria API is deprecated; use the JPA javax.persistence.criteria.CriteriaQuery instead 2022-08-02 09:56:02,718 [DefaultQuartzScheduler_Worker-1] WARN org.hibernate.orm.deprecation - HHH020100: The Ehcache second-level cache provider for Hibernate is deprecated. See https://hibernate.atlassian.net/browse/HHH-12441 for details. 2022-08-02 09:56:33,348 [C3P0PooledConnectionPoolManager[identityToken->z8kfluaqp0t6ro20pjuq|3ff5aba ]-HelperThread-#0] WARN com.mchange.v2.resourcepool.BasicResourcePool - com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@1c8f4b1f -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception: org.postgresql.util.PSQLException: The hostname lkv-srvapp39 could not be verified by hostnameverifier PgjdbcHostnameVerifier. 2022-08-02 09:56:33,348 [C3P0PooledConnectionPoolManager[identityToken->z8kfluaqp0t6ro20pjuq|3ff5aba ]-HelperThread-#0] WARN com.mchange.v2.resourcepool.BasicResourcePool - Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@411ce9ec is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests. 2022-08-02 09:56:33,348 [DefaultQuartzScheduler_Worker-1] WARN org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator - HHH000342: Could not obtain connection to query metadata : Connections could not be acquired from the underlying database! 2022-08-02 09:56:33,354 [C3P0PooledConnectionPoolManager[identityToken->z8kfluaqp0t6ro20pjuq|3ff5aba ]-HelperThread-#1] WARN com.mchange.v2.resourcepool.BasicResourcePool - com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@5ab931dd -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception: org.postgresql.util.PSQLException: The hostname lkv-srvapp39 could not be verified by hostnameverifier PgjdbcHostnameVerifier. 2022-08-02 09:56:33,354 [C3P0PooledConnectionPoolManager[identityToken->z8kfluaqp0t6ro20pjuq|3ff5aba ]-HelperThread-#1] WARN com.mchange.v2.resourcepool.BasicResourcePool - Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@411ce9ec is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests. 2022-08-02 09:56:33,360 [DefaultQuartzScheduler_Worker-1] WARN net.sf.ehcache.DiskStorePathManager - diskStorePath '/tmp' is already used by an existing CacheManager either in the same VM or in a different process. The diskStore path for this CacheManager will be set to /tmp/ehcache_auto_created2394383558487899130diskstore. To avoid this warning consider using the CacheManager factory methods to create a singleton CacheManager or specifying a separate ehcache configuration (ehcache.xml) for each CacheManager instance. 2022-08-02 09:56:33,361 [C3P0PooledConnectionPoolManager[identityToken->z8kfluaqp0t6ro20pjuq|3ff5aba ]-HelperThread-#2] WARN com.mchange.v2.resourcepool.BasicResourcePool - com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@68e07fff -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception: org.postgresql.util.PSQLException: The hostname lkv-srvapp39 could not be verified by hostnameverifier PgjdbcHostnameVerifier. 2022-08-02 09:56:33,362 [C3P0PooledConnectionPoolManager[identityToken->z8kfluaqp0t6ro20pjuq|3ff5aba ]-HelperThread-#2] WARN com.mchange.v2.resourcepool.BasicResourcePool - Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@411ce9ec is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests. 2022-08-02 09:56:33,374 [C3P0PooledConnectionPoolManager[identityToken->z8kfluaqp0t6ro20pjuq|3ff5aba ]-HelperThread-#1] WARN com.mchange.v2.resourcepool.BasicResourcePool - com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@3b518b25 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception: org.postgresql.util.PSQLException: The hostname lkv-srvapp39 could not be verified by hostnameverifier PgjdbcHostnameVerifier. 2022-08-02 09:56:33,374 [C3P0PooledConnectionPoolManager[identityToken->z8kfluaqp0t6ro20pjuq|3ff5aba ]-HelperThread-#0] WARN com.mchange.v2.resourcepool.BasicResourcePool - com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@5599538e -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception: org.postgresql.util.PSQLException: The hostname lkv-srvapp39 could not be verified by hostnameverifier PgjdbcHostnameVerifier. 2022-08-02 09:56:33,374 [C3P0PooledConnectionPoolManager[identityToken->z8kfluaqp0t6ro20pjuq|3ff5aba ]-HelperThread-#1] WARN com.mchange.v2.resourcepool.BasicResourcePool - Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@411ce9ec is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests. 2022-08-02 09:56:33,375 [DefaultQuartzScheduler_Worker-1] WARN org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 0, SQLState: null 2022-08-02 09:56:33,375 [DefaultQuartzScheduler_Worker-1] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - Connections could not be acquired from the underlying database! 2022-08-02 09:56:33,375 [C3P0PooledConnectionPoolManager[identityToken->z8kfluaqp0t6ro20pjuq|3ff5aba ]-HelperThread-#0] WARN com.mchange.v2.resourcepool.BasicResourcePool - Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@411ce9ec is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests. 2022-08-02 09:56:33,384 [DefaultQuartzScheduler_Worker-1] ERROR com.redhat.rhn.taskomatic.task.ReportDbUpdateTask - Executing a task threw an exception: org.quartz.JobExecutionException 2022-08-02 09:56:33,385 [DefaultQuartzScheduler_Worker-1] ERROR com.redhat.rhn.taskomatic.task.ReportDbUpdateTask - Message: Unable to update reporting db 2022-08-02 09:56:33,385 [DefaultQuartzScheduler_Worker-1] ERROR com.redhat.rhn.taskomatic.task.ReportDbUpdateTask - Cause: {} org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection Caused by: java.sql.SQLException: Connections could not be acquired from the underlying database! Caused by: com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary factory or source. Caused by: org.postgresql.util.PSQLException: The hostname lkv-srvapp39 could not be verified by hostnameverifier PgjdbcHostnameVerifier. 2022-08-02 09:56:33,387 [DefaultQuartzScheduler_Worker-1] ERROR com.redhat.rhn.taskomatic.task.ReportDbUpdateTask - Stack trace:org.quartz.JobExecutionException: Unable to update reporting db [See nested exception: org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection] Caused by: org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection Caused by: java.sql.SQLException: Connections could not be acquired from the underlying database! Caused by: com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary factory or source. Caused by: org.postgresql.util.PSQLException: The hostname lkv-srvapp39 could not be verified by hostnameverifier PgjdbcHostnameVerifier. 2022-08-02 09:57:00,022 [DefaultQuartzScheduler_Worker-2] WARN org.hibernate.orm.deprecation - HHH90000022: Hibernate's legacy org.hibernate.Criteria API is deprecated; use the JPA javax.persistence.criteria.CriteriaQuery instead Maybe someone has a better understanding of this stuff and can explain what's going wrong? BTW: The messages with "QuartzScheduler" are repeated every minute, independent of the status of "mgr-update-reporting-bunch". TIA! Regards. Tobias Crefeld.

4 3

Adding Oracle Linux
by Crefeld, Tobias LKV Bayern e.V. 01 Aug '22

01 Aug '22

Hi, I'd like to add Repositories for Oracle Linux 8 to the Uyuni-Server. Therefore I'm following the advice at https://www.uyuni-project.org/uyuni-docs/en/uyuni/client-configuration/clien ts-oracle.html#_add_software_channels and enter spacewalk-common-channels oraclelinux8 Afterwards system requests SUSE-Manager's credentials. There I enter the credentials that I use to logon to the Web-UI which can be found at the Web-UI under Users / User List / Active with the roles "SUSE Manager Administrator" and "Organization Administrator". Afterwards it reports Traceback (most recent call last): File "/usr/bin/spacewalk-common-channels", line 269, in <module> client, key = connect(options.user, options.password, options.server) File "/usr/bin/spacewalk-common-channels", line 119, in connect key = xmlrpc_login(client, options.user, password) File "/usr/lib/python3.6/site-packages/uyuni/common/cli.py", line 74, in xmlrpc_login sessionkey = client.auth.login(username, password) File "/usr/lib64/python3.6/xmlrpc/client.py", line 1112, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python3.6/xmlrpc/client.py", line 1452, in __request verbose=self.__verbose File "/usr/lib64/python3.6/xmlrpc/client.py", line 1154, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python3.6/xmlrpc/client.py", line 1187, in single_request dict(resp.getheaders()) xmlrpc.client.ProtocolError: <ProtocolError for localhost/rpc/api: 400 Bad Request> If I'm using tools like spacewalk-remove-channel, the same credentials work fine. Any idea? Regards, Tobias Crefeld.

1 0

Subtask mgr-update-reporting failed.
by Crefeld, Tobias LKV Bayern e.V. 28 Jul '22

28 Jul '22

Hi, recently I upgraded the Uyuni system from 2021.07 to 2022.06. Several tests were successful so I'm not sure if the current problems come from the update. There are two issues: 1. Since Uyuni's update several clients don't check in any more. All of them are using "Push via SSH tunnel" or "Push via SSH" as contact method. Salt clients with contact method "Default" (SLES15-SP3) run fine. Client OS is "openSUSE Leap 15.1 x86_64" or "SUSE Linux Enterprise Server 12 SP5 x86_64". There is no "configuration" or scripting - the only target is to monitor the patch level and provide repositories. 2. After a reboot of the Uyuni host I was sent an email with this content: "Taskomatic bunch mgr-update-reporting-bunch was scheduled to run within the update-reporting-default schedule. Subtask mgr-update-reporting failed. For more information check null." (Checking "null" wasn't successful) Any hints are welcome! Regards, Tobias Crefeld.

2 1

A question about venv-salt-minion and systemd
by Simon Avery 22 Jul '22

22 Jul '22

Hi A little flummoxed about this. I've switched to using venv-salt-minion on clients, and it installs okay. However, we require /tmp to have the noexec flag. Salt doesn't like this very much. Our previous workaround was to create a file in /etc/systemd/system/salt-minion.service.d containing [Service] Environment="TMPDIR=/usr/tmp" This told salt-minion to use a different tmpdir that did have the exec flag and it was happy again. However, venv-salt-minion doesn't read that file, because it's a different service. I assumed I could just create /etc/systemd/system/venv-salt-minion.service.d instead, but the process is not reading this. If I edit the system file directly and add that file it works, but I would prefer to use a drop-in file for this. I'm not overly familiar with venv programs, and less so when combined with systemd. Can anyone please point me the right way to do this? Thanks S

2 3