[Spacewalk-list] OSAD not picking up updates

[Robert Paschedag]

I really don't understand, why many people have problems using osad.

In our production environment (500+ server), this is working. The only problem I have is "load" when you want to do something on many servers. Then, performance is going down.

But I don't know, what's the difference in mine and your setups. I register server to spacewalk, enable all remote actions and install osad. Done!

You're all using SSL with osad, right? You all have enabled remote controls? (rhn-action-control --enable-all)

My only problem I ever had was somebody cloned a VM (already registered) and did not remove the osad-auth file so both systems logged into jabber server with the same "credentials" kicking out.

Regards
Robert
Am 13.05.2016 19:18 schrieb "Sorensen, Paul - (p)" <pauls at telenav.com>:
>
> Is that the only piece OSAD on the client does?  I’ve also spent several months trying to get OSAD working consistently, with little luck.   Seems like a cron job is the better route all around – consistent, reliable, simple.
>
>  
>
> What about “rhncfg-client get” – do you not manage configuration files as well? 
>
>  
>
> There is a mention of replacing OSAD here:  https://fedorahosted.org/spacewalk/wiki/BrainBox
>
>  
>
>  
>
> From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Matt Moldvan
> Sent: Friday, May 13, 2016 9:14 AM
> To: spacewalk-list at redhat.com
> Subject: Re: [Spacewalk-list] OSAD not picking up updates
>
>  
>
> I'm with Maxime... I spent months trying to get OSAD to work properly, and we recently had a major issue with some network equipment that lead to many OSAD clients going offline.  Personally I'm just about done with it and ready to implement a cron job to do rhn_check every 5 minutes...
>
>  
>
> On Fri, May 13, 2016 at 10:44 AM Maxime VEROONE <maxime.veroone at nordnet.fr> wrote:
>>
>> We have personally chosen to restart both the whole jabberd/osa-dispatcher stack and the osad clients every morning.
>> We banged our heads way too much trying to figure out why osad clients randomly loose communications with the server without any log/alert/crash
>>
>> Maxime VEROONE
>> Capensis SARL
>> Lille, France
>>
>> De : spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] De la part de Matthew Madey
>> Envoyé : vendredi 13 mai 2016 16:27
>> À : spacewalk-list at redhat.com
>> Objet : Re: [Spacewalk-list] OSAD not picking up updates
>>
>> Are there any errors in /var/log/rhn/osa-dispatcher.log? Also try running the below command on your clients
>> rm -f /etc/sysconfig/rhn/osad-auth.conf;   service osad restart
>> If you are running a host firewall or have firewalls in place on your network, ensure port 5222 is open between clients and your Spacewalk server
>> On May 13, 2016 8:44 AM, "Daryl Rose" <darylrose at outlook.com> wrote:
>> OSAD is not picking up scheduled updates.    To the best of my knowledge, everything is running and I don't see any errors on the server or on the clients.  osad is running on the client, osa-dispatcher as well as the jabberd processes are running on the server.   The packages will be picked up and applied by rhnsd, but I have to wait for it to check in.   I would like to have the packages picked up immediately via osad.
>>
>> BTW, I'm using SW version 2.3.
>>
>> Any thoughts on why osad isn't picking up packages?
>>
>> Thanks
>>
>> Daryl
>>
>> _______________________________________________
>> 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