[Spacewalk-list] OSAD not picking up updates

Fri May 13 21:13:57 UTC 2016

I actually spent a lot of time researching the back end of this and when
using a load balancer to distribute OSAD connections it was not elegant for
me to use NFS mounts to keep the jabber db files in sync with 8 proxies in
the mix.  So what I did instead is modify the jabber configs on all my
proxies to use the same external Postgres DB that my spacewalk server
does... that part works well now and I can see what happens internally with
OSAD and the Jabber database, and I've seen less corruption of the jabber
entries like others have.

But, unfortunately it seems that there are other factors at play also and
the OSAD client (or maybe the dated version of jabber this is based on)
will corrupt the entries in whatever database Jabber is assigned to use.
Worst case scenario for us was to restart OSAD, which doesn't appear to
have reestablished the connection either... so I don't know.

After manually doing a "service osad restart" on 360 or so systems today, I
see that my number of systems marked as online in the S/W database haven't
increased (and I have a feeling the 2,685 that are there marked as online
are also actually offline).  My only option for now is to remove
/etc/sysconfig/rhn/osad-auth.conf and restart OSAD on all of those
systems.  It's not impossible for me to do that during our Puppet runs
between 0700 and 0900, but I'm worried about so many systems (~7k) doing
that all at once and crushing the database with creating new jabber IDs for
themselves...

There was a commit in 2.4 that was intended to fix this and allow OSAD
clients to reregister instead of having to create a new Jabber ID in either
the Jabber DB files or whatever back end, however at the moment I'm not
seeing that behavior as working...

Sorry for the long reply, OSAD has been stewing in my mind for a while... :)

On Fri, May 13, 2016 at 2:18 PM Sorensen, Paul - (p) <pauls at telenav.com>
wrote:

> Ahh ok – that’s not too bad.
>
>
>
> And no, I did not rename my host, just added a spacewalk proxy to the mix,
> and I’ve been slowly getting clients registered to it.
>
>
>
> Thanks !
>
>
>
>
>
> *From:* spacewalk-list-bounces at redhat.com [mailto:
> spacewalk-list-bounces at redhat.com] *On Behalf Of *Konstantin Raskoshnyi
> *Sent:* Friday, May 13, 2016 10:50 AM
>
>
> *To:* spacewalk-list at redhat.com
> *Subject:* Re: [Spacewalk-list] OSAD not picking up updates
>
>
>
> Restart spacewalk-service restart and check osa-dispatcher logs.
>
>
>
> Did you rename your spacewalk host?
>
>
>
> On Fri, May 13, 2016 at 10:42 AM, Sorensen, Paul - (p) <pauls at telenav.com>
> wrote:
>
> Can you elaborate on this?  I was just about to set up spacewalk proxy
> servers, and I’ve found that deleting that DB directory did help with OSAD
> issues.
>
>
>
> What problems were encountered, and what did you have to do to fix this?
>
>
>
> *From:* spacewalk-list-bounces at redhat.com [mailto:
> spacewalk-list-bounces at redhat.com] *On Behalf Of *Thomas
> *Sent:* Friday, May 13, 2016 10:18 AM
> *To:* spacewalk-list at redhat.com
> *Subject:* Re: [Spacewalk-list] OSAD not picking up updates
>
>
>
> Don't delete the database if you use spacewalk proxies connected to the
> spacewalk server or you'll run into osad problems with clients connected to
> the proxy.
>
> Am 13. Mai 2016 19:00:32 MESZ, schrieb Paul Robert Marino <
> prmarino1 at gmail.com>:
>
> I have had success with a weekly cron job to clean out the jabber database
>
> service jabberd stop
> rm -Rf /var/lib/jabberd/db/*
>  service jabberd start
> service osa-dispacher restart
>
>
>
>
>
>
> On Fri, May 13, 2016 at 12:13 PM, Matt Moldvan <matt at moldvan.com> wrote:
>
>  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 <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
>
>
>
> ------------------------------
>
>
>  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
>
>
> _______________________________________________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20160513/8f2e49d4/attachment.htm>