Bug #10006
closedFailed to load Rudder login page post installation.
Description
Environment;
-------------------------------------------------
OS : CentOS release 6.7 (Final)
Kernel : 2.6.32-573.el6.x86_64 x86_64
-------------------------------------------------
---Rudder Install Version---
rudder-inventory-ldap-4.0.2.release-1.EL.6.x86_64
rudder-techniques-4.0.2.release-1.EL.6.noarch
rudder-server-relay-4.0.2.release-1.EL.6.noarch
rudder-agent-4.0.2.release-1.EL.6.x86_64
rudder-webapp-4.0.2.release-1.EL.6.noarch
rudder-server-root-4.0.2.release-1.EL.6.noarch
rudder-jetty-4.0.2.release-1.EL.6.noarch
rudder-inventory-endpoint-4.0.2.release-1.EL.6.noarch
rudder-reports-4.0.2.release-1.EL.6.noarch
-------------------------------------------------
HTTPD Version;
-------------------------------------------------
httpd-2.2.15-45.el6.centos.x86_64
-------------------------------------------------
JAVA Version;
-------------------------------------------------
java-1.7.0-openjdk-1.7.0.79-2.5.5.4.el6.x86_64
-------------------------------------------------
Note :
1. All the dependencies have been gracefully resolved prior to Rudder installation.
2. Firewall and selinux has been disabled.
Files
Updated by Alexis Mousset over 7 years ago
Looks like an httpd configuration issue. Are Rudder vhosts (rudder-vhost.conf and rudder-vhost-ssl.conf) in /etc/httpd/conf.d/, and di you have custom httpd configuration on this server?
Do you see error messages in httpd logs, or in /var/log/rudder/webapp/TODAY.stderrout.log?
Updated by Kiran V over 7 years ago
Both the said files ( rudder-vhost.conf and rudder-vhost-ssl.conf ) very much exists and didn't do any custom config. In fact, I tried multiple times by rebuilding new system each time and could reproduce the same issue every time.
Last lines from today.stderrout.log
[2017-01-16 15:21:09] INFO bootstrap.liftweb.Boot - classpath [2017-01-16 15:21:09] INFO application - Application Rudder started 2017-01-16 15:21:09.807:INFO:oejd.DeploymentManager:Deployable added: /opt/rudder/share/webapps/endpoint.xml 2017-01-16 15:21:09.812:INFO:oejw.WebInfConfiguration:Extract jar:file:/opt/rudder/share/webapps/endpoint.war!/ to /var/rudder/tmp/jetty/jetty-127.0.0.1-8080-endpoint.war-_endpoint-any-/webapp Use configuration file defined by JVM property -Dlogback.configurationFile : /opt/rudder/etc/logback.xml 2017-01-16 15:21:12.722:INFO:oejsh.ContextHandler:started o.e.j.w.WebAppContext{/endpoint,file:/var/rudder/tmp/jetty/jetty-127.0.0.1-8080-endpoint.war-_endpoint-any-/webapp/},/opt/rudder/share/webapps/endpoint.war 2017-01-16 15:21:12.831:INFO:/endpoint:Initializing Spring FrameworkServlet 'dispatcher' [2017-01-16 15:21:13] WARN org.springframework.context.annotation.ConfigurationClassEnhancer - @Bean method PropertyPlaceholderConfig.propertyConfigurer is non-static and returns an object assignable to Spring's BeanFactoryPostProcessor interface. This will result in a failure to process annotations such as @Autowired, @Resource and @PostConstruct within the method's declaring @Configuration class. Add the 'static' modifier to this method to avoid these container lifecycle issues; see @Bean Javadoc for complete details [2017-01-16 15:21:13] INFO com.normation.inventory.provisioning.endpoint.config.PropertyPlaceholderConfig - Use configuration file defined by JVM property -Dinventoryweb.configFile : /opt/rudder/etc/inventory-web.properties 2017-01-16 15:21:14.028:INFO:oejs.AbstractConnector:Started SelectChannelConnector@127.0.0.1:8080
Updated by Alexis Mousset over 7 years ago
Have you tried restarting manually httpd after installation?
Updated by Kiran V over 7 years ago
Yes, I tried restarting httpd and rudder application aswell.
Updated by Alexis Mousset over 7 years ago
What is the hostname of the server? We already saw issues when it was "localhost.localdomain" (which is the default on CentOS).
Updated by Kiran V over 7 years ago
hostname gets resolved without any issues, have set the same in /etc/hosts. And I could telnet positively on localhost port 8080 which actually nullifies the application issue. The issue is somewhere in front end apache.
Besides, I have been working with Rudder (3.x deployments are doing great) for quite some time, never had any issues especially from installation angle.
Updated by Vincent MEMBRÉ about 7 years ago
Great news \o/
Do you have more insight of what went wrong and what fixed it ? So we can document it (either in a FAQ or in doc)
Updated by François ARMAND about 7 years ago
- Status changed from New to Rejected
I'm closing the issue but Kiran, if you have any information about how the issue was solved, or about missing document that could have help you avoid the issue completly, we would be glad to hear it. Thanks for you help!
Updated by Kiran V about 7 years ago
Hi François,
The issue was due to presence of rudder-relay-vhost-ssl.conf in /etc/httpd/conf.d/ directory path. The same was generating error "VirtualHost overlap on port 443" at every httpd daemon restart and throwing error page each time; moved the file out from dir path to fix the issue.
My apologies for delay in responding to your query.
Thanks !!
Updated by Benoît PECCATTE about 7 years ago
- Found in version(s) old deleted (
4.0.2)