Description of problem: There are strange error messages in /var/log/httpd/error_log which should not be there - we do not want any [error] messages there. Version-Release number of selected component (if applicable): Satellite-5.4.0-RHEL5-re20101001.1-x86_64-embedded-oracle How reproducible: always (seen it multiple times) Steps to Reproduce: 1. Install Satellite - this seems to appear that the satellite produces this when is restarted as a last step of the installation process. Actual results: # less /var/log/httpd/error_log [...] [Wed Oct 06 16:03:05 2010] [error] (111)Connection refused: proxy: AJP: attempt to connect to 127.0.0.1:8009 (*) failed [Wed Oct 06 16:03:05 2010] [error] proxy: AJP: failed to make connection to backend: localhost [Wed Oct 06 16:03:09 2010] [error] (111)Connection refused: proxy: AJP: attempt to connect to 127.0.0.1:8009 (*) failed [Wed Oct 06 16:03:09 2010] [error] proxy: AJP: failed to make connection to backend: localhost [Wed Oct 06 16:03:13 2010] [error] (111)Connection refused: proxy: AJP: attempt to connect to 127.0.0.1:8009 (*) failed [Wed Oct 06 16:03:13 2010] [error] proxy: AJP: failed to make connection to backend: localhost [Wed Oct 06 16:03:13 2010] [error] (111)Connection refused: proxy: AJP: attempt to connect to 127.0.0.1:8009 (*) failed [Wed Oct 06 16:03:13 2010] [error] proxy: AJP: failed to make connection to backend: localhost [...] Expected results: No [error] messages in the error_log.
Jan, at the end of the spacewalk-setup, services are restarted. The spacewalk-setup then tries to access the server a couple of times in the wait_for_tomcat method, waiting for tomcat to finish loading. The problem with tomcat is that its init script returns upon start even if tomcat is still not ready to serve the content. So what the error messages mean are actually probes that try to access the server, before telling you that the installation passed alright.
The truth is, we could be able to address this by checking tomcat directly, and only once it's loaded, do a HEAD request via httpd. Taking for more investigation.
Fixed in Spacewalk master, bd0ff15cb3f86cefdcd1c899852bd404bb958aa0.
Tagged and built as spacewalk-setup-1.3.1-1. It will be in tomorrow's Spacewalk nightly composes.
It's regression against Sat 520. :)
Moving ON_QA.
This issue is resolved with the release of RHN Satellite 5.5. As of September 20th 2012, RHN Satellite 5.5 has been generally available. Release Notes and other 5.5 documentation can be found here: https://access.redhat.com/knowledge/docs/Red_Hat_Network_Satellite/ The associated Errata for the 5.5 release are: 5.5 Satellite GA Errata - http://rhn.redhat.com/errata/RHEA-2012-1296.html 5.5 Upgrade Errata - http://rhn.redhat.com/errata/RHEA-2012-1298.html 5.5 RHN Proxy GA Errata - http://rhn.redhat.com/errata/RHEA-2012-1297.html 5.5 RHN Tools GA Errata - http://rhn.redhat.com/errata/RHEA-2012-1299.html Regards, Clifford - Engineering Manager, Satellite