I had similar issue and had to restore 2022.6 from backup, but think there might be a solution in github issue below https://github.com/uyuni-project/uyuni/issues/5556 -----Original Message----- From: Thomas Weis <tweis@ntw-datentechnik.de> Reply-To: General discussion related to the openSUSE Uyuni project <users@lists.uyuni-project.org> To: users@lists.uyuni-project.org Subject: Antw: since update 2022.08 (probably earlier) error "The scheduling service appears down" Date: Thu, 08 Sep 2022 11:33:25 +0200 Hello everyone, no one have an Idea? Regards Thomas Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Thomas Weis 05.09.2022 09:40 >>> Hello, everyone
recently we upgraded from 2022.06 to Uyuni 2022.08 without any problems. It was noticed that there has been a task in Schdule, Pending Actions since 08/27/2022, which is not being processed. The task should be aborted using chancel Actions, but this was not possible. After marking the task and executing chancel actions, the error message "Could not cancel action. Please make sure that the task scheduler is running" appeared. No tasks/schedules are listed under "Uyuni Schedules" either. systemctl status taskomatic.service indicates that Taskomatic is active. There are regular messages in /var/log/messages: " WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance. taskomatic.service: Main process exited, code=exited, status=255/EXCEPTION taskomatic.service: Failed with result 'exit-code'. taskomatic.service: Scheduled restart job, restart counter is at 1 /var/log/rhn/rhn_taskomatic_daemon.log shows: "2022-09-05 09:34:47,805 [Thread-41] WARN org.hibernate.orm.deprecation - HHH90000014: Found use of deprecated [org.hibernate.id.SequenceHiLoGenerator] sequence-based id generator; use org.hibernate .id.enhanced.SequenceStyleGenerator instead.See Hibernate Domain Model Mapping Guide for details. 2022-09-05 09:34:47,807 [Thread-41] WARN org.hibernate.orm.deprecation - HHH90000014: Found use of deprecated [org.hibernate.id.SequenceGenerator] sequence-based id generator; use org.hibernate.id.enhanced.SequenceStyleGenerator instead. See Hibernate Domain Model Mapping Guide for details. 2022-09-05 09:34:47,807 [Thread-41] WARN org.hibernate.orm.deprecation - HHH90000014: Found use of deprecated [org.hibernate.id.SequenceGenerator] sequence-based id generator; use org.hibernate.id.enhanced.SequenceStyleGenerator instead. See Hibernate Domain Model Mapping Guide for details. 2022-09-05 09:34:47,807 [Thread-41] WARN org.hibernate.orm.deprecation - HHH90000014: Found use of deprecated [org.hibernate.id.SequenceGenerator] sequence-based id generator; use org.hibernate.id.enhanced.SequenceStyleGenerator instead. See Hibernate Domain Model Mapping Guide for details. 2022-09-05 09:34:47,807 [Thread-41] WARN org.hibernate.orm.deprecation - HHH90000014: Found use of deprecated [org.hibernate.id.SequenceGenerator] sequence-based id generator; use org.hibernate.id.enhanced.SequenceStyleGenerator instead. See Hibernate Domain Model Mapping Guide for details. 2022-09-05 09:34:47,808 [Thread-41] WARN org.hibernate.orm.deprecation - HHH90000014: Found use of deprecated [org.hibernate.id.SequenceGenerator] sequence-based id generator; use org.hibernate.id.enhanced.SequenceStyleGenerator instead. See Hibernate Domain Model Mapping Guide for details. 2022-09-05 09:34:54,777 [Thread-41] WARN org.hibernate.orm.deprecation - HHH90000017: Found use of deprecated entity-type selector syntax in HQL/JPQL query ['s.class']; use TYPE operator instead : type(s) 2022-09-05 09:34:55,003 [Thread-41] WARN org.hibernate.orm.deprecation - HHH90000017: Found use of deprecated entity-type selector syntax in HQL/JPQL query ['s.class']; use TYPE operator instead : type(s) 2022-09-05 09:34:55,214 [Thread-41] WARN org.hibernate.orm.deprecati on - HHH90000017: Found use of deprecated entity-type selectoHQL/JPQL query ['sa.server.class']; use TYPE operator instead : type(sa.server) 2022-09-05 09:34:55,249 [Thread-41] WARN org.hibernate.orm.deprecation - HHH90000017: Found use of deprecated entity-type selector syntax in HQL/JPQL query ['sa.server.class']; use TYPE operator instead : type(sa.server) 2022-09-05 09:34:55,263 [Thread-41] WARN org.hibernate.orm.deprecation - HHH90000017: Found use of deprecated entity-type selector syntax in HQL/JPQL query ['s.class']; use TYPE operator instead : type(s) 2022-09-05 09:34:56,378 [Thread-41] FATAL com.redhat.rhn.taskomatic.core.TaskomaticDaemon - Failure occurred during job recovery." Synchronize repositories does not work, patches and updates are not displayed / processed. Up until 08/26/2022 and Uyuni 2022.06 everything was fine and working correctly. Where can I start troubleshooting, does anyone have an idea? Thank you very much Best Regards Thomas mit freundlichen Gruessen Thomas Weis NTW Netzwerk • Telekommunikation • Datentechnik Burghaldenstrasse 24 D-71336 Waiblingen Fon: +49 7151 9440447 Fax: +49 7151 9440446 E-Mail: tweis@ntw-datentechnik.de Web: www.ntw-datentechnik.de Portal: https://support.ntw-datentechnik.de UST-ID: DE175034656