Bug 682779

Summary: OSA Dispatcher fails to start
Product: [Community] Spacewalk Reporter: Dan Bateman <danielba>
Component: ServerAssignee: Michael Mráka <mmraka>
Status: CLOSED DEFERRED QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.3CC: jpazdziora, markrwatts
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-05 07:05:35 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: 723481    

Description Dan Bateman 2011-03-07 15:16:40 UTC
Description of problem:
Installed Spacewalk as per the Wiki - followed all instructions.

When starting rhn-satellite or restarting the following error occurs:


Starting osa-dispatcher: /usr/lib/python2.6/site-packages/jabber/jabber.py:68: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha, time
RHN 899 2011/03/07 15:08:43 +01:00: ('Connection attempt failed', 12154, 'ORA-12154: TNS:could not resolve the connect identifier specified\n')
RHN 899 2011/03/07 15:08:43 +01:00: ('Error caught:',)
RHN 899 2011/03/07 15:08:43 +01:00: ('Traceback (most recent call last):\n  File "/usr/share/rhn/osad/jabber_lib.py", line 118, in main\n    self.setup_config(config)\n  File "/usr/share/rhn/osad/osa_dispatcher.py", line 80, in setup_config\n    rhnSQL.initDB()\n  File "/usr/lib/python2.6/site-packages/spacewalk/server/rhnSQL/__init__.py", line 121, in initDB\n    __init__DB(backend, host, port, username, password, database)\n  File "/usr/lib/python2.6/site-packages/spacewalk/server/rhnSQL/__init__.py", line 52, in __init__DB\n    __DB.connect()\n  File "/usr/lib/python2.6/site-packages/spacewalk/server/rhnSQL/driver_cx_Oracle.py", line 385, in connect\n    raise apply(sql_base.SQLConnectError, err_args)\nSQLConnectError: (12154, \'ORA-12154: TNS:could not resolve the connect identifier specified\\n\', \'XE\', \'Connection_Connect(): server attach\')\n',)

The same error is seen in the /var/log/rhn/osa-dispatcher.log regularly.

Version-Release number of selected component (if applicable):
osa-dispatcher-5.9.55-1.el6.noarch
spacewalk-backend-1.3.57-1.el6.noarch


How reproducible:
Everytime

Steps to Reproduce:
1. /usr/sbin/rhn-satellite restart
2.
3.
  
Actual results:
osa-dispatcher errors during startup

Expected results:
No errors during startup.


Additional info:
Running on RHEL6 x86_64 - Oracle XE

Comment 1 Mark Watts 2011-04-19 08:11:34 UTC
I'm seeing this exact same error on a fresh Spacewalk 1.3 install, but using Oracle 11gR2.
"spacewalk-setup --disconnected" is able to populate the database but osa-dispatecher fails on restart with this error.

Comment 2 Jan Pazdziora (Red Hat) 2011-07-20 11:52:14 UTC
Aligning under space16.

Comment 3 Jan Pazdziora (Red Hat) 2011-07-25 17:58:33 UTC
Can you guys check the permissions on your /etc/tnsnames.ora file?

By the way, we've changed the installer for Spacewalk 1.4 to not touch (or need) that file at all, so if the permissions turns out to be the problem on your installation, I'd close this bugzilla.

Comment 4 Dan Bateman 2011-08-01 09:07:37 UTC
Unfortunately I rebuilt Spacewalk on RHEL5 and it worked ok,as this was some time ago.

Comment 5 Jan Pazdziora (Red Hat) 2011-08-05 07:05:35 UTC
(In reply to comment #4)
> Unfortunately I rebuilt Spacewalk on RHEL5 and it worked ok,as this was some
> time ago.

Thanks.

Let me close this bugzilla now.