[Spacewalk-list] Spacewalk 2.4 reposync not running after upgrade

[Kalchik, Jeffery]

I'm in the process of finishing a 2.4 upgrade/migration.

When I configured all of my release channels with the same reposync schedule, I did receive a series of taskomatic reposync error messages nightly with subtask repo-sync failed.  I broke the reposyncs up by family, i.e. all CentOS6 at 6:00 PM, CentOS7 at 7:00 PM, etc.  All of the reposyncs are now completing, without the error & warning messages.  There's roughly 10 per group that are configured to sync at exactly the same time, they appear to run serially, & all complete.  In total, 52 channels in 5 groups run reposync nightly.   Each group takes somewhere between 10 & 30 minutes to complete.  Server is a virtual machine with 2 vCPUs and 12 gb of RAM (mostly unused.)

Jeff Kalchik
Systems Engineering
Land O'Lakes

From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Howard Coles
Sent: Friday, January 15, 2016 9:06 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Spacewalk 2.4 reposync not running after upgrade

I'm looking hard at setting up cron to handle it via scripts.
I can set it up to log results, and manage those logs via syslog and/or logrotate, and potentially get notified on failure.
I've had to manually sync the repos twice now.

Has anyone else solved this, or is it that you setup the schedules to run far enough apart to avoid the problem?


See Ya'
Howard Coles Jr.

From: spacewalk-list-bounces at redhat.com<mailto:spacewalk-list-bounces at redhat.com> [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Coffman, Anthony J
Sent: Friday, January 15, 2016 8:54 AM
To: spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>
Subject: Re: [Spacewalk-list] Spacewalk 2.4 reposync not running after upgrade

Has anybody else run into this issue on Spacewalk 2.4?  Is there any way to revert to the previous reposync behavior?

The previous behavior (when overlapping repo synchs were run, they would queue up and execute serially) was quite nice and I'd like to get back to that if possible.

Regards,
--Tony


From: Coffman, Anthony J
Sent: Wednesday, December 16, 2015 10:34 AM
To: 'spacewalk-list at redhat.com' <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Subject: RE: Spacewalk 2.4 reposync not running after upgrade

Has anybody else run into this issue on Spacewalk 2.4?  Is there any way to revert to the previous reposync behavior?

The previous behavior (when overlapping repo synchs were run, they would queue up and execute serially) was quite nice and I'd like to get back to that if possible.

--Tony



From: Coffman, Anthony J
Sent: Thursday, October 15, 2015 2:35 PM
To: 'spacewalk-list at redhat.com' <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Subject: RE: Spacewalk 2.4 reposync not running after upgrade

Follow up on this.  I've spent more time looking at it and the change in behavior seems to be that when multiple repo synchonizations are scheduled overlapping, it'll will run one of them but the rest don't run (no mention in the log except for the API request).

So the first one runs but the rest don't.  If I very carefully and painfully run then one at a time, waiting for one to complete before starting another, they run normally.

Has anybody else seen this behavior on 2.4?

Regards,
--Tony


From: Coffman, Anthony J
Sent: Wednesday, October 14, 2015 8:31 AM
To: spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>
Subject: Spacewalk 2.4 reposync not running after upgrade

I upgraded 2.3 -> 2.4 over the weekend and noticed that my reposyncs stopped running according to their schedules.

I changed a few schedules by one minute and hit the schedule button and that seems to have fixed those.  On others, I merely hit the schedule button again with the same schedule but they didn't run.

So I guess I need to reschedule the whole lot?

Has anybody else run into this?

Regards,
--Tony

This message may contain confidential material from Land O'Lakes, Inc. (or its subsidiary) for the sole use of the intended recipient(s) and may not be reviewed, disclosed, copied, distributed or used by anyone other than the intended recipient(s). If you are not the intended recipient, please contact the sender by reply email and delete all copies of this message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20160115/9d2d118b/attachment.htm>