<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="#0563C1" vlink="#954F72"> <div class="WordSection1"> Good afternoon, all.<o:p></o:p> <o:p> </o:p> And, as is frequently the case, I’ll struggle with something for several days, finally ask for assistance….. and solve it myself within a couple of hours.<o:p></o:p> <o:p> </o:p> The secret appears to be in execution of taskomatic. reinitializeAllSchedulesFromNow. I don’t know what’s caused the log jam, but simply executing this:<o:p></o:p> <o:p> </o:p> my $RC = $CLIENT->call('taskomatic.reinitializeAllSchedulesFromNow', $SESSION);<o:p></o:p> printf("%s\n", Dumper($RC));<o:p></o:p> <o:p> </o:p> now shows a lot of expected Taskomatic activity. Time will tell, but the channel-repo-data bunch immediately fired off, which is the one I’ve been most concerned with.<o:p></o:p> <o:p> </o:p> Now…….for a bit of a nit to pick. For years, I’ve been using Perl scripts for some task automation, and used the API docs to write these scripts. I’ve been redirected to:<o:p></o:p> <o:p> </o:p> <a href="https://spacewalkproject.github.io/documentation/api/2.7/index.html">https://spacewalkproject.github.io/documentation/api/2.7/index.html</a><o:p></o:p> <o:p> </o:p> for the 2.7 API documentation. However, the taskomatic and taskomatic.org namespace APIs are conspicuous by their absence. I’ve found those here:<o:p></o:p> <o:p> </o:p> <a href="https://github.com/spacewalkproject/spacewalk/wiki/Features_TaskomaticAPI">https://github.com/spacewalkproject/spacewalk/wiki/Features_TaskomaticAPI</a><o:p></o:p> <o:p> </o:p> Should the taskomatic and taskomatic.org namespaces be included in the main API docs?<o:p></o:p> <o:p> </o:p> Jeff Kalchik<o:p></o:p> Systems Engineering<o:p></o:p> Land O’Lakes<o:p></o:p> 651-375-2421<o:p></o:p> <o:p> </o:p> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: spacewalk-list-bounces@redhat.com [mailto:spacewalk-list-bounces@redhat.com] On Behalf Of Kalchik, Jeffery Sent: Friday, December 15, 2017 7:15 AM To: spacewalk-list@redhat.com Subject: [Spacewalk-list] Spacewalk 2.7 - post upgrade. Taskomatic bunches/queues not processing?<o:p></o:p> </div> </div> <o:p> </o:p> <table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" align="left" width="100%" style="width:100.0%"> <tbody> <tr> <td style="background:#910A19;padding:5.25pt 1.5pt 5.25pt 1.5pt"></td> <td width="100%" style="width:100.0%;background:#FDF2F4;padding:5.25pt 3.75pt 5.25pt 11.25pt;word-wrap:break-word"> <div> This sender failed our fraud detection checks and may not be who they appear to be. Learn about <a href="http://aka.ms/LearnAboutSpoofing">spoofing</a><o:p></o:p> </div> </td> <td width="75" style="width:56.25pt;background:#FDF2F4;padding:5.25pt 3.75pt 5.25pt 3.75pt;word-wrap:break-word;align:left"> <a href="http://aka.ms/SafetyTipsFeedback">Feedback</a><o:p></o:p> </td> </tr> </tbody> </table> <div> Good morning, all.<o:p></o:p> <o:p> </o:p> Sunday, I finally upgraded from 2.6 to 2. (CentOS6 host, 2vCPUs and 12gb of RAM.) Since then, I have discovered a little Taskomatic tweaking is in order, max heap size has been increased to 2gb. The upgrade itself was largely uneventful, had to remove xmlbeans, manually swap jpackage-tools out for javapackage-tools, and create the symlink for the geronimo-jta.jar -> jta.jar issue (referenced for RHEL6, but not CentOS6.)<o:p></o:p> <o:p> </o:p> Unfortunately, I’ve discovered since, that I’ve got problems with Taskomatic bunches not processing on time:<o:p></o:p> <o:p> </o:p> Last Execution Times<o:p></o:p> Last Execution Times<o:p></o:p> Auto Errata Updates: 2017-12-10 10:55:00 CST FINISHED<o:p></o:p> Channel Repodata: 2017-12-13 14:21:01 CST INTERRUPTED<o:p></o:p> Changelog Cleanup: 2017-12-14 23:00:00 CST FINISHED<o:p></o:p> Clean Log History: 2017-12-14 23:00:00 CST FINISHED<o:p></o:p> Cobbler Sync: 2017-12-10 11:21:32 CST FINISHED<o:p></o:p> Compare Config Files: 2017-12-14 23:00:00 CST FINISHED<o:p></o:p> Daily Summary Mail: 2017-12-14 23:00:00 CST FINISHED<o:p></o:p> Errata Cache: 2017-12-10 11:00:00 CST FINISHED<o:p></o:p> Errata Notification Mail: 2017-12-10 11:00:00 CST FINISHED<o:p></o:p> Errata Notification Queue: 2017-12-10 11:00:00 CST FINISHED<o:p></o:p> Kickstart Cleanup: 2017-12-10 11:00:00 CST FINISHED<o:p></o:p> Kickstart Sync: 2017-12-10 11:21:33 CST FINISHED<o:p></o:p> Package Cleanup: 2017-12-12 15:06:44 CST FINISHED<o:p></o:p> Failed reboots cleanup: 2017-12-15 07:00:00 CST FINISHED<o:p></o:p> Sandbox Cleanup: 2017-12-15 04:05:00 CST FINISHED<o:p></o:p> Session Cleanup: 2017-12-13 15:13:18 CST FINISHED<o:p></o:p> Daily Summary Queue: 2017-12-14 23:00:00 CST FINISHED<o:p></o:p> UUID cleanup: 2017-12-15 07:00:00 CST FINISHED<o:p></o:p> The task schedules have been left bone-stock:<o:p></o:p> <o:p> </o:p> Schedule name Frequency Active From Bunch<o:p></o:p> auto-errata-default 0 5/10 * * * ? 2017-12-10 11:21:32 CST auto-errata-bunch<o:p></o:p> channel-repodata-default 0 * * * * ? 2017-12-10 11:21:32 CST channel-repodata-bunch<o:p></o:p> cleanup-data-default 0 0 23 ? * * 2012-09-26 16:27:16 CDT cleanup-data-bunch<o:p></o:p> clear-taskologs-default 0 0 23 ? * * 2012-09-26 16:27:16 CDT clear-taskologs-bunch<o:p></o:p> cobbler-sync-default 0 * * * * ? 2017-12-06 12:56:47 CST cobbler-sync-bunch<o:p></o:p> compare-configs-default 0 0 23 ? * * 2012-09-26 16:27:16 CDT compare-configs-bunch<o:p></o:p> daily-status-default 0 0 23 ? * * 2012-09-26 16:27:16 CDT daily-status-bunch<o:p></o:p> errata-cache-default 0 * * * * ? 2017-12-10 11:21:32 CST errata-cache-bunch<o:p></o:p> errata-queue-default 0 * * * * ? 2017-12-10 11:21:32 CST errata-queue-bunch<o:p></o:p> kickstart-cleanup-default 0 0/10 * * * ? 2017-12-10 11:21:32 CST kickstart-cleanup-bunch<o:p></o:p> kickstartfile-sync-default 0 0/10 * * * ? 2017-12-06 12:56:47 CST kickstartfile-sync-bunch<o:p></o:p> package-cleanup-default 0 0/10 * * * ? 2017-12-10 11:21:32 CST package-cleanup-bunch<o:p></o:p> reboot-action-cleanup-default 0 0 * * * ? 2017-12-10 12:09:55 CST reboot-action-cleanup-bunch<o:p></o:p> sandbox-cleanup-default 0 5 4 ? * * 2012-09-26 16:27:16 CDT sandbox-cleanup-bunch<o:p></o:p> session-cleanup-default 0 0/15 * * * ? 2017-12-10 11:21:32 CST session-cleanup-bunch<o:p></o:p> uuid-cleanup-default 0 0 * * * ? 2017-12-10 12:09:55 CST uuid-cleanup-bunch<o:p></o:p> <o:p> </o:p> All of the services appear to be up:<o:p></o:p> <o:p> </o:p> $ sudo spacewalk-service status<o:p></o:p> postmaster (pid 51627) is running...<o:p></o:p> router (pid 51664) is running...<o:p></o:p> sm (pid 51672) is running...<o:p></o:p> c2s (pid 51680) is running...<o:p></o:p> s2s (pid 51688) is running...<o:p></o:p> tomcat6 (pid 51766) is running... [ OK ]<o:p></o:p> httpd (pid 51888) is running...<o:p></o:p> osa-dispatcher (pid 51916) is running...<o:p></o:p> rhn-search is running (51938).<o:p></o:p> cobblerd (pid 51981) is running...<o:p></o:p> RHN Taskomatic is running (52007).<o:p></o:p> <o:p> </o:p> All of the bunches dated 2017-12-10 have not executed since I upgraded on Sunday. They will execute if I run them manually through the single run scheduler, but not otherwise. Obviously, this is having some rather wide ranging side effects. I’ve never had to get into Taskomatic much over the years, I really don’t grok how it works under the covers.<o:p></o:p> <o:p> </o:p> I’d really much rather not have to go back to a 2.6 image. Any idea what I have manage to foul up during the upgrade process? <o:p></o:p> <o:p> </o:p> Jeff Kalchik<o:p></o:p> Systems Engineering<o:p></o:p> Land O’Lakes<o:p></o:p> 651-375-2421<o:p></o:p> 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. <o:p></o:p> </div> </div> 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. </body> </html>