Chris -- Sounds like the communication between spacewalk and the client is working, but perhaps the client isn't "allowed" to execute a command?
What does the output of "rhn-actions-control --report" on an affected client show? Especially, does it show that "run is enabled" ? Andy Andy Ingham IT Infrastructure Fuqua School of Business Duke University From: Chris Balcum <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Thursday, June 26, 2014 at 3:03 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [Spacewalk-list] Scheduled jobs picked up but not executing Hi all, Having a funky issue with Spacewalk and scheduling remote commands. On some systems (around 40 or so out of over 500) I schedule a command and they get picked up, but they don't actually execute. The UI shows them as being picked up, but they just... sit there. I've verified that rhnsd and osad is running on the client side, and jabberd and osa-dispatcher is running on the server end. This action will be executed after 6/26/14 2:27:00 PM EDT This action's status is: Picked Up. The client picked up this action on 6/26/14 2:28 PM The client has not yet completed this action. Any help would be greatly appreciated. Chris __________________________________ Chris Balcum | Infrastructure Operations Engineer millennial media Mobile: 315.530.2911 Email: [email protected]<mailto:[email protected]> Web: www.millennialmedia.com<http://www.millennialmedia.com/>
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
