[Spacewalk-list] Clients not uprading software

[Dimitri Yioulos]

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. pastebin):

2014/08/29 13:28:19 -04:00 17700 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error caught:')
2014/08/29 13:28:19 -04:00 17700 0.0.0.0: osad/jabber_lib.main('ERROR', 'Traceback (most
recent call last):\n  File "/usr/share/rhn/osad/jabber_lib.py", line 121, in main\n   
self.process_forever(c)\n  File "/usr/share/rhn/osad/jabber_lib.py", line 179, in
process_forever\n    self.process_once(client)\n  File
"/usr/share/rhn/osad/osa_dispatcher.py", line 182, in process_once\n   
client.retrieve_roster()\n  File "/usr/share/rhn/osad/jabber_lib.py", line 729, in
retrieve_roster\n    stanza = self.get_one_stanza()\n  File
"/usr/share/rhn/osad/jabber_lib.py", line 801, in get_one_stanza\n   
self.process(timeout=tm)\n  File "/usr/share/rhn/osad/jabber_lib.py", line 1055, in
process\n    data = self._read(self.BLOCK_SIZE)\nSSLError: (\'OpenSSL error; will
retry\', "(-1, \'Unexpected EOF\')")\n')
2014/08/29 13:28:29 -04:00 17700 0.0.0.0: osad/jabber_lib.__init__
2014/08/29 13:28:29 -04:00 17700 0.0.0.0: osad/jabber_lib.setup_connection('Connected to
jabber server', 'taunton.onpointfc.com')
2014/08/29 13:28:29 -04:00 17700 0.0.0.0: osad/osa_dispatcher.fix_connection('Upstream
notification server started on port', 1290)
2014/08/29 13:28:29 -04:00 17700 0.0.0.0: osad/jabber_lib.process_forever

I'm not sure what to make of it.  An SSL problem?  I can see the packages awaiting
upgrade for the various clients.  They just don't get installed.  Arrgh.

Dimitri


On Fri, 29 Aug 2014 11:54:40 -0500, Matthew Madey wrote
> 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 need to rebuild the jabberd database.
> 
> service jabberd stop
> rm -Rf /var/lib/jabberd/db/*
> service jabberd start
> 
> On Fri, Aug 29, 2014 at 10:04 AM, Dimitri Yioulos <dyioulos at onpointfc.com>
> wrote:
> 
> > 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 appeared to go fine.
> >
> > However, now when I try to upgrade packages on my clients via the
> > spacewalk Web UI, all
> > I get is the hourglass icon, and Events shows that the job is queued.
> > Previously, when
> > I ran top on a client being updated, I'd see osad-dispatcher (iirc)
> > running.  Now, I don't.
> >
> > I can't, for the life of me, figure out what's wrong.  Would anyone be so
> > kind as to
> > show me how to troubleshoot/correct this issue?
> >
> > Many thanks.
> >
> > Dimitri
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
> >
> > _______________________________________________
> > Spacewalk-list mailing list
> > Spacewalk-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/spacewalk-list
> >
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.


--
Dimitri Yioulos
Chief Information Officer
Director, Facilities Management
Onpoint Financial Corporation
141 Longwater Dr., Suite 102
Norwell, MA 02061

781-871-4220 x1007
dyioulos at onpointfc.com


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.