[Spacewalk-list] OSAD - Clients not receiving actions

[Wojtak, Greg]

If you're able to get the OSA clients working with proxy at all, you're better off than I am.  I (and I think one or two other people on this list) all have the issue where it has never worked; only if the clients communicate directly with the spacewalk server does OSA seem to work for me.

I'm going to try the steps you outlined below and see if I can use that as a starting point to get the proxy communications to the server working properly.

Greg

From: Jeremy Davis <jdavis4102 at gmail.com<mailto:jdavis4102 at gmail.com>>
Reply-To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Date: Thu, 4 Aug 2011 18:51:34 -0400
To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Subject: Re: [Spacewalk-list] OSAD - Clients not receiving actions

List,

Anyone have any ideas as to what is causing this issue? Any assistance you could provide would be greatly appreciated.

Thanks,
Jeremy

On Wed, Aug 3, 2011 at 3:10 PM, Jeremy Davis <jdavis4102 at gmail.com<mailto:jdavis4102 at gmail.com>> wrote:
List,

I have a Spacewalk 1.4 installation and have about 2000+ servers connected to proxy servers. At intermittent times I am unable to send remote commands to clients via the osad service. When this happens the only way to get this feature to work again is to perform the following steps on in order.

Step 1: On Spacewalk Application server.
service jabberd stop
service osa-dispatcher stop
rm -f /var/lib/jabberd/db/*
service jabberd start
sleep 5
service osa-dispatcher start

Step 2: Wait until Proxy server reconnect to Spacewalk Application server.

Step 3: On Spacewalk Proxy servers.
service jabberd stop
rm -f /var/lib/jabberd/db/*
service jabberd start

After I perform these steps the client will be able to receive actions until the next time it goes down. Unfortunately, I am unable to find any logs to determine what is going on. Any assistance you could provide in this would be greatly appreciated.

Thanks,
Jeremy