[Spacewalk-list] error generated when running rhn_check on client
Assaf Flatto
assaf.flatto at goldmoney.com
Wed Apr 13 14:55:15 UTC 2011
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
i just did a restart to paste the results :
/usr/sbin/spacewalk-service restart
Shutting down spacewalk services...
Stopping RHN Taskomatic...
Stopped RHN Taskomatic.
Stopping cobbler daemon: [ OK ]
Stopping rhn-search...
Stopped rhn-search.
Stopping MonitoringScout ...
[ OK ]
Stopping Monitoring ...
[ OK ]
Stopping httpd: [ OK ]
Stopping tomcat5: [ OK ]
Shutting down osa-dispatcher: [ OK ]
Terminating jabberd processes ...
Stopping router: [ OK ]
Stopping sm: [ OK ]
Stopping c2s: [ OK ]
Stopping s2s: [ OK ]
Done.
Starting spacewalk services...
Initializing jabberd processes ...
Starting router: [ OK ]
Starting sm: [ OK ]
Starting c2s: [ OK ]
Starting s2s: [ OK ]
Starting osa-dispatcher: RHN 1438 2011/04/13 14:50:52 -00:00: ('Server did not return a <features /> stanza',)
RHN 1438 2011/04/13 14:50:52 -00:00: ('Traceback (most recent call last):\n File "/usr/share/rhn/osad/jabber_lib.py", line 253, in setup_connection\n c = self._get_jabber_client(js)\n File "/usr/share/rhn/osad/jabber_lib.py", line 310, in _get_jabber_client\n c.connect()\n File "/usr/share/rhn/osad/jabber_lib.py", line 583, in connect\n raise SSLDisabledError\nSSLDisabledError\n',)
[ OK ]
Starting tomcat5: [ OK ]
Waiting for tomcat to be ready ...
# lsof -i |grep tomcat
java 1973 tomcat 70u IPv6 1074846 TCP *:webcache (LISTEN)
java 1973 tomcat 72r IPv6 1075282 TCP *:8009 (LISTEN)
java 1973 tomcat 73r IPv6 1075283 TCP localhost.localdomain:8005 (LISTEN)
java 1973 tomcat 123r IPv6 1075040 TCP localhost.localdomain:44595->localhost.localdomain:postgres (ESTABLISHED)
java 1973 tomcat 124r IPv6 1075043 TCP localhost.localdomain:44596->localhost.localdomain:postgres (ESTABLISHED)
java 1973 tomcat 125r IPv6 1075045 TCP localhost.localdomain:44597->localhost.localdomain:postgres (ESTABLISHED)
java 1973 tomcat 126r IPv6 1075051 TCP localhost.localdomain:44600->localhost.localdomain:postgres (ESTABLISHED)
java 1973 tomcat 127r IPv6 1075049 TCP localhost.localdomain:44599->localhost.localdomain:postgres (ESTABLISHED)
now when i manually start httpd :
/etc/init.d/httpd start
Starting httpd: [ OK ]
[root@~]# lsof -i |grep tomcat
java 1973 tomcat 70u IPv6 1074846 TCP *:webcache (LISTEN)
java 1973 tomcat 72r IPv6 1075282 TCP *:8009 (LISTEN)
java 1973 tomcat 73r IPv6 1075283 TCP localhost.localdomain:8005 (LISTEN)
java 1973 tomcat 123r IPv6 1075040 TCP localhost.localdomain:44595->localhost.localdomain:postgres (ESTABLISHED)
java 1973 tomcat 124r IPv6 1075043 TCP localhost.localdomain:44596->localhost.localdomain:postgres (ESTABLISHED)
java 1973 tomcat 125r IPv6 1075045 TCP localhost.localdomain:44597->localhost.localdomain:postgres (ESTABLISHED)
java 1973 tomcat 126r IPv6 1075051 TCP localhost.localdomain:44600->localhost.localdomain:postgres (ESTABLISHED)
java 1973 tomcat 127r IPv6 1075049 TCP localhost.localdomain:44599->localhost.localdomain:postgres (ESTABLISHED)
java 1973 tomcat 138r IPv6 1079852 TCP localhost.localdomain:44622->localhost.localdomain:postgres (ESTABLISHED)
java 1973 tomcat 139r IPv6 1079854 TCP localhost.localdomain:44623->localhost.localdomain:postgres (ESTABLISHED)
java 1973 tomcat 140r IPv6 1079856 TCP localhost.localdomain:44624->localhost.localdomain:postgres (ESTABLISHED)
and then the spacewalk start script moves and gives this output :
Starting httpd:
Starting Monitoring ...
[ OK ]
Starting MonitoringScout ...
[ OK ]
Starting rhn-search...
Starting cobbler daemon: [ OK ]
Starting RHN Taskomatic...
Done.
and then i have access to the spacewalkj web interface .
On 13 Apr 2011, at 15:44, Jan Pazdziora wrote:
> On Wed, Apr 13, 2011 at 03:30:46PM +0100, Assaf Flatto wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>>
>> Yes , i just upgraded to the 1.4 RC and did a restart of spacewalk and had the same issues i had on 1.3 , both the postgresql and the tomcat hangup .
>
> But in the nextdoor thread you say that in fact, tomcat does not start
> properly at all.
>
> When the spacewalk-service is waiting for tomcat to start listening
> on port 8009, do you see the
>
> INFO: Server startup in ... ms
>
> line in your catalina.out? What does lsof (which is what we use to
> check for tomcat being ready) return in that situation?
>
> --
> Jan Pazdziora
> Principal Software Engineer, Satellite Engineering, Red Hat
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 10.1.0 (Build 860)
Charset: us-ascii
wsBVAwUBTaW5VmK6JZrjLX7GAQjMRwf+NI9sELMO5QXHQ2lJEUNSTflhCpM942FA
0f+3FJrGWNjPcFzD6nJgKjrckf0a3chHzhlIceVTBRgQThlpflTsEZAlTCU5dvS3
5QW+XhLnbRXdQpNJiUk00nasU9EHxm2j9CmB/Zspgasa2+SWouvpkTi61b1a4nK9
cPI/FTsow30v4rBnTDIl2AfH6Td4jYstB4oy1NLFGcUXV74VIzDbmzzYQwiDWBLy
m93KghGPSQqWm6OVJbQzCduRdgwnGh6mu/9SAoTW60lHCN1oBMoQWlsokQgYyuyn
nopkMgMvdybqJYUDkdCb9ff1cBTtPaqpOFpyiqge7kkIIlJKwMwkjg==
=GlXW
-----END PGP SIGNATURE-----
More information about the Spacewalk-list
mailing list