<[email protected]> wrote:
>> 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
Milan,
It appears that minutes ago a new 1.6-nightly was release to the repo.
The available versions were spacewalk-backend-*-1.6.48-1.el6.noarch
(amongst others).
I have updated to the latest nightly and done the following:
* Update
yum -y update
* Stop spacewalk
spacewalk-service stop
* Change to user postgres and apply new schema changes to the
postgresql spaceschema database
su - postgres
cd
/etc/sysconfig/rhn/schema-upgrade/spacewalk-schema-1.5-to-spacewalk-schema-1.6/
psql -d spaceschema -f 132-rhnServerNetwork-update-rhn_probe.sql.postgresql
^D
exit
* Remove old jabber sqlite tables
rm -f /var/lib/jabberd/db/*
* Start spacewalk
spacewalk-service start
* Check osa-dispatcher.log
tail -f /var/log/rhn/osa-dispatcher.log
2011/12/05 15:10:58 -04:00 5925 0.0.0.0: osad/jabber_lib.__init__
2011/12/05 15:10:58 -04:00 5925 0.0.0.0:
osad/jabber_lib.setup_connection('Connected to jabber server',
'spacewalk-01.somedomain.com')
2011/12/05 15:10:58 -04:00 5925 0.0.0.0:
osad/osa_dispatcher.fix_connection('Upstream notification server
started on port', 1290)
2011/12/05 15:10:58 -04:00 5925 0.0.0.0: osad/jabber_lib.process_forever
I'll test the osad clients and see if they are checking in and
functioning, but I assume all is good now.
Thank you for your assistance.
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
