[Spacewalk-list] Problems syncing EPEL repositories

[Ree, Jan-Albert van]

Good morning,

Over the last few days I've experienced issues syncing from the EPEL repositories :

- Spacewalk 2.8 server, running Scientific Linux 7.5
- The problem only occurs on the EPEL repositories, I can sync all other repositories fine
- It hapens both for EPEL for RHEL6 and EPEL for RHEL7
- I've changed mirror URL's to exclude problems with a single mirror

I get the following error on the EPEL syncs :

2018-05-08 08:45:33,363 [Thread-52] ERROR com.redhat.rhn.taskomatic.task.RepoSyncTask  - 08:45:32 ERROR: Invalid severity: None

2018-05-08 08:45:33,364 [DefaultQuartzScheduler_Worker-1] ERROR com.redhat.rhn.taskomatic.task.RepoSyncTask  - Executing a task threw an exception: org.quartz.JobExecutionException
2018-05-08 08:45:33,364 [DefaultQuartzScheduler_Worker-1] ERROR com.redhat.rhn.taskomatic.task.RepoSyncTask  - Message: Command '[/usr/bin/spacewalk-repo-sync, --channel, epelv7, --type, yum]' exited with error code 1
2018-05-08 08:45:33,364 [DefaultQuartzScheduler_Worker-1] ERROR com.redhat.rhn.taskomatic.task.RepoSyncTask  - Cause: null
2018-05-08 08:45:33,365 [DefaultQuartzScheduler_Worker-1] ERROR com.redhat.rhn.taskomatic.task.RepoSyncTask  - Stack trace:org.quartz.JobExecutionException: Command '[/usr/bin/spacewalk-repo-sync, --channel, epelv7, --type, yum]' exited with error code 1
        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)

The sync log shows

2018/05/08 08:44:31 +02:00 Command: ['/usr/bin/spacewalk-repo-sync', '--channel', 'epelv7', '--type', 'yum']
2018/05/08 08:44:31 +02:00 Sync of channel started.
2018/05/08 08:44:31 +02:00
2018/05/08 08:44:31 +02:00   Processing repository with URL: http://mirror.infonline.de/epel/7/x86_64/
2018/05/08 08:44:34 +02:00
2018/05/08 08:44:34 +02:00   Importing comps file comps.xml.
2018/05/08 08:44:58 +02:00     Packages in repo:             12530
2018/05/08 08:44:58 +02:00     Packages passed filter rules: 12309
2018/05/08 08:45:28 +02:00     No new packages to sync.
2018/05/08 08:45:29 +02:00
2018/05/08 08:45:29 +02:00   Errata in repo: 4247.
2018/05/08 08:45:32 +02:00     Syncing 55 new errata to channel.
2018/05/08 08:45:32 +02:00 ERROR: Invalid severity: None
2018/05/08 08:45:32 +02:00 ERROR: Invalid severity: None
2018/05/08 08:45:33 +02:00 Sync of channel completed in 0:01:01.

Am I correct in assuming this is due to a bad package in EPEL ?
Regards,
--
Jan-Albert van Ree



Jan-Albert van Ree  | Linux System Administrator | MARIN Support Group
MARIN | T +31 317 49 35 48 | mailto:J.A.v.Ree at marin.nl | http://www.marin.nl

MARIN news: http://www.marin.nl/web/News/News-items/CRS-meets-in-Wageningen-November-27December-1.htm