-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
- -------- Original Message -------- Subject: [Spacewalk-list] osa-dispatcher not running or not connecting From: Joshua Roys <[email protected]> To: [email protected] <[email protected]> Date: 10/22/2009 01:30 PM > On 10/21/2009 05:19 AM, Michiel van Es wrote: >>>> Tue Oct 20 14:44:45 2009 authreg.c:661 auth get >>>> Tue Oct 20 14:44:45 2009 authreg_db.c:105 fetching auth creds for user >>>> 'osad-da05225b95' realm '' >>>> Tue Oct 20 14:44:45 2009 authreg_db.c:70 creating new db handle for realm >>>> '' >>>> >>> Was there anything after this? It seems to end abruptly. >> self._read(self.BLOCK_SIZE)\nerror: (104, \'Connection reset by peer\')\n',) >> >> On the osa client side: >> <snip> >> > > Hello, Hi > > It looks like it's something on the jabber (server) side. Was there > anything else after what you previously posted from the c2s -D command? > Could you maybe run all the jabberd services in separate terminals > (s2s -D, c2s -D, sm -D, router -D)? I had to start them in the opposite order (all modules connect to the router as I am correctly informed?) I see on the router -D: Thu Oct 22 15:24:38 2009 router.c:515 want read Thu Oct 22 15:24:38 2009 router.c:855 read action on fd 6 sx (io.c:191) 6 ready for reading sx (io.c:197) tag 6 event 2 data 0x8daea28 Thu Oct 22 15:24:38 2009 router.c:525 reading from 6 Thu Oct 22 15:24:38 2009 router.c:583 read 256 bytes sx (io.c:216) passed 256 read bytes sx (chain.c:93) calling io read chain sx (sasl_gsasl.c:246) doing sasl decode sx (sasl_gsasl.c:262) 256 bytes decoded from sasl channel sx (io.c:240) decoded read data (256 bytes): <route xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' from='devmx01.buro.info.nl' to='s2s'><iq xmlns='jabber:client' id='cdtkf3d2' from='devmx01.buro.info.nl' to='s2s' type='get'><query xmlns='http://jabber.org/protocol/disco#info'/></iq></route> sx (io.c:92) completed nad: <route xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' to='s2s' from='devmx01.buro.info.nl'><iq xmlns='jabber:client' type='get' to='s2s' from='devmx01.buro.info.nl' id='cdtkf3d2'><query xmlns='http://jabber.org/protocol/disco#info'/></iq></route> sx (chain.c:119) calling nad read chain sx (io.c:156) tag 6 event 6 data 0x8daf1a8 Thu Oct 22 15:24:38 2009 router.c:379 unicast route from devmx01.buro.info.nl to s2s Thu Oct 22 15:24:38 2009 router.c:424 writing route for 's2s' to 127.0.0.1, port 44982 sx (chain.c:106) calling nad write chain sx (io.c:406) queueing for write: <route xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' to='s2s' from='devmx01.buro.info.nl'><iq xmlns='jabber:client' type='get' to='s2s' from='devmx01.buro.info.nl' id='cdtkf3d2'><query xmlns='http://jabber.org/protocol/disco#info'/></iq></route> sx (io.c:429) tag 8 event 1 data 0x0 Thu Oct 22 15:24:38 2009 router.c:520 want write Thu Oct 22 15:24:38 2009 router.c:869 write action on fd 8 sx (io.c:328) 8 ready for writing sx (io.c:286) encoding 256 bytes for writing: <route xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' to='s2s' from='devmx01.buro.info.nl'><iq xmlns='jabber:client' type='get' to='s2s' from='devmx01.buro.info.nl' id='cdtkf3d2'><query xmlns='http://jabber.org/protocol/disco#info'/></iq></route> sx (chain.c:79) calling io write chain sx (sasl_gsasl.c:218) doing sasl encode sx (sasl_gsasl.c:234) 256 bytes encoded for sasl channel sx (io.c:349) handing app 256 bytes to write sx (io.c:350) tag 8 event 3 data 0x8db1570 Thu Oct 22 15:24:38 2009 router.c:590 writing to 8 Thu Oct 22 15:24:38 2009 router.c:594 256 bytes written sx (io.c:383) tag 8 event 0 data 0x0 Thu Oct 22 15:24:38 2009 router.c:515 want read sx (io.c:431) tag 8 event 0 data 0x0 Thu Oct 22 15:24:38 2009 router.c:515 want read Thu Oct 22 15:25:38 2009 main.c:446 running time checks Thu Oct 22 15:25:38 2009 main.c:451 next time check at 1256217998 Thu Oct 22 15:26:38 2009 main.c:446 running time checks Thu Oct 22 15:26:38 2009 main.c:451 next time check at 1256218058 Thu Oct 22 15:27:39 2009 main.c:446 running time checks Thu Oct 22 15:27:39 2009 main.c:451 next time check at 1256218119 sm -D: Thu Oct 22 15:24:38 2009 sm.c:53 reading from 5 Thu Oct 22 15:24:38 2009 sm.c:78 read 79 bytes sx (io.c:216) passed 79 read bytes sx (chain.c:93) calling io read chain sx (io.c:240) decoded read data (79 bytes): <presence xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' from='s2s'/> sx (io.c:92) completed nad: <presence xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' from='s2s'/> sx (chain.c:119) calling nad read chain sx (io.c:156) tag 5 event 6 data 0x8299b20 Thu Oct 22 15:24:38 2009 sm.c:203 got a packet Thu Oct 22 15:24:38 2009 pkt.c:107 creating new packet Thu Oct 22 15:24:38 2009 mm.c:622 dispatching pkt-router chain Thu Oct 22 15:24:38 2009 mm.c:635 calling module session Thu Oct 22 15:24:38 2009 mm.c:635 calling module disco Thu Oct 22 15:24:38 2009 mod_disco.c:566 presence from component s2s, issuing discovery request Thu Oct 22 15:24:38 2009 pkt.c:107 creating new packet Thu Oct 22 15:24:38 2009 pkt.c:366 delivering pkt to router Thu Oct 22 15:24:38 2009 mm.c:530 dispatching out-router chain Thu Oct 22 15:24:38 2009 mm.c:543 calling module privacy Thu Oct 22 15:24:38 2009 mm.c:550 out-router chain returning 1 sx (chain.c:106) calling nad write chain sx (io.c:406) queueing for write: <route xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' from='devmx01.buro.info.nl' to='s2s'><iq xmlns='jabber:client' id='cdtkf3d2' from='devmx01.buro.info.nl' to='s2s' type='get'><query xmlns='http://jabber.org/protocol/disco#info'/></iq></route> sx (io.c:429) tag 5 event 1 data 0x0 Thu Oct 22 15:24:38 2009 sm.c:48 want write Thu Oct 22 15:24:38 2009 sm.c:243 write action on fd 5 sx (io.c:328) 5 ready for writing sx (io.c:286) encoding 256 bytes for writing: <route xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' from='devmx01.buro.info.nl' to='s2s'><iq xmlns='jabber:client' id='cdtkf3d2' from='devmx01.buro.info.nl' to='s2s' type='get'><query xmlns='http://jabber.org/protocol/disco#info'/></iq></route> sx (chain.c:79) calling io write chain sx (io.c:349) handing app 256 bytes to write sx (io.c:350) tag 5 event 3 data 0x8299c20 Thu Oct 22 15:24:38 2009 sm.c:85 writing to 5 Thu Oct 22 15:24:38 2009 sm.c:89 256 bytes written sx (io.c:383) tag 5 event 0 data 0x0 Thu Oct 22 15:24:38 2009 sm.c:43 want read sx (io.c:431) tag 5 event 0 data 0x0 Thu Oct 22 15:24:38 2009 sm.c:43 want read Thu Oct 22 15:24:38 2009 pkt.c:297 freeing pkt Thu Oct 22 15:24:38 2009 pkt.c:297 freeing pkt Thu Oct 22 15:24:38 2009 mm.c:642 pkt-router chain returning 0 c2s -D: Thu Oct 22 15:24:40 2009 c2s.c:142 writing to 7 Thu Oct 22 15:24:40 2009 c2s.c:146 266 bytes written sx (server.c:29) stream established sx (server.c:39) 7 state change from 1 to 3 sx (server.c:40) tag 7 event 4 data 0x0 sx (server.c:45) building features nad sx (sasl_gsasl.c:355) offering sasl mechanisms sx (sasl_gsasl.c:766) in _sx_sasl_gsasl_callback, property: 5 sx (sasl_gsasl.c:766) in _sx_sasl_gsasl_callback, property: 6 sx (sasl_gsasl.c:375) offering mechanism: PLAIN sx (sasl_gsasl.c:375) offering mechanism: DIGEST-MD5 Thu Oct 22 15:24:40 2009 bind.c:38 not auth'd, offering auth and register sx (io.c:383) tag 7 event 0 data 0x0 Thu Oct 22 15:24:40 2009 c2s.c:35 want read Thu Oct 22 15:24:40 2009 c2s.c:539 write action on fd 7 sx (io.c:328) 7 ready for writing sx (io.c:286) encoding 318 bytes for writing: <stream:features xmlns:stream='http://etherx.jabber.org/streams'><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>PLAIN</mechanism><mechanism>DIGEST-MD5</mechanism></mechanisms><auth xmlns='http://jabber.org/features/iq-auth'/><register xmlns='http://jabber.org/features/iq-register'/></stream:features> sx (chain.c:79) calling io write chain sx (ssl.c:278) in _sx_ssl_wio sx (ssl.c:282) queueing buffer for write sx (ssl.c:298) preparing queued buffer for write sx (ssl.c:360) prepared 394 ssl bytes for write sx (io.c:349) handing app 394 bytes to write sx (io.c:350) tag 7 event 3 data 0x8f19d70 Thu Oct 22 15:24:40 2009 c2s.c:142 writing to 7 Thu Oct 22 15:24:40 2009 c2s.c:146 394 bytes written sx (io.c:383) tag 7 event 0 data 0x0 Thu Oct 22 15:24:40 2009 c2s.c:35 want read Thu Oct 22 15:24:40 2009 c2s.c:525 read action on fd 7 sx (io.c:191) 7 ready for reading sx (io.c:197) tag 7 event 2 data 0x8f19d70 Thu Oct 22 15:24:40 2009 c2s.c:45 reading from 7 Thu Oct 22 15:24:40 2009 c2s.c:104 read 149 bytes sx (io.c:216) passed 149 read bytes sx (chain.c:93) calling io read chain sx (ssl.c:380) in _sx_ssl_rio sx (ssl.c:384) loading 149 bytes into ssl read buffer sx (io.c:240) decoded read data (120 bytes): <iq type='get' id='auth-get-9db85f-0'><query xmlns = 'jabber:iq:auth' ><username>osad-3e8bb143fc</username></query></iq> sx (io.c:92) completed nad: <iq xmlns='jabber:client' id='auth-get-9db85f-0' type='get'><query xmlns='jabber:iq:auth'><username>osad-3e8bb143fc</username></query></iq> sx (chain.c:119) calling nad read chain sx (io.c:156) tag 7 event 6 data 0x8f2e580 Thu Oct 22 15:24:40 2009 authreg.c:661 auth get Thu Oct 22 15:24:40 2009 authreg_db.c:105 fetching auth creds for user 'osad-3e8bb143fc' realm '' Thu Oct 22 15:24:40 2009 authreg_db.c:70 creating new db handle for realm '' s2s -D: Thu Oct 22 15:24:38 2009 router.c:171 got a packet from router, but we're not online, dropping Thu Oct 22 15:24:38 2009 router.c:288 read action on fd 6 sx (io.c:191) 6 ready for reading sx (io.c:197) tag 6 event 2 data 0x8234e78 Thu Oct 22 15:24:38 2009 router.c:44 reading from 6 Thu Oct 22 15:24:38 2009 router.c:69 read 511 bytes sx (io.c:216) passed 511 read bytes sx (chain.c:93) calling io read chain sx (io.c:240) decoded read data (511 bytes): <bind xmlns='http://jabberd.jabberstudio.org/ns/component/1.0'><default/></bind><presence xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' from='devmx01.buro.info.nl'/><presence xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' from='c2s'/><route xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' to='s2s' from='devmx01.buro.info.nl'><iq xmlns='jabber:client' type='get' to='s2s' from='devmx01.buro.info.nl' id='cdtkf3d2'><query xmlns='http://jabber.org/protocol/disco#info'/></iq></route> sx (io.c:92) completed nad: <bind xmlns='http://jabberd.jabberstudio.org/ns/component/1.0'><default/></bind> sx (chain.c:119) calling nad read chain sx (io.c:156) tag 6 event 6 data 0x8233098 Thu Oct 22 15:24:38 2009 router.c:183 coming online Thu Oct 22 15:24:38 2009 [notice] [0.0.0.0, port=5269] listening for connections Thu Oct 22 15:24:38 2009 [notice] ready for connections sx (io.c:92) completed nad: <presence xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' from='devmx01.buro.info.nl'/> sx (chain.c:119) calling nad read chain sx (io.c:156) tag 6 event 6 data 0x824e648 Thu Oct 22 15:24:38 2009 router.c:205 got a packet Thu Oct 22 15:24:38 2009 router.c:215 dropping non-route packet sx (io.c:92) completed nad: <presence xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' from='c2s'/> sx (chain.c:119) calling nad read chain sx (io.c:156) tag 6 event 6 data 0x824ea38 Thu Oct 22 15:24:38 2009 router.c:205 got a packet Thu Oct 22 15:24:38 2009 router.c:215 dropping non-route packet sx (io.c:92) completed nad: <route xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' from='devmx01.buro.info.nl' to='s2s'><iq xmlns='jabber:client' id='cdtkf3d2' from='devmx01.buro.info.nl' to='s2s' type='get'><query xmlns='http://jabber.org/protocol/disco#info'/></iq></route> sx (chain.c:119) calling nad read chain sx (io.c:156) tag 6 event 6 data 0x824ed60 Thu Oct 22 15:24:38 2009 router.c:205 got a packet Thu Oct 22 15:24:38 2009 router.c:229 dropping unknown or invalid packet for s2s component proper Thu Oct 22 15:25:38 2009 main.c:795 running time checks Thu Oct 22 15:25:38 2009 main.c:800 next time check at 1256217998 Thu Oct 22 15:26:38 2009 main.c:795 running time checks Thu Oct 22 15:26:38 2009 main.c:800 next time check at 1256218058 Thu Oct 22 15:27:39 2009 main.c:795 running time checks Thu Oct 22 15:27:39 2009 main.c:800 next time check at 1256218119 Thu Oct 22 15:28:39 2009 main.c:795 running time checks Thu Oct 22 15:28:39 2009 main.c:800 next time check at 1256218179 osa-dispatcher -N -vvvvv (after firing up a push install package): lse: self._sock.connect((self._hostIP, self._port))\n File "<string>", line 1, in connect\nerror: (111, \'Connection refused\')\n',) RHN 16880 2009/10/22 15:24:33 +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',) - --> <?xml version='1.0' encoding='UTF-8'?><stream:stream to='devmx01.buro.info.nl' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'> I think the jabber client connection refused is because the jabber server wans't up at that time..(or the router) Can you make anything out of it? I am suspecting the c2s or sm not working correctly.. > > Josh Michiel > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrgXlsACgkQSU+5fmlaNkPj2gCgzy/tDwPKGC5fJbgQxChNuzrn IQgAnAkgf3YP8RbP3xre/Vg8u3AffaPF =ChqD -----END PGP SIGNATURE----- _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
