Bug #2839
closedRudder 2.4.0~beta3 Webapp interface is still blocked on "Rudder loading" page on CentOS 6 64bits
Description
All seems to work perfectly since, no error appears in the log file. Besides, the application API returns OK:
[root@vagrant-centos-6 ~]# curl http://localhost:8080/rudder/api/status OK
[root@vagrant-centos-6 ~]# curl http://localhost:8080/endpoint/api/status OK
I'm using openJDK 7 from the CentOS 6.3 repository (java-1.7.0-openjdk.x86_64 1:1.7.0.5-2.2.1.el6_3)
Updated by Jonathan CLARKE over 12 years ago
Hmm, that's weird. Have you tried restarting apache ?
Updated by Nicolas PERRON over 12 years ago
Jonathan CLARKE wrote:
Hmm, that's weird. Have you tried restarting apache ?
Yes..but you've just give me the thought of apache2 logs !:
[Thu Aug 23 06:08:36 2012] [error] proxy: HTTP: disabled connection for (localhost) [Thu Aug 23 06:08:36 2012] [error] [client 10.0.2.2] File does not exist: /opt/rudder/share/load-page/files/jquery.ui.base.css, referer: http://server.rudder.local:8080/files/jquery.css [Thu Aug 23 06:08:36 2012] [error] [client 10.0.2.2] File does not exist: /opt/rudder/share/load-page/files/jquery.ui.theme.css, referer: http://server.rudder.local:8080/files/jquery.css [Thu Aug 23 06:08:36 2012] [error] [client 10.0.2.2] File does not exist: /opt/rudder/share/load-page/images, referer: http://server.rudder.local:8080/files/rudder-login.css
proxy: HTTP: disabled connection for (localhost) should be the issue
Updated by Nicolas PERRON over 12 years ago
- Status changed from New to Discussion
It seems that the proxy module is not installed.
[root@vagrant-centos-6 ~]# ls -lh /etc/httpd/conf.d/ total 16K -rw-r--r--. 1 root root 26 23 août 05:15 dav_mod.conf -rw-r--r--. 1 root root 392 13 févr. 2012 README -rw-r--r--. 1 root root 2,3K 23 août 2012 rudder-default.conf -rw-r--r--. 1 root root 299 7 févr. 2012 welcome.conf
[root@vagrant-centos-6 ~]# yum install mod_proxy_html [...] Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package mod_proxy_html.x86_64 0:3.1.2-6.el6 will be installed [...]
Even with this, the reverse proxy still not working.
On SLES system we add these modules in APACHE_MODULES envvar: "rewrite dav dav_fs proxy proxy_http". Could it be that some of them are not present ?
Updated by Jonathan CLARKE over 12 years ago
This post seems to have a similar problem, and some ideas to solve it: http://stackoverflow.com/questions/4240189/errordocument-not-working-with-local-file (he didn't solve it, but maybe the suggestions would be enough for this problem?).
For the proxy configuration, I'm not convinced that RedHat reads that variable in from /etc/sysconfig... you should check, and restrict this to SLES if it doesn't. You may well be missing the "LoadModule" instructions (AFAIK you have to insert these manually on RHEL/CentOS), see http://www.jedi.be/blog/2009/03/03/using-apache-as-a-reverse-proxy-to-access-tomcat-in-virtual-machines/ for example.
Updated by Jonathan CLARKE over 12 years ago
- Category set to 11
- Target version changed from 2.4.0~beta4 to 2.4.0~beta5
Found the missing ticket... it didn't have a category!
Updated by Jonathan CLARKE over 12 years ago
- Target version changed from 2.4.0~beta5 to 2.4.0~rc1
Updated by Nicolas PERRON over 12 years ago
Nicolas PERRON wrote:
It seems that the proxy module is not installed.
[...][...]
Even with this, the reverse proxy still not working.
On SLES system we add these modules in APACHE_MODULES envvar: "rewrite dav dav_fs proxy proxy_http". Could it be that some of them are not present ?
It shouldn't be needed to install the package mod_proxy_html since the command above are not proof of its installation or use. mod_proxy is already used:
# grep proxy /etc/sysconfig/httpd APACHE_MODULES="${APACHE_MODULES} rewrite dav dav_fs proxy proxy_http"
# grep -R proxy /etc/httpd/ /etc/httpd/conf.d/rudder-default.conf: # Local reverse proxy authorization override /etc/httpd/conf.d/rudder-default.conf: # Most unix distribution deny proxy by default (ie /etc/apache2/mods-enabled/proxy.conf in Ubuntu) /etc/httpd/conf/httpd.conf:LoadModule proxy_module modules/mod_proxy.so /etc/httpd/conf/httpd.conf:LoadModule proxy_balancer_module modules/mod_proxy_balancer.so /etc/httpd/conf/httpd.conf:LoadModule proxy_ftp_module modules/mod_proxy_ftp.so /etc/httpd/conf/httpd.conf:LoadModule proxy_http_module modules/mod_proxy_http.so /etc/httpd/conf/httpd.conf:LoadModule proxy_ajp_module modules/mod_proxy_ajp.so /etc/httpd/conf/httpd.conf:LoadModule proxy_connect_module modules/mod_proxy_connect.so /etc/httpd/conf/httpd.conf:# enable the proxy server: /etc/httpd/conf/httpd.conf:#<IfModule mod_proxy.c> /etc/httpd/conf/httpd.conf:# CacheRoot "/var/cache/mod_proxy" /etc/httpd/conf/httpd.conf:# End of proxy directives. Fichier binaire /etc/httpd/modules/mod_proxy_ajp.so concordant Fichier binaire /etc/httpd/modules/mod_auth_digest.so concordant Fichier binaire /etc/httpd/modules/mod_proxy_scgi.so concordant Fichier binaire /etc/httpd/modules/mod_proxy_connect.so concordant Fichier binaire /etc/httpd/modules/mod_cache.so concordant Fichier binaire /etc/httpd/modules/mod_rewrite.so concordant Fichier binaire /etc/httpd/modules/mod_dir.so concordant Fichier binaire /etc/httpd/modules/mod_proxy_balancer.so concordant Fichier binaire /etc/httpd/modules/mod_proxy.so concordant Fichier binaire /etc/httpd/modules/mod_proxy_http.so concordant Fichier binaire /etc/httpd/modules/mod_proxy_ftp.so concordant Fichier binaire /etc/httpd/modules/mod_filter.so concordant
I can conclude that the problem come not from mod_proxy module. Nevertheless, it seems that SELinux as part in it. Disabling it have resolved the problem and the login page appears:
setenforce 0
But actually I can't reproduce the bug since jetty don't want to start propeprly with this error:
nested exception is java.io.FileNotFoundException: /opt/rudder/etc/licenses/licenses.xml (No such file or directory)
Updated by Nicolas PERRON over 12 years ago
Nicolas PERRON wrote:
Nicolas PERRON wrote:
But actually I can't reproduce the bug since jetty don't want to start propeprly with this error:
[...]
Err... this is normal, I've forgotten to initiate some actions with rudder-init.sh.
Updated by Nicolas PERRON over 12 years ago
The problem was only SElinux and it worked since I deactivated it with:
setenforce 0
I wasn't sure of the fix since my test VM was so extremely slow that it give me impression that jetty didn't start.
I suppose the only fix we can do for now is to inform users in the documentation that SELinux should be off.
Updated by Nicolas PERRON over 12 years ago
- Status changed from Discussion to Pending technical review
- % Done changed from 0 to 100
Nicolas PERRON wrote:
The problem was only SElinux and it worked since I deactivated it with:
[...]I wasn't sure of the fix since my test VM was so extremely slow that it give me impression that jetty didn't start.
I suppose the only fix we can do for now is to inform users in the documentation that SELinux should be off.
I have upgraded the documentation
Updated by Jonathan CLARKE over 12 years ago
- Status changed from Pending technical review to Released
Updated by Nicolas PERRON over 12 years ago
- Target version changed from 2.4.0~rc1 to 2.4.0~beta5
Updated by Nicolas PERRON almost 12 years ago
- Project changed from Rudder to 34
- Category deleted (
11)
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 34 to Rudder
- Category set to Packaging