Thank you, Michael.
One problem at I time.
On startup:
[root@angus rhn]# /usr/sbin/rhn-satellite start
Starting spacewalk services...
Initializing jabberd processes ...
Starting router: [ OK ]
Starting sm: [ OK ]
Starting c2s: [ OK ]
Starting s2s: [ OK ]
Starting osa-dispatcher: /usr/lib/python2.6/site-packages/jabber/jabber.py:68:
DeprecationWarning: the sha module is deprecated; use the hashlib module instead
import sha, time
RHN 31791 2011/08/24 14:09:13 -04:00: ('Traceback (most recent call last):\n
File "/usr/share/rhn/osad/jabber_lib.py", line 250, in setup_connection\n c
= self._get_jabber_client(js)\n File "/usr/share/rhn/osad/jabber_lib.py", line
307, in _get_jabber_client\n c.connect()\n File
"/usr/share/rhn/osad/jabber_lib.py", line 564, in connect\n
jabber.Client.connect(self)\n File
"/usr/lib/python2.6/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: [Errno 111] Connection refused\n',)
[ OK ]
I am guessing that error is because c2s and s2s really failed to start.
[root@angus rhn]# service jabberd status
router (pid 31737) is running...
sm (pid 31744) is running...
c2s dead but subsys locked
s2s dead but subsys locked
/var/log/rhn/osa-dispatcher.log shows the same error as above.
Where should I look next?
-Rod
On Aug 24, 2011, at 10:38 AM, Michael Mraka wrote:
> Grau, Roderick wrote:
> % Spacewalk List:
> %
> % My setup:
> % Oracle 6.0
> % Postgres DB
> % Spacewalk 1.4 upgraded to 1.5
> %
> % I am getting "500 Error - Internal Server Error" after creating a kickstart
> profile and after making edits to an existing kickstart profile.
> %
> % Once I get the 500 error, I reload the page /rhn/YourRhn.do, and go to the
> kickstart profile page and my changes are there.
> %
> % When I start the satellite server I get an osa-dispatcher warning about the
> sha module being deprecated.
> % When I stop the satellite server c2s and s2s failed to stop, probably
> because they are not running.
> %
> % What are the next steps or logs to check to track the problem down?
>
> ISE should be logged in /var/log/httpd/{error_log,ssl_error_log}.
> As it applies to YourRhn.do there can be also a relevant message in
> tomcat's log - /var/log/tomcat{5,6}/catalina.out.
>
> As for osa-dispatcher, it's log is in /var/log/rhn/osa-dispatcher.log.
>
> Regards,
>
> --
> Michael Mráka
> Satellite Engineering, Red Hat
>
> _______________________________________________
> Spacewalk-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/spacewalk-list
--
Roderick Grau
IT Systems Management and Operations
University at Albany
1400 Washington Avenue Ext.
Albany, New York 12222
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
