What is error code 137? Ans: Exit Code Number 128+n "Fatal error signal "n" could be generated by "kill -9 $PPID of script" returns comment "script $? returns 137 (128 + 9)" So that would more than likely be a red herring. You need to check the state of taskomatic as it tend to be the primary source of problems of this nature.
"2018-12-06 08:08:55,736 [DefaultQuartzScheduler_Worker-5] ERROR com.redhat.rhn.taskomatic.task.RepoSyncTask - Stack trace:org.quartz.JobExecutionException: Command '[/usr/bin/spacewalk-repo-sync, --channel, epel7-x86_64, --type, yum]' exited with error code 137" Dennis J. Pittman (e) [email protected] (m) 919-426-8907 (a) 310 Acorn Hollow Pl., Durham, NC 27703 From: [email protected] [mailto:[email protected]] On Behalf Of Dimitri Yioulos Sent: Wednesday, December 12, 2018 9:57 AM To: [email protected] Subject: Re: [Spacewalk-list] Subtask repo-sync failed Anybody on this? It's making me crazy. Thanks. Dimitri From: Dimitri Yioulos Sent: Thursday, December 06, 2018 9:17 AM To: [email protected]<mailto:[email protected]> Subject: Subtask repo-sync failed Hi, all. For a while now, scheduled repo syncs of with the epel 6 and 7 repositories have produced emails from our Spacewalk 2.8 saying the following: Taskomatic bunch repo-sync-bunch was scheduled to run within the repo-sync-1-130 schedule. Subtask repo-sync failed. For more information check /var/log/rhn/tasko/org1/repo-sync-bunch/repo-sync_10814174_err. I've looked at the error log identified above, the output of which is: 2018-12-06 08:08:55,660 [DefaultQuartzScheduler_Worker-5] ERROR com.redhat.rhn.taskomatic.task.RepoSyncTask - Executing a task threw an exception: org.quartz.JobExecutionException 2018-12-06 08:08:55,667 [DefaultQuartzScheduler_Worker-5] ERROR com.redhat.rhn.taskomatic.task.RepoSyncTask - Message: Command '[/usr/bin/spacewalk-repo-sync, --channel, epel7-x86_64, --type, yum]' exited with error code 137 2018-12-06 08:08:55,670 [DefaultQuartzScheduler_Worker-5] ERROR com.redhat.rhn.taskomatic.task.RepoSyncTask - Cause: null 2018-12-06 08:08:55,736 [DefaultQuartzScheduler_Worker-5] ERROR com.redhat.rhn.taskomatic.task.RepoSyncTask - Stack trace:org.quartz.JobExecutionException: Command '[/usr/bin/spacewalk-repo-sync, --channel, epel7-x86_64, --type, yum]' exited with error code 137 at com.redhat.rhn.taskomatic.task.RhnJavaJob.executeExtCmd(RhnJavaJob.java:103) at com.redhat.rhn.taskomatic.task.RepoSyncTask.execute(RepoSyncTask.java:70) at com.redhat.rhn.taskomatic.task.RhnJavaJob.execute(RhnJavaJob.java:88) at com.redhat.rhn.taskomatic.TaskoJob.execute(TaskoJob.java:186) at org.quartz.core.JobRunShell.run(JobRunShell.java:216) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549) What is error code 137? Previously, I tried removing the schedule with the spacewalk-api (e.g. client.taskomatic.org.unscheduleBunch(key, 'repo-sync-1-130'), and creating it anew. I've made sure that spacewalk-backend-2.8.60-1 is installed. I've searched for any other ideas, but found none. Help would be greatly appreciated. With thanks, Dimitri
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
