[Spacewalk-list] osa-dispatcher (1.6 nightly) now requires a password

[Jan Pazdziora]

On Wed, Dec 07, 2011 at 09:12:23AM -0500, Scott Worthington wrote:
> On 12/5/2011 12:51 PM, Milan Zazrivec wrote:
> > On Monday 05 December 2011 18:21:33 Scott Worthington wrote:
> >
> >> What shared password needs to be added & where for osa-dispatcher on
> >> the Spacewalk server?  Since this is a new table field, do clients
> >> have to re-register with the the osa-dispatcher?
> > 
> > Clients don't have to do anything.
> > 
> > On the server, you just need to:
> > * stop osa-dispatcher & jabberd
> > * update to latest nightly spacewalk-backend* & osa-dispatcher
> > * rm -f /var/lib/jabberd/db/*
> > * start jabberd & osa-dispatcher
> 
> Hello,
> 
> In 1.6-nightly, osa-dispatcher-5.10.28-1.el6 does not seem to start up 
> unless you 'rm -f /var/lib/jabberd/db/*' in 1.6-nightly.  This is after 

Yes, that's what Milan has noted above.

> tail /var/log/rhn/osa-dispatcher.log
> 
> 2011/12/07 08:50:27 -04:00 4142 0.0.0.0: osad/jabber_lib.__init__
> 2011/12/07 08:50:27 -04:00 4142 0.0.0.0: osad/jabber_lib.setup_connection('Connected to jabber server', 'spacewalk-01.somedomain.com')
> 2011/12/07 08:50:27 -04:00 4142 0.0.0.0: osad/osa_dispatcher.fix_connection('Upstream notification server started on port', 1290)
> 2011/12/07 08:50:28 -04:00 4142 0.0.0.0: osad/jabber_lib.process_forever

So it works fine then, right?

> Is the password field in the postgresql table rhnpushdispatcher supposed 
> to become populated when osa-dispatcher starts?  I have not observed data 

Yes.

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat