[Spacewalk-list] osa-dispatcher not running or not connecting
Michiel van Es
michiele at info.nl
Thu Oct 29 15:43:44 UTC 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- -------- Original Message --------
Subject: [Spacewalk-list] osa-dispatcher not running or not connecting
From: Michiel van Es <michiele at info.nl>
To: spacewalk-list at redhat.com <spacewalk-list at redhat.com>
Date: 10/29/2009 09:56 AM
>
>
> -------- Original Message --------
> Subject: [Spacewalk-list] osa-dispatcher not running or not connecting
> From: Michiel van Es <michiele at info.nl>
> To: Joshua Roys <joshua.roys at gtri.gatech.edu>
> Date: 10/27/2009 03:46 PM
>
>
>> -------- Original Message --------
>> Subject: Re: [Spacewalk-list] osa-dispatcher not running or not connecting
>> From: Joshua Roys <joshua.roys at gtri.gatech.edu>
>> To: Michiel van Es <Michiele at info.nl>
>> Date: 10/27/2009 03:18 PM
>
>>> On 10/27/2009 10:12 AM, Michiel van Es wrote:
>>>>> [root at devmx01 sbin]# ./osa-dispatcher -N -vvvvvvvvvvvv
>>>>> --> <?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'>
>>>>>
>>>> Update, it takes some time but then I see:
>>>>
>>>> RHN 4848 2009/10/27 15:09:37 +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 512, in
>>>> connect\n self.header()\n File "/usr/share/rhn/osad/jabber_lib.py",
>>>> line 1193, in header\n self.process(jabber.timeout)\n File
>>>> "/usr/share/rhn/osad/jabber_lib.py", line 1061, in process\n data =
>>>> self._read(self.BLOCK_SIZE)\nerror: (104, \'Connection reset by peer\')\n',)
>>>>
>>> Maybe run a tcpdump and see what is happening?
>> 15:43:56.626250 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto:
>> TCP (6), length: 60) 10.101.0.26.5222 > 10.101.0.26.43390: S, cksum
>> 0x3949 (correct), 3212154399:3212154399(0) ack 3212832223 win 32768 <mss
>> 16396,sackOK,timestamp 2867760 2866160,nop,wscale 7>
>> 0x0000: 4500 003c 0000 4000 4006 25bf 0a65 001a E..<.. at .@.%..e..
>> 0x0010: 0a65 001a 1466 a97e bf75 961f bf7f eddf .e...f.~.u......
>> 0x0020: a012 8000 3949 0000 0204 400c 0402 080a ....9I.... at .....
>> 0x0030: 002b c230 002b bbf0 0103 0307 .+.0.+......
>> 15:43:56.626298 IP (tos 0x0, ttl 64, id 23514, offset 0, flags [DF],
>> proto: TCP (6), length: 64) 10.101.0.26.43390 > 10.101.0.26.5222: .,
>> cksum 0x3947 (correct), ack 1 win 257 <nop,nop,timestamp 2867760
>> 2867760,nop,nop,sack 1 {0:1}>
>> 0x0000: 4500 0040 5bda 4000 4006 c9e0 0a65 001a E..@[. at .@....e..
>> 0x0010: 0a65 001a a97e 1466 bf7f ee82 bf75 9620 .e...~.f.....u..
>> 0x0020: b010 0101 3947 0000 0101 080a 002b c230 ....9G.......+.0
>> 0x0030: 002b c230 0101 050a bf75 961f bf75 9620 .+.0.....u...u..
>> 15:43:56.746125 IP (tos 0x0, ttl 64, id 23515, offset 0, flags [DF],
>> proto: TCP (6), length: 215) 10.101.0.26.43390 > 10.101.0.26.5222: P,
>> cksum 0x15c7 (incorrect (-> 0xadc8), 1:164(163) ack 1 win 257
>> <nop,nop,timestamp 2867880 2867760>
>> 0x0000: 4500 00d7 5bdb 4000 4006 c948 0a65 001a E...[. at .@..H.e..
>> 0x0010: 0a65 001a a97e 1466 bf7f eddf bf75 9620 .e...~.f.....u..
>> 0x0020: 8018 0101 15c7 0000 0101 080a 002b c2a8 .............+..
>> 0x0030: 002b c230 3c3f 786d 6c20 7665 7273 696f .+.0<?xml.versio
>> 0x0040: 6e3d 2731 2e30 2720 656e 636f 6469 6e67 n='1.0'.encoding
>> 0x0050: 3d27 5554 462d 3827 3f3e 3c73 7472 6561 ='UTF-8'?><strea
>> 0x0060: 6d3a 7374 7265 616d 2074 6f3d 2764 6576 m:stream.to='dev
>> 0x0070: 6d78 3031 2e62 7572 6f2e 696e 666f 2e6e mx01.buro.info.n
>> 0x0080: 6c27 2078 6d6c 6e73 3d27 6a61 6262 6572 l'.xmlns='jabber
>> 0x0090: 3a63 6c69 656e 7427 2078 6d6c 6e73 3a73 :client'.xmlns:s
>> 0x00a0: 7472 6561 6d3d 2768 7474 703a 2f2f 6574 tream='http://et
>> 0x00b0: 6865 7278 2e6a 6162 6265 722e 6f72 672f herx.jabber.org/
>> 0x00c0: 7374 7265 616d 7327 2076 6572 7369 6f6e streams'.version
>> 0x00d0: 3d27 312e 3027 3e ='1.0'>
>
>
>> Is it possible that the supplied certificate is not accepted or
>> something else witj jabber?
>
>> Look at my netstat -an ? SYN_RCVD is not good:
>
>> root at devmx01 ~]# netstat -an | grep 5222
>> tcp 0 0 0.0.0.0:5222 0.0.0.0:*
>> LISTEN
>> tcp 0 0 10.101.0.26:5222 172.22.0.104:39143
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.23.3.24:59154
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.86:35239
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.5.10:51865
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.23.3.20:39145
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.117:48053
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.23.3.22:56608
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 10.101.0.170:42861
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 10.101.0.183:42906
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.93:35128
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.5.30:41429
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.23.1.8:35922
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.2.52:39418
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.23.3.61:36714
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.23.8.11:43990
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.23.3.45:34422
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.23.3.25:57408
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.12:56593
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.21.1.13:45633
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 10.101.0.220:45144
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.111:38414
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.202:37836
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.112:59644
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.26:59165
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 10.101.111.116:48387
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.214:35496
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.120:50923
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.122:34888
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 10.101.0.247:47629
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.21.1.13:16852
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.2.51:51712
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.23.3.23:48836
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.195:39411
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 10.101.0.26:43390
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 10.101.0.242:43237
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 10.101.0.46:35900
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.216:49395
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 10.101.0.218:34824
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.211:55642
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.23.3.21:39261
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.228:56093
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 10.101.0.245:36026
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.58:50456
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.23.3.38:50213
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.87:44796
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.212:58668
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.23.2.31:26322
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.23.8.10:42902
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.21.1.13:45635
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.210:35482
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.5.60:37861
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 10.101.0.25:38811
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.82:44755
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 10.101.0.202:44803
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.79:52663
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.23.3.70:47229
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.22.0.51:37248
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 10.101.111.116:48469
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 10.101.111.116:48396
>> SYN_RECV
>> tcp 0 0 10.101.0.26:5222 172.23.7.10:40519
>> SYN_RECV
>> tcp 163 0 10.101.0.26:5222 10.101.0.216:34498
>> ESTABLISHED
>> tcp 1 0 10.101.0.26:5222 172.23.3.14:33388
>> CLOSE_WAIT
>> tcp 163 0 10.101.0.26:5222 10.101.0.236:37834
>> ESTABLISHED
>> tcp 163 0 10.101.0.26:5222 172.22.0.49:53601
>> ESTABLISHED
>> tcp 163 0 10.101.0.26:5222 10.101.0.48:44039
>> ESTABLISHED
>> tcp 163 0 10.101.0.26:5222 172.22.0.200:37351
>> ESTABLISHED
>> tcp 163 0 10.101.0.26:5222 10.101.0.252:45722
>> ESTABLISHED
>> tcp 163 0 10.101.0.26:5222 10.101.0.179:56609
>> ESTABLISHED
>> tcp 164 0 10.101.0.26:5222 10.101.0.26:51642
>> CLOSE_WAIT
>> tcp 163 0 10.101.0.26:5222 10.101.0.238:58963
>> ESTABLISHED
>> tcp 163 0 10.101.0.26:5222 10.101.0.239:53855
>> ESTABLISHED
>> tcp 0 163 10.101.0.26:43390 10.101.0.26:5222
>> ESTABLISHED
>> tcp 163 0 10.101.0.26:5222 172.22.0.76:51943
>> ESTABLISHED
>
>
>
>>> Josh
>
> Is it possible to reconfigure the jabber service and start clean?
> The SYN_RECV packages are not ok..
> The strange thing is that I can not even make a normal jabber connection
> from a client (say pidgin) so I suspect my jabber settings are garbled..
> Is it possible if I post some of my configuration here so people can
> look at it?
Another question:
Is it possbile to set the rhnsd on 5 minutes instead of 4 hours?
In case of a failing jabber server, the clients will pull the requests
every 5 minutes?
Can this do any harm?
Kind regards,
Michiel
>
> Kind regards,
>
> Michiel
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
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
iEYEARECAAYFAkrpuDAACgkQSU+5fmlaNkP24wCcCaOJXoFdlrFng9AzKGAE42zA
51YAoIYwVU2Ih/mSog5+58t5kk1m81PS
=hnDh
-----END PGP SIGNATURE-----
More information about the Spacewalk-list
mailing list