Bug 189969

Summary:	osad on Satellite client stops when jabberd is restarted on Satellite server
Product:	Red Hat Satellite 5	Reporter:	Carsten Clasohm <clasohm>
Component:	Other	Assignee:	John Wregglesworth <wregglej>
Status:	CLOSED DUPLICATE	QA Contact:	Vlady Zlatkin <vzlatkin>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	cperry, rhn-bugs
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-06-21 16:04:33 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.