Bug 189969 - osad on Satellite client stops when jabberd is restarted on Satellite server
Summary: osad on Satellite client stops when jabberd is restarted on Satellite server
Keywords:
Status: CLOSED DUPLICATE of bug 167000
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Other
Version: unspecified
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: John Wregglesworth
QA Contact: Vlady Zlatkin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-26 10:56 UTC by Carsten Clasohm
Modified: 2007-10-24 02:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-06-21 16:04:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Carsten Clasohm 2006-04-26 10:56:26 UTC 
Description of problem:
When osad looses the connection to jabberd, it stops running.

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

How reproducible:
always

Steps to Reproduce:
1. Install and start osad on a system registered with the Satellite.
2. Run "service jabberd restart" on the Satellite server.
3. Run "service osad status" on the Satellite client.
  
Actual results:
The osad process dies, administrators loose the Push to Client functionality
until they manually restart the osad service on all clients.

Expected results:
osad should continue running, and wait for the Jabber server to come back.

Additional info:
Currently, we install a crontab entry to periodically check if osad is still
running, and run "services osad restart" if it is not.
Note You need to log in before you can comment on or make changes to this bug.