[Spacewalk-list] Spacewalk 0.6 -> 0.7 Upgrade Issues

[Michael Gale]

Hello,

In regards to your first problem, I had the same issue and it was
because of file permissions under /etc/jabberd/...

In /etc/sysconfig/jabberd you will find that jabberd is setup to run as
the jabber user and not root. So the files must be readable as the
jabber user. 

I would check the file permissions first, also to help trouble shoot the
issue you should su to the jabber user and try to start the processes
manually:

For example:
/usr/bin/sm -c /etc/jabberd/sm.xml

Michael Gale


-----Original Message-----
From: spacewalk-list-bounces at redhat.com
[mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Andy Speagle
Sent: December 10, 2009 11:32 AM
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Spacewalk 0.6 -> 0.7 Upgrade Issues

Hi Team,

I just went through the ugprade from 0.6 to 0.7 and everything seemed to
go as planned.  I have a couple of questions regarding the upgrade.

1) First, a small problem.  When the "osa-dispatcher" service is
starting, I get the following output:

Starting osa-dispatcher: RHN 10106 2009/12/10 12:23:04 -05:00:
('Traceback (most recent call last):\n  File
"/usr/share/rhn/osad/jabber_lib.py", line 254, in setup_connection\n
c = self._get_jabber_client(js)\n  File
"/usr/share/rhn/osad/jabber_lib.py", line 311, in _get_jabber_client\n
c.connect()\n  File "/usr/share/rhn/osad/jabber_lib.py", line 577, in
connect\n    jabber.Client.connect(self)\n  File
"/usr/lib/python2.4/site-packages/jabber/xmlstream.py", line 464, in
connect\n    else: self._sock.connect((self._hostIP, self._port))\n
File "<string>", line 1, in connect\nerror: (111, \'Connection refused
\')\n',)
                                                           [  OK  ]

  Even though it says "OK" at the end... and at first glance I am able
to login and see things... this has me somewhat disconcerted.

2) During the package upgrade, a couple of *.rpmnew files were created
for cobbler package... and I'm wondering if I should be concerned.  Here
are the files:

  /etc/cobbler/modules.conf.rpmnew
  /etc/cobbler/settings.rpmnew

  There seem to be a large number of new configuration options in the
cobbler config laid down in these new files... without me dumping a diff
of the two... are there any obvious things that need to be included in
my running config from the new config?

3) The "tsdb" package did not update.  I ran into an error unpacking
it... after a few attempts.  

Error unpacking rpm package tsdb-1.27.21-1.el5.noarch
error: unpacking of archive failed on
file /etc/rc.d/init.d/tsdb_local_queue: cpio: rename

Is there a fundamental problem with the package?... or is the mirror to
which I'm connecting having issues?


Any insight into these would be appreciated...

-- 
Andy Speagle

"THE Student" - UCATS
Wichita State University