On one of your clients, try this:
service osad stop
rm /etc/sysconfig/rhn/osad-auth.conf
service osad start
Are you getting any errors on the client side? /var/log/osad ?
On Fri, Aug 29, 2014 at 12:37 PM, Dimitri Yioulos
wrote:
> Matt,
>
> Thanks for the info. Still no joy :-( .
>
> The clie
Matt,
Thanks for the info. Still no joy :-( .
The clients are running the 2.2 version. I cleaned out the jabber database. I
also
looked at osa_dispatcher.log (after clearing it out, and restarting the jabber
service),
and here's the output (it's not that long, so I didn't up it to e.g. paste
Did you upgrade your clients' Spacewalk packages? I had issues with OSAD
and clients picking up actions until I upgraded my clients using the new
2.2 client repo: http://yum.spacewalkproject.org/2.2-client/
Also check /var/log/rhn/osa_dispatcher.log on your Spacewalk server for any
errors. You may
Hello Dimitri
Have you tried to use a remote command ?!, for example execute the command
echo "ok" /tmp/out.txt
and in the client, you can check restarting the osad daemon and runing
rhn_check.
If don't work with osad, you have to check your osad configuration btw
probably will work when you ex
Hi, all.
After upgrading to spacewalk 2.2, I had to essentially recreate my spacewalk
installation (this wasn't due to the upgrade; that's another story). I
recreated the
database (postgresql), recreated the channels/repos, updated spacewalk on, and
re-registered, the clients, etc. That all app
