[Spacewalk-list] question about jabber server and osad clients

[Michiel van Es]

Same here... especially the netstat -an | grep 5222 on the client 
showing the ESTABLISHED is strange..


-------- Original Message --------
Subject: [Spacewalk-list] question about jabber server and osad clients
From: Mullis, Josh (CCI - Atlanta) <josh.mullis at cox.com>
To: spacewalk-list at redhat.com <spacewalk-list at redhat.com>
Date: 11/25/2009 03:46 PM

> 
> To build on this...
> 
> I am having the same issue.
> More on the side of the client not responding to actions from the 
> spacewalk server after a random period of time.
> 
> (NTP is in sync on both)
> 
> 
> 
> Set debug to 10 on client yesterday and get nothing in the logs when it 
> stops responding.
> (Nothing in "osa-dispatcher" log on server either)
> 
> 
> 
> Also, I noticed that on the client side that netstat shows an 
> "ESTABLISHED" connection to the spacewalk server.
> 
> But netstat on the spacewalk server does not show a connection from the 
> client.
> 
> 
> 
> 
> 
> 
> 
> 
> On Wed, 2009-11-25 at 08:17 -0500, Michiel van Es wrote:
>> Hi,
>>
>> We seem to habe a small problem with our Jabber server on spacewalk and
>> the osad client on the spacewalk nodes.
>>
>> Before we reboot the spacewalk server we see a 104 connections connected
>> with local port 5222 (jabber).
>> Whenever we reboot the Spacewalk server the connections are limited to 3
>> (local connections).
>> It seems that the client connections aren't reconnecting if the
>> connection is lost.
>>
>> Is there a setting in /etc/sysconfig/osad or such on the client side
>> that we have to alter to force clients/nodes to reconnect if the
>> spacewalk server is down?
>>
>> Kind regards,
>>
>> Michiel
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com <mailto:Spacewalk-list at redhat.com>
>> https://www.redhat.com/mailman/listinfo/spacewalk-list