[Spacewalk-list] osa-dispatcher not running or not connecting
Michiel van Es
michiele at info.nl
Thu Oct 22 14:33:08 UTC 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- -------- Original Message --------
Subject: [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/22/2009 04:25 PM
> On 10/22/2009 09:30 AM, Michiel van Es wrote:
>> I had to start them in the opposite order (all modules connect to the
>> router as I am correctly informed?)
>>
>
> Yes, sorry.
No prob. :)
>
>> router -D:
>> sm -D:
>> c2s -D:
>> s2s -D:
>
> Can you send the whole logs, please? I don't see anything so far. If
> you're using screen, do a screen -L and then send the screenlog.* files
> (you can send them straight to me if you want to - they will be decently
> sized). And maybe try to run osa-dispatcher a few times.
I use my default ssh terminal from Ubuntu.
Is it better to run:
screen -L router -D etc?
Isn't it possible to startup jabber with verbose logging and send you
the logfiles in stead of the screen debug terminal output?
>
>>
>> osa-dispatcher -N -vvvvv (after firing up a push install package):
>>
>> 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)
>>
>
> Yep - looks like it couldn't connect.
Michiel
>
> Josh
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkrgbSQACgkQSU+5fmlaNkOxdACfYu4L10s+8x22g2YqesAFlg0O
EikAnRQ6j1K7lLcqyjKSimrXmJL064Ee
=ISft
-----END PGP SIGNATURE-----
More information about the Spacewalk-list
mailing list