Bug 771650 - osad on the clients will not pick up scheduled actions
Summary: osad on the clients will not pick up scheduled actions
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 1.6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space17
TreeView+ depends on / blocked
 
Reported: 2012-01-04 13:32 UTC by daniel.schindler
Modified: 2012-01-06 10:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-06 10:05:24 UTC


Attachments (Terms of Use)
Example osad output (6.03 KB, text/plain)
2012-01-04 13:32 UTC, daniel.schindler
no flags Details

Description daniel.schindler 2012-01-04 13:32:51 UTC
Created attachment 550683 [details]
Example osad output

Description of problem:
OSAD on the clients will not pick up scheduled actions. Pings, however, still work.
Behavior occured after upgrade 1.5 -> 1.6. I'd blame the server side (osa-dispatcher, jabberd). Tried different OSAD versions (osad-5.10.34-1.el5; osad-5.10.18.2-1.el5) but same effect

Version-Release number of selected component (if applicable):
1.6

How reproducible:
Schedule any desired action (install package, run remote command) to run as soon as possible or any desired time, it won't be picked up.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Scheduled actions are not picked up via osad/osa-dispatcher.

Expected results:
Scheduled actions run successfully.

Additional info:
osad output looks fine. Could you provide info on how to monitor server side processes (osa-dispatcher, jabberd)?

Comment 1 daniel.schindler 2012-01-06 10:05:24 UTC
Seems like it was my fault... Works again. I'll let you know if I can find out what the root cause was.

Thanks.

Comment 2 daniel.schindler 2012-01-06 10:08:10 UTC
OK. Seems like this helped:
# spacewalk-service stop
# rm -f /var/lib/jabberd/db/*
# spacewalk-service start


Note You need to log in before you can comment on or make changes to this bug.