Bug 628582

Summary: osa-dispatcher service start fails - traceback
Product: Red Hat Satellite 5 Reporter: Garik Khachikyan <gkhachik>
Component: ServerAssignee: Jan Pazdziora (Red Hat) <jpazdziora>
Status: CLOSED NOTABUG QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: low    
Version: 540CC: cperry, mkoci, shughes
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-31 15:25:27 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:
Bug Depends On:    
Bug Blocks: 487678    

Description Garik Khachikyan 2010-08-30 12:52:27 UTC
Description of problem:
in scopes of /usr/sbin/rhn-satellite start the service start of osa-dispatcher fails with a traceback:
---
Starting osa-dispatcher: RHN 12561 2010/08/30 14:47:19 +02:00: ('Traceback (most recent call last):\n  File "/usr/share/rhn/osad/jabber_lib.py", line 254, in setup_connection\n    c = self._get_jabber_client(js)\n  File "/usr/share/rhn/osad/jabber_lib.py", line 311, in _get_jabber_client\n    c.connect()\n  File "/usr/share/rhn/osad/jabber_lib.py", line 577, in connect\n    jabber.Client.connect(self)\n  File "/usr/lib/python2.4/site-packages/jabber/xmlstream.py", line 464, in connect\n    else: self._sock.connect((self._hostIP, self._port))\n  File "<string>", line 1, in connect\nerror: (111, \'Connection refused\')\n',)
---

Version-Release number of selected component (if applicable):
Satellite-5.4.0-RHEL5-re20100827.0-x86_64.iso
osa-dispatcher-5.9.38-1.el5sat

How reproducible:
always

Steps to Reproduce:
1. /usr/sbin/rhn-satellite restart
2.
3.
  
Actual results:
exception. osa-dispatcher is not started

Expected results:
the service should get started. no console tracebacks1

Additional info:

Comment 1 Jan Pazdziora (Red Hat) 2010-08-31 14:22:21 UTC
What is the SELinux situation on that machine? Any AVC denials?

Comment 5 Jan Pazdziora (Red Hat) 2010-08-31 15:25:27 UTC
(In reply to comment #4)
> ---
> # service jabberd status
> router (pid 5764) is running...
> sm dead but subsys locked
> c2s dead but subsys locked
> s2s dead but subsys locked
> ---

Your jabberd is stopped / dead. It's expected that osa-dispatcher will complain.