<div dir="ltr"><div>OK, so I've doing some more testing on this - since I couldn't remember preciseley the time I submitted the previous jobs so I've recorded times more accurately now.<br><br></div>Yesterday morning between 1045-1100 GMT I submitted a number of jobs to run at 9AM over the next 4 days too see when they were picked up and executed. The first job was scheduled to execute today after 9AM, according to the schedule its showing:<br><br><div class="">
<ul class=""><li class="">
<div class="">
<div class="">
<strong>Summary:</strong>
</div>
<div class="">
Package Install scheduled by mattb
</div>
</div>
</li><li class="">
<div class="">
<div class="">
<strong>Details:</strong>
</div>
<div class="">
This action will be executed after 12/23/14 9:00:00 AM GMT<br>This action's status is: Queued.<br>This action has not yet been picked up.<br>Packages Scheduled:<br><ul><li>kernel-2.6.32-504.3.3.el6.x86_64</li><li>rsyslog-5.8.10-10.el6_6.x86_64</li><li>kernel-firmware-2.6.32-504.3.3.el6.noarch</li></ul>
</div>
</div>
</li><li class="">
<div class="">
<div class="">
<strong>Time:</strong>
</div>
<div class="">
12/23/14 9:00:00 AM GMT
</div>
</div>
</li></ul>
I'm surprised that the action "has not yet been picked up" since the server checked in (via the spacewalk proxy) just 35 minutes before the "execute after" time.<br><br></div><div class="">I've checked and times on the three involved nodes (spacewalk, proxy & client) are all in sync.<br><br></div><div class="">Regards,<br></div><div class=""><br></div><div class=""><br></div><br><div><div><div class="gmail_extra"><br><div class="gmail_quote">On 19 December 2014 at 12:10, Matt Bayliss <span dir="ltr"><<a href="mailto:aarrgghh765@gmail.com" target="_blank">aarrgghh765@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>I scheduled a jobs on the morning of the 17th December to execute the following morning at 9AM, it seems that although the rhnsd interval is set to 240 [1] the job was not picked up and executed until approx 28 hours after I created the schedule.<br><br></div><div>[1] # cat /etc/sysconfig/rhn/rhnsd<br>INTERVAL=240<br><br></div><div><br></div> Summary:<br> Package Install scheduled by swadmin<br> Details:<br> This action will be executed after 12/18/14 9:00:00 AM GMT<br> This action's status is: Completed.<br> The client picked up this action on 12/18/14 3:03 PM<br> The client completed this action on 12/18/14 3:05 PM<br> Client execution returned "Update Succeeded" (code 0)<br> Packages Scheduled:<br> nss-util-3.16.2.3-2.el6_6.x86_64<br> rpm-python-4.8.0-38.el6_6.x86_64<br> rpm-4.8.0-38.el6_6.x86_64<br> system-config-firewall-base-1.2.27-7.2.el6_6.noarch<br> selinux-policy-3.7.19-260.el6_6.1.noarch<br> nss-3.16.2.3-3.el6_6.x86_64<br> nss-sysinit-3.16.2.3-3.el6_6.x86_64<br> rpm-build-4.8.0-38.el6_6.x86_64<br> nss-tools-3.16.2.3-3.el6_6.x86_64<br> ruby-1.8.7.374-3.el6_6.x86_64<br> ruby-libs-1.8.7.374-3.el6_6.x86_64<br> rpm-libs-4.8.0-38.el6_6.x86_64<br> selinux-policy-targeted-3.7.19-260.el6_6.1.noarch<br> Time:<br> 12/18/14 9:00:00 AM GMT<br><br>Also, this job was pard of an action chain to reboot the system when the package update was complete (not necessary but I wanted to test it) this was not completed until 4-5 hours after the package update which would have only taken a few minutes. I'm surprised that this didn't happen immediately afterward.<br><br>Summary:<br>System reboot scheduled by mattb<br>Details:<br>This action will be executed after 12/18/14 9:00:00 AM GMT<br>This action's status is: Completed.<br>The client picked up this action on 12/18/14 3:05 PM<br>The client completed this action on 12/18/14 7:48 PM<br>Client execution returned "null" (code null)<br>Time:<br>12/18/14 9:00:00 AM GMT<br><br>Am I misunderstanding how the scheduler works? I won't be able to rely on this in production if I can't predict with some accuracy when the jobs will execute.<br><br>Regards,<br></div>
</blockquote></div><br></div></div></div></div>