[Spacewalk-list] osa-dispatcher (1.6 nightly) now requires a password
Scott Worthington
scott.c.worthington at gmail.com
Wed Dec 7 14:12:23 UTC 2011
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
>
> -MZ
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
a stop and a start of spacewalk-service (including rebooting the server).
Spacewalk is running on CentOS 6.0 CR. Spacewalk is up-to-date with
1.6-nightly.
[root at spacewalk-01 ~]# rpm -qa | grep osa-d
osa-dispatcher-5.10.28-1.el6.noarch
osa-dispatcher-selinux-5.10.28-1.el6.noarch
* Stop spacewalk
spacewalk-service stop
* Start spacewalk
spacewalk-service start
* Examine the logs...
tail /var/log/rhn/osa-dispatcher.log
2011/12/07 09:08:00 -04:00 5522 0.0.0.0: osad/jabber_lib.__init__
2011/12/07 09:08:00 -04:00 5522 0.0.0.0: osad/jabber_lib.setup_connection('Connected to jabber server', 'tpa-spacewalk-01.allianceoneinc.com')
2011/12/07 09:08:00 -04:00 5522 0.0.0.0: osad/jabber_lib.register('ERROR', 'Invalid password')
* Stop spacewalk
spacewalk-service stop
* Remove jabber's tables
rm -f /var/lib/jabberd/db/*
* Start up spacewalk
spacewalk-service start
* Examine logs...
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
Is the password field in the postgresql table rhnpushdispatcher supposed
to become populated when osa-dispatcher starts? I have not observed data
in the password field when osa-dispatcher successfully starts.
Thank you for your time,
ScottW
More information about the Spacewalk-list
mailing list