Thanks Jan.
It does appear that jabber is running though.. Starting spacewalk services... Initializing jabberd processes ... Starting router: [ OK ] Starting sm: [ OK ] Starting c2s: [ OK ] Starting s2s: [ OK ] Starting osa-dispatcher: RHN 5827 2011/09/20 14:17:51 -04:00: ('Traceback (most recent call last):\n File "/usr/share/rhn/osad/jabber_lib.py", line 253, in setup_connection\n c = self._get_jabber_client(js)\n File "/usr/share/rhn/osad/jabber_lib.py", line 310, in _get_jabber_client\n c.connect()\n File "/usr/share/rhn/osad/jabber_lib.py", line 567, 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',) [ OK ] Starting tomcat5: [ OK ] Waiting for tomcat to be ready ... [root@localhost ~]# service jabberd status router (pid 5763) is running... sm dead but subsys locked c2s dead but subsys locked s2s (pid 5784) is running... [root@localhost ~]# service osa-dispatcher status osa-dispatcher (pid 5856) is running... [root@localhost ~]# Thought the sm and c2s being marked as dead could be an issue so I tried restarting jabberd. Start process got past the osa-dispatcher stage but Tomcat still shows as waiting. Should I go back to 1.3? -----Original Message----- From: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Jan Pazdziora Sent: Tuesday, September 20, 2011 1:40 PM To: spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] Waiting for Tomcat to be ready... On Tue, Sep 20, 2011 at 12:01:15PM -0400, Gomes, Rich wrote: > Last week, I remove 1.5 and Oracle completely and re-installed as 1.4 > > Everything looked great at first, services started, I configured some > channels and registered some clients. > > > > But, I needed to restart the machine and the Tomcat issue reared its ugly > head again. Note that osa-dispatcher has *nothing* to do with osa-dispatcher. Tomcat is just the next in the startup script. So let's call this an osa-dispatcher issue. > Here are the results of an strace. > > I am really confused as to what is causing this. I had similar results in 1.5 > until a reboot and it also stopped working. > > I see a lot of errors in the strace but am not sure what needs to be > corrected. Is this a symptom or the actual problem? > [...] > connect(5, {sa_family=AF_INET, sin_port=htons(5222), > sin_addr=inet_addr("127.0.0.1")}, 16) = -1 ECONNREFUSED (Connection > refused) The osa-dispatcher cannot connect to jabberd, which is service started before osa-dispatcher. So you want to check service jabberd status, check if it listens on the port 5222 at all, and the like. -- Jan Pazdziora Principal Software Engineer, Satellite Engineering, Red Hat _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list