Hi, meanwhile I updated Uyuni from 2022.06 to 2022.08 and since then patching of (salt) clients works again after some manual resynchronisations. Now most of the Taskomatic jobs get executed successfully again. The Taskomatic job mgr-update-reporting-bunch still fails with similar log messages as before. Another job “minion-action-executor-bunch” that failed can’t be found on the Task Schedules list. Systems with the Contact Method “Push via SSH” still cannot check in. Trying to remove a ssh-client was successful. Trying to re-register the client by the bootstrap dialogue fails with the message “Error: Unable to download https://lkv-srvapp39.lkvbay.net:443/pub/repositories/opensuse/15/1/bootstrap... file!” Actually this file doesn’t exist but we never changed the respective repositories manually so we don’t know why the same task worked before. I found a job “ssh-push” with the status “SKIPPED”. The log message is “com.redhat.rhn.taskomatic.task.SSHPush - Maximum number of workers already put ... skipping.” BTW: Returning to latest Uyuni-version before the upgrade to 2022.06 wasn’t successful, too. Seems to be related to different salt versions. Regards, Tobias Crefeld. Von: David Mace [mailto:david@macemail.co.uk] Gesendet: Dienstag, 16. August 2022 11:42 "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" Since the update taskomatic also just crashes every 10 seconds for me <https://github.com/uyuni-project/uyuni/issues/5556> https://github.com/uyuni-project/uyuni/issues/5556 -----Original Message----- From: "Crefeld, Tobias LKV Bayern e.V." < <mailto:%22Crefeld,%20Tobias%20LKV%20Bayern%20e.V.%22%20%3cTobias.Crefeld@lkv.bayern.de%3e> Tobias.Crefeld@lkv.bayern.de> Reply-To: General discussion related to the openSUSE Uyuni project < <mailto:General%20discussion%20related%20to%20the%20openSUSE%20Uyuni%20project%20%3cusers@lists.uyuni-project.org%3e> users@lists.uyuni-project.org> To: 'Paul-Andre Panon via Uyuni Users' < <mailto:'Paul-Andre%20Panon%20via%20Uyuni%20Users'%20%3cusers@lists.uyuni-project.org%3e> users@lists.uyuni-project.org> Subject: AW: RE: Subtask mgr-update-reporting failed. Date: Tue, 16 Aug 2022 09:11:27 +0000 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 <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