Open santeri3700 opened 2 years ago
Thanks for reporting @santeri3700 , if you have the chance it would be interesting to understand if it happens just for RPM (I guess so).
@mbussolotto I just tested the issue with RPM based channels and got same results. So it doesn't seem to be specific to RPM or DEB based channels. \ Also, I think it is not actually necessary to have the "repo-sync" task start automatically, I just tested this with the "Sync now" button.
Hi all,
I have been facing the same error message with the latest version of SUSE Manager (4.3.5). Manually repo sync not working on the Web UI, and the automatic mgr-sync-refresh schedule also run into errors.
The full error message in /var/log/rhn/rhn_taskomatic.log:
2023-06-09 14:20:53,031 [DefaultQuartzScheduler_Worker-1] DEBUG com.redhat.rhn.taskomatic.task.MgrSyncRefresh - Refreshing mgr-sync data
…
2023-06-09 14:21:43,943 [DefaultQuartzScheduler_Worker-1] DEBUG com.redhat.rhn.taskomatic.task.MgrSyncRefresh - Scheduling synchronization of all vendor channels
2023-06-09 14:21:43,986 [Thread-8] WARN com.redhat.rhn.taskomatic.TaskoQuartzHelper - Job single-repo-sync-bunch-1 failed to schedule.
2023-06-09 14:21:44,015 [DefaultQuartzScheduler_Worker-1] ERROR com.redhat.rhn.taskomatic.task.MgrSyncRefresh - Executing a task threw an exception: org.quartz.JobExecutionException
org.quartz.JobExecutionException: com.redhat.rhn.taskomatic.TaskomaticApiException: redstone.xmlrpc.XmlRpcException: The response could not be parsed.
at com.redhat.rhn.taskomatic.task.MgrSyncRefresh.execute(MgrSyncRefresh.java:127) ~[rhn.jar:?]
at com.redhat.rhn.taskomatic.task.RhnJavaJob.execute(RhnJavaJob.java:56) [rhn.jar:?]
at com.redhat.rhn.taskomatic.TaskoJob.execute(TaskoJob.java:155) [rhn.jar:?]
at org.quartz.core.JobRunShell.run(JobRunShell.java:202) [quartz-2.3.0.jar:?]
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) [quartz-2.3.0.jar:?]
Caused by: com.redhat.rhn.taskomatic.TaskomaticApiException: redstone.xmlrpc.XmlRpcException: The response could not be parsed.
at com.redhat.rhn.taskomatic.TaskomaticApi.invoke(TaskomaticApi.java:92) ~[rhn.jar:?]
at com.redhat.rhn.taskomatic.TaskomaticApi.scheduleSingleRepoSync(TaskomaticApi.java:172) ~[rhn.jar:?]
at com.redhat.rhn.taskomatic.task.MgrSyncRefresh.execute(MgrSyncRefresh.java:118) ~[rhn.jar:?]
... 4 more
Caused by: redstone.xmlrpc.XmlRpcException: The response could not be parsed.
at redstone.xmlrpc.XmlRpcClient.handleResponse(XmlRpcClient.java:435) ~[redstone-xmlrpc-client-1.1_20071120.jar:?]
at redstone.xmlrpc.XmlRpcClient.endCall(XmlRpcClient.java:376) ~[redstone-xmlrpc-client-1.1_20071120.jar:?]
at redstone.xmlrpc.XmlRpcClient.invoke(XmlRpcClient.java:209) ~[redstone-xmlrpc-client-1.1_20071120.jar:?]
at com.redhat.rhn.taskomatic.TaskomaticApi.invoke(TaskomaticApi.java:89) ~[rhn.jar:?]
at com.redhat.rhn.taskomatic.TaskomaticApi.scheduleSingleRepoSync(TaskomaticApi.java:172) ~[rhn.jar:?]
at com.redhat.rhn.taskomatic.task.MgrSyncRefresh.execute(MgrSyncRefresh.java:118) ~[rhn.jar:?]
... 4 more
Caused by: org.xml.sax.SAXParseException: Premature end of file.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) ~[xerces-j2.jar:?]
at redstone.xmlrpc.XmlRpcParser.parse(XmlRpcParser.java:158) ~[redstone-xmlrpc-client-1.1_20071120.jar:?]
at redstone.xmlrpc.XmlRpcClient.handleResponse(XmlRpcClient.java:420) ~[redstone-xmlrpc-client-1.1_20071120.jar:?]
at redstone.xmlrpc.XmlRpcClient.endCall(XmlRpcClient.java:376) ~[redstone-xmlrpc-client-1.1_20071120.jar:?]
at redstone.xmlrpc.XmlRpcClient.invoke(XmlRpcClient.java:209) ~[redstone-xmlrpc-client-1.1_20071120.jar:?]
at com.redhat.rhn.taskomatic.TaskomaticApi.invoke(TaskomaticApi.java:89) ~[rhn.jar:?]
at com.redhat.rhn.taskomatic.TaskomaticApi.scheduleSingleRepoSync(TaskomaticApi.java:172) ~[rhn.jar:?]
at com.redhat.rhn.taskomatic.task.MgrSyncRefresh.execute(MgrSyncRefresh.java:118) ~[rhn.jar:?]
... 4 more
The journalctl -u tomcat shows these error messages:
Jun 09 14:45:10 node01 server[12314]: [Fatal Error] :-1:-1: Premature end of file.
Jun 09 14:47:24 node01 server[12314]: [Fatal Error] :-1:-1: Premature end of file.
Taskomatic logs shows these errors at the same time:
2023-06-09 14:45:10,183 [Thread-10] WARN com.redhat.rhn.taskomatic.TaskoQuartzHelper - Job single-repo-sync-bunch-1 failed to schedule.
2023-06-09 14:47:24,907 [Thread-11] WARN com.redhat.rhn.taskomatic.TaskoQuartzHelper - Job single-repo-sync-bunch-1 failed to schedule.
The custom and vendor channels sync are working via spacewalk-repo-sync but not manually from Web UI. Vendor channels sync are not working automatically.
Do you have any suggestion of this issue?
@wweellddeerr can this one also be related to https://github.com/SUSE/spacewalk/issues/22195 ?
Problem description
Channel repo sync schedule can't be changed while Taskomatic is (automatically) running a "repo-sync" task for the specific channel at the moment. \ Attempting to change the sync schedule will result in error and the previously configured schedule to be deleted/lost.
I would not expect the schedule change to fail and especially result in the previously set schedule to be deleted/lost.
Version of Uyuni Server and Proxy (if used)
Reproduced on two separate Uyuni Servers on versions 2022.05 and 2022.06 (updated from 2022.05). I do not know if this affects older versions.
Details about the issue
I discovered this issue about a week before opening this issue. I was trying to mass-update channel sync schedules via spacecmd and some channels repeatedly resulted in error. It later came apparent that the channels in question were being automatically synchronized at the moment by Taskomatic due to the daily schedule setting. \ These channels are both added via
spacewalk-common-channels
or manually via Web UI or spacecmd and function fine otherwise.2022-06-29: I have so far only observed this issue on DEB repositories (Debian & Ubuntu), but this could be because the RPM repositories in my environment(s) are automatically synchronized earlier in the morning when I haven't done any tests.This affects RPM and DEB based channels.How to reproduce
spacewalk-common-channels
etc. \ These channels contain packages and patches/errata from previous automatic synchronizations.spacecmd 'softwarechannel_setsyncschedule CHANNEL-LABEL 0 0 11 ? * *'
taskotop -e
(taskotop is provided by thespacewalk-utils-extras
package)0 0 11 ? * *
) is deleted at this point and appears unset/disabled when inspecting via Web UI or spacecmd.Logs and error messages
/var/log/rhn/rhn_taskomatic_daemon.log:
/var/log/messages:
The task ended successfully later and there were no new packages or patches/errata to be imported.