[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Spacewalk-list] osad not working after re-registering




This has solved a lot of osad issues for me in the past...

Run these commands on spacewalk server:

/sbin/service jabberd stop
/sbin/service osa-dispatcher stop
mv /var/lib/jabberd/db/* /tmp/
/sbin/service jabberd start
/sbin/service osa-dispatcher start


Then restart osad clients:
/etc/init.d/osad restart



The files in /var/lib/jabberd/db/ should get regenerated upon jabberd restart, but if they don't you'll have the copy in /tmp/.

-Josh


On Fri, 2010-11-12 at 16:25 -0500, Sean Laurent wrote:
Yup. /var/lib/jabber and everything underneath is owned by jabber user and group.

On Fri, Nov 12, 2010 at 2:58 PM, Glaser, David <dsglaser umich edu> wrote:
I took a look at the pastebins, but didn’t see anything that really stood out. The Segmentation fault is likely causing the issue. Are the files in  /var/lib/jabber[d]/db owned by the jabber user and group?

 

Dave

 

 

From: spacewalk-list-bounces redhat com [mailto:spacewalk-list-bounces redhat com] On Behalf Of Sean Laurent
Sent: Friday, November 12, 2010 2:03 PM



To: spacewalk-list redhat com
Subject: Re: [Spacewalk-list] osad not working after re-registering

 

sm output here:

 


http://pastebin.com/P9zi4wvK


 


router output here:


 


http://pastebin.com/Kds4iM8g


 


-Sean

On Fri, Nov 12, 2010 at 11:59 AM, Glaser, David <dsglaser umich edu> wrote:

If sm isn’t staying running, I’d say that is probably a big part of your problem. Can you post a patebin of the sm output?

 

Dave

 

From: spacewalk-list-bounces redhat com [mailto:spacewalk-list-bounces redhat com] On Behalf Of Sean Laurent
Sent: Friday, November 12, 2010 12:45 PM


To: spacewalk-list redhat com


Subject: Re: [Spacewalk-list] osad not working after re-registering


 

Since I'm not really familiar (at all) with the jabberd service, I'm not entirely sure what I'm looking for... :) That said, I've noticed a couple of things that may or may not be relevant.

 


First, "router" seems to run fine. No obvious errors to my eyes, except for one strange thing:


 


---snip---


Fri Nov 12 11:34:47 2010 router.c:649 want read


Fri Nov 12 11:34:47 2010 router.c:50 advertising bilbo.studyblue.local to all routes (unavail=0)


Fri Nov 12 11:34:47 2010 router.c:996 read action on fd 6


sx (io.c:498) 6 state change from 4 to 6


sx (io.c:499) tag 6 event 7 data 0x0


Fri Nov 12 11:34:47 2010 router.c:1018 close action on fd 6


Fri Nov 12 11:34:47 2010 [notice] [127.0.0.1, port=52659] disconnect


Fri Nov 12 11:34:47 2010 [notice] [bilbo.studyblue.local] offline


Fri Nov 12 11:34:47 2010 router.c:50 advertising bilbo.studyblue.local to all routes (unavail=1)


sx (sx.c:68) freeing sx for 6


sx (sx.c:101) freeing 1 env plugins


sx (sasl_gsasl.c:767) cleaning up conn state


---snip---


 


Not sure why it says unavail=1. Could be unrelated.


 


sm seems to launch fine, but it segfaults as soon as I launch c2s. No obvious errors. Looks like it connects fine to router:


 


---snip---


sx (sx.c:130) authenticating stream (method=SASL/DIGEST-MD5; id=jabberd jabberd-router)


sx (sx.c:135) 6 state change from 2 to 4


sx (sx.c:136) tag 6 event 5 data 0x0


Fri Nov 12 11:34:47 2010 [notice] connection to router established


---snip---


 


c2s definitely shows an error, but I'm not sure if it's before or after sm segfaults:


 


---snip---


Fri Nov 12 11:39:46 2010 c2s.c:185 no host available for requested domain 'bilbo'


sx (error.c:79) prepared error: <stream:error xmlns:stream='http://etherx.jabber.org/streams'><host-unknown xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text xmlns='urn:ietf:params:xml:ns:xmpp-streams'>service requested for unknown domain</text></stream:error>


---snip---


 


I'm not sure why it's referring to the unqualified domain name "bilbo", instead of the FQDN "bilbo.studyblue.local". That's the only thing I can notice.


 


Any suggestions as to what I should be looking for?


 


-Sean


 

On Fri, Nov 12, 2010 at 5:34 AM, Glaser, David <dsglaser umich edu> wrote:

I’d try stopping the jabber service, then (running with script), fire up (as user jabber) /usr/bin/router –D &, /usr/bin/sm –D &, /usr/bin/c2s –D & , and finally /usr/bin/s2s –D &. You should be able to go through the script output and see much better what the problem is.

 

The error ‘session manager for the requested domain is not available’ makes me think that /usr/bin/sm is not running correctly. You may want to take a close look at the /usr/bin/sm info and see if you can see what errors it is throwing.

 

Dave

 

 

From: spacewalk-list-bounces redhat com [mailto:spacewalk-list-bounces redhat com] On Behalf Of Sean Laurent
Sent: Friday, November 12, 2010 2:23 AM


To: spacewalk-list redhat com


Subject: Re: [Spacewalk-list] osad not working after re-registering

 

Hrmmm. Interesting. The server's name is "bilbo", but the FQDN is "bilbo.studyblue.local". Looking through /etc/jabberd/*.xml on the spacewalk server, I found two places that referenced "bilbo" instead of "bilbo.studyblue.local". I updated those and made some progress. Of course, it still doesn't work... :)

 


---snip---


# service osad start


Starting osad: 2010-11-12 01:12:36 osad._setup_config: Updating configuration


2010-11-12 01:12:37 osad._setup_config: Time drift 268


2010-11-12 01:12:37 osad._setup_config: Client name 613496345888de34


2010-11-12 01:12:37 osad._setup_config: Shared key 1f8d4979df825e62db95fde7efe7470cda4683d9


2010-11-12 01:12:37 jabber_lib.setup_connection: Connecting to bilbo.studyblue.local


2010-11-12 01:12:37 jabber_lib._get_jabber_client: 


2010-11-12 01:12:37 jabber_lib._get_jabber_client: Connecting to bilbo.studyblue.local


2010-11-12 01:12:37 jabber_lib.__init__: 


2010-11-12 01:12:37 jabber_lib.__init__: 


2010-11-12 01:12:37 jabber_lib.check_cert: Loading cert <X509Name object '/C=US/ST=WI/L=Madison/O=StudyBlue, Inc./OU=frodo.studyblue.local/CN=frodo.studyblue.local'>


2010-11-12 01:12:37 jabber_lib.connect: 


2010-11-12 01:12:37 jabber_lib.connect: Attempting to connect


--> <?xml version='1.0' encoding='UTF-8'?><stream:stream to='bilbo.studyblue.local' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>


 


2010-11-12 01:12:37 jabber_lib.process: 300


2010-11-12 01:12:37 jabber_lib.process: before select(); timeout 300.0


2010-11-12 01:12:37 jabber_lib.process: select() returned


2010-11-12 01:12:37 jabber_lib._auth_dispatch: <error><host-gone xmlns = 'urn:ietf:params:xml:ns:xmpp-streams'  /><text xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' >session manager for requested domain is not available</text></error>


<-- <error><host-gone xmlns = 'urn:ietf:params:xml:ns:xmpp-streams'  /><text xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' >session manager for requested domain is not available</text></error>


 


2010-11-12 01:12:37 jabber_lib.connect: Connected


---snip---


 


And here's a snippet of the certificate on the Spacewalk server:


 


---snip---


]# cat /etc/pki/spacewalk/jabberd/server.pem


Certificate:


    Data:


        Version: 3 (0x2)


<TEXT DELETED>


        Signature Algorithm: sha1WithRSAEncryption


        Issuer: C=US, ST=WI, L=Madison, O=studyblue.local, OU=bilbo.studyblue.local, CN=bilbo


        Validity


            Not Before: Nov  5 00:21:43 2010 GMT


            Not After : Nov  5 00:21:44 2036 GMT


        Subject: C=US, ST=WI, O=studyblue.local, OU=bilbo.studyblue.local, CN=bilbo/emailAddress=spacewalk TEXT_DELETED


---snip---


 


Anything else obvious at this point? Am I even barking up the right tree, so to speak?


 


-Sean


 

On Thu, Nov 11, 2010 at 7:49 PM, Glaser, David <dsglaser umich edu> wrote:

Just ran into this problem with our Satellite. Our problem appears to have been that the hostname was listed wrong in /etc/jabberd/*.xml . Check the files and make sure that the server names listed there match the server name listed in server.pem (the CAcert). The file that jabber points to is listed in c2s.xml with the <pemfile> stanza. In spacewalk this is usually /etc/pki/spacewalk/jabberd/server.pem I believe.

 

Dave

 

Dave Glaser

University of Michigan: LSA

 

From: spacewalk-list-bounces redhat com [mailto:spacewalk-list-bounces redhat com] On Behalf Of Sean Laurent
Sent: Thursday, November 11, 2010 8:38 PM
To: spacewalk-list redhat com
Subject: [Spacewalk-list] osad not working after re-registering

 

I had a working copy of Spacewalk running CentOS 5.5 x86_64 with several clients connected to it. I then setup a new copy of CentOS on a different server and registered two of the clients with it. Both clients registered successfully and show in the new Spacewalk server. Unfortunately, osad isn't working. With the debug level cranked up to 6, I see the following messages on the client:


 


---snip---


# service osad start


Starting osad: 2010-11-11 19:31:07 osad._setup_config: Updating configuration


2010-11-11 19:31:07 osad._setup_config: Time drift 268


2010-11-11 19:31:07 osad._setup_config: Client name e95df18be2f52f6a


2010-11-11 19:31:07 osad._setup_config: Shared key 9306c8e03531e3786f37b0dd8d6c63e5495a80e1


2010-11-11 19:31:07 jabber_lib.setup_connection: Connecting to bilbo.studyblue.local


2010-11-11 19:31:07 jabber_lib._get_jabber_client: 


2010-11-11 19:31:07 jabber_lib._get_jabber_client: Connecting to bilbo.studyblue.local


2010-11-11 19:31:07 jabber_lib.__init__: 


2010-11-11 19:31:07 jabber_lib.__init__: 


2010-11-11 19:31:07 jabber_lib.check_cert: Loading cert <X509Name object '/C=US/ST=WI/L=Madison/O=StudyBlue, Inc./OU=frodo.studyblue.local/CN=frodo.studyblue.local'>


2010-11-11 19:31:07 jabber_lib.connect: 


2010-11-11 19:31:07 jabber_lib.connect: Attempting to connect


--> <?xml version='1.0' encoding='UTF-8'?><stream:stream to='bilbo.studyblue.local' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>


 


2010-11-11 19:31:07 jabber_lib.process: 300


2010-11-11 19:31:07 jabber_lib.process: before select(); timeout 299.999999046


2010-11-11 19:31:07 jabber_lib.process: select() returned


2010-11-11 19:31:07 jabber_lib._auth_dispatch: <error><host-unknown xmlns = 'urn:ietf:params:xml:ns:xmpp-streams'  /><text xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' >service requested for unknown domain</text></error>


<-- <error><host-unknown xmlns = 'urn:ietf:params:xml:ns:xmpp-streams'  /><text xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' >service requested for unknown domain</text></error>


 


2010-11-11 19:31:07 jabber_lib.connect: Connected


2010-11-11 19:31:07 jabber_lib.connect: Expecting features stanza, got: <error><host-unknown xmlns = 'urn:ietf:params:xml:ns:xmpp-streams'  /><text xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' >service requested for unknown domain</text></error>


Server did not return a <features /> stanza


--> <presence type='unavailable' />


 


2010-11-11 19:31:07 jabber_lib.print_message: SSLError


2010-11-11 19:31:07 jabber_lib.print_message: Could not connect to jabber server bilbo.studyblue.local


Traceback (most recent call last):


  File "/usr/share/rhn/osad/jabber_lib.py", line 254, in setup_connection


    c = self._get_jabber_client(js)


  File "/usr/share/rhn/osad/jabber_lib.py", line 311, in _get_jabber_client


    c.connect()


  File "/usr/share/rhn/osad/jabber_lib.py", line 593, in connect


    raise SSLDisabledError


SSLDisabledError


 


2010-11-11 19:31:07 jabber_lib.setup_connection: Could not connect to any jabber server


---snip---


 


On the server (bilbo.studyblue.local), I see the following error in /var/log/rhn/osa-dispatcher.log:


 


---snip---


2010/11/11 19:35:44 -05:00 6206 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error caught:')


2010/11/11 19:35:44 -05:00 6206 0.0.0.0: osad/jabber_lib.main('ERROR', 'Traceback (most recent call last):\n  File "/usr/share/rhn/osad/jabber_lib.py", line 120, in main\n    c = self.setup_connection(no_fork=no_fork)\n  File "/usr/share/rhn/osad/jabber_lib.py", line 288, in setup_connection\n    resource=self._resource)\n  File "/usr/share/rhn/osad/dispatcher_client.py", line 33, in start\n    self.auth(username, password, resource)\n  File "/usr/share/rhn/osad/jabber_lib.py", line 892, in auth\n    self.SendAndWaitForResponse(auth_set_iq)\n  File "/usr/lib/python2.4/site-packages/jabber/jabber.py", line 401, in SendAndWaitForResponse\n    return self.waitForResponse(ID,timeout)\n  File "/usr/share/rhn/osad/jabber_lib.py", line 1160, in waitForResponse\n    raise TimeoutError()\nTimeoutError\n')


2010/11/11 19:35:54 -05:00 6206 0.0.0.0: osad/jabber_lib.__init__


2010/11/11 19:35:54 -05:00 6206 0.0.0.0: osad/jabber_lib.setup_connection('Connected to jabber server', 'bilbo')


---snip---


 


Any suggestions?


 

-Sean


 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]