Crowd Installation error -->HTTTP Status 404 - Not Found

HTTP Status 404-Not Found.pngI was using Crowd 3.0.2 and noticed there is a newer release (Crowd 3.1.1) tried to install this version and got the above error message.

Any assistance is appreciated.

2 answers

0 votes
Ann Worley Atlassian Team Dec 11, 2017

Hi Ayesha,

Thanks for trying Crowd 3.1.1.

Please let me know what steps you took to install the new version of Crowd and whether it was an upgrade or a new installation that produced the error.

Please let us know any related error messages in the logs located at:

  • <crowd-home>/logs
  • <crowd-install>/apache-tomcat/logs

I look forward to hearing more about the issue you are running into.

Thanks,

Ann

The log on Crowd_home is for 3.0.2 version. I am doing a new installation

Given below atlassian-crowd-3.1.1/apache-tomcat/logs/catalina.2017-12-11

11-Dec-2017 09:54:02.662 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [C:\Progra~1\Java\jdk1.8.0_152\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;.]
11-Dec-2017 09:54:02.897 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8095"]
11-Dec-2017 09:54:03.288 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
11-Dec-2017 09:54:03.288 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1259 ms
11-Dec-2017 09:54:03.303 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
11-Dec-2017 09:54:03.303 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.20
11-Dec-2017 09:54:03.350 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deploying configuration descriptor [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\conf\Catalina\localhost\crowd.xml]
11-Dec-2017 09:54:14.038 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
11-Dec-2017 09:54:14.038 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/crowd] startup failed due to previous errors
11-Dec-2017 09:54:14.116 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deployment of configuration descriptor [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\conf\Catalina\localhost\crowd.xml] has finished in [10,766] ms
11-Dec-2017 09:54:14.116 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deploying configuration descriptor [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\conf\Catalina\localhost\openidclient.xml]
11-Dec-2017 09:54:19.148 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deployment of configuration descriptor [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\conf\Catalina\localhost\openidclient.xml] has finished in [5,032] ms
11-Dec-2017 09:54:19.148 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deploying configuration descriptor [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\conf\Catalina\localhost\openidserver.xml]
11-Dec-2017 09:54:32.961 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deployment of configuration descriptor [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\conf\Catalina\localhost\openidserver.xml] has finished in [13,813] ms
11-Dec-2017 09:54:32.961 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\webapps\ROOT]
11-Dec-2017 09:54:33.274 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\webapps\ROOT] has finished in [313] ms
11-Dec-2017 09:54:33.289 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8095"]
11-Dec-2017 09:54:33.305 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 30012 ms
11-Dec-2017 14:17:57.381 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [C:\Progra~1\Java\jdk1.8.0_152\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;.]
11-Dec-2017 14:17:57.896 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8095"]
11-Dec-2017 14:17:58.849 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
11-Dec-2017 14:17:58.849 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 2806 ms
11-Dec-2017 14:17:58.881 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
11-Dec-2017 14:17:58.881 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.20
11-Dec-2017 14:17:58.928 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deploying configuration descriptor [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\conf\Catalina\localhost\crowd.xml]
11-Dec-2017 14:18:14.460 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
11-Dec-2017 14:18:14.460 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/crowd] startup failed due to previous errors
11-Dec-2017 14:18:14.569 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deployment of configuration descriptor [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\conf\Catalina\localhost\crowd.xml] has finished in [15,626] ms
11-Dec-2017 14:18:14.585 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deploying configuration descriptor [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\conf\Catalina\localhost\openidclient.xml]
11-Dec-2017 14:18:20.616 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deployment of configuration descriptor [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\conf\Catalina\localhost\openidclient.xml] has finished in [6,047] ms
11-Dec-2017 14:18:20.616 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deploying configuration descriptor [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\conf\Catalina\localhost\openidserver.xml]
11-Dec-2017 14:18:38.008 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deployment of configuration descriptor [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\conf\Catalina\localhost\openidserver.xml] has finished in [17,392] ms
11-Dec-2017 14:18:38.117 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\webapps\ROOT]
11-Dec-2017 14:18:38.446 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\SW_Inst\atlassian-crowd-3.1.1\apache-tomcat\webapps\ROOT] has finished in [329] ms
11-Dec-2017 14:18:38.461 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8095"]
11-Dec-2017 14:18:38.477 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 39614 ms

-------------------------

Given below atlassian-crowd-3.1.1/apache-tomcat/logs/localhost.2017-12-11

 

11-Dec-2017 09:54:16.460 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log No Spring WebApplicationInitializer types detected on classpath
11-Dec-2017 09:54:16.554 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Initializing Spring root WebApplicationContext
11-Dec-2017 09:54:23.414 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log No Spring WebApplicationInitializer types detected on classpath
11-Dec-2017 09:54:28.898 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Initializing Spring root WebApplicationContext
11-Dec-2017 09:54:31.477 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Starting spray application ...
11-Dec-2017 09:54:32.055 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Automatically setting spray.servlet.root-path to '/openidserver'
11-Dec-2017 09:54:32.617 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: loaded (conf ok)
11-Dec-2017 14:18:17.585 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log No Spring WebApplicationInitializer types detected on classpath
11-Dec-2017 14:18:17.679 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Initializing Spring root WebApplicationContext
11-Dec-2017 14:18:27.007 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log No Spring WebApplicationInitializer types detected on classpath
11-Dec-2017 14:18:33.945 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Initializing Spring root WebApplicationContext
11-Dec-2017 14:18:36.571 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Starting spray application ...
11-Dec-2017 14:18:37.071 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Automatically setting spray.servlet.root-path to '/openidserver'
11-Dec-2017 14:18:37.711 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: loaded (conf ok)

0 votes
Ann Worley Atlassian Team Dec 11, 2017

I understand you are installing Crowd on a different server or you shut down Crowd 3.0.2 to make sure there is no port conflict on port 8095.

In order to install Crowd, it is necessary to 

Specify your Crowd Home directory by editing the configuration file at: {CROWD_INSTALL}\crowd-webapp\WEB-INF\classes\crowd-init.properties. 

Based on the log entries you posted, "Full details will be found in the appropriate container log file" I suspect there may be something in the home directory log that will give us a better hint:

11-Dec-2017 09:54:14.038 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
11-Dec-2017 09:54:14.038 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/crowd] startup failed due to previous errors

I have added crowd.home=C:/data/Crowd-home to crowd-init.properties.

How do I shut down Crowd 3.0.2 ?

The C:\data\crowd-hone\logs\atlassian-crowd has log details on 2017-12-07 which relates to crowd version 3.0.2

 

---------------------Part 1 -----


atlassian-crowd_V1.pngatlassian-crowd_V2.png

Log file is very long. I have give some from the start and entries from the end. All these relate to 07/12/2017. (i.e. version 3.0.2)

Marcin Kempa Atlassian Team Dec 12, 2017

Hi @Ayesha Karunaratne

From the last log entry you've shared it seems that jdbc/CrowdTest jndi context is not defined in your server.xml which might be the cause why the Crowd application is not starting up.

Could you check the <crowd-install>/apache-tomcat/conf/server.xml contains jdbc/CrowdTest?

Could you also share why are you using jdbc jndi resource rather than jdbc connection?

 

Hope that helps,

Marcin Kempa

Hi Marcin,

If you followed my email trail I said I initially used version 3.0.2. The log (C:\data\crowd-hone\logs\atlassian-crowd ) is from this version. Yes I had a database issue and I should have used CrowdTest. This is my first time trying to install Atlassian products.  Since jdbc connection didn't work I tried jndi connection. Instruction given is inadequate to understand the environment for first time user.

Since I saw a newer version (version 3:1;1) I tried to use that. I do not get to initial wizard screen. ( I was able to get here from version 3.0.2)

I have set up JAVA_HOME, CROWD_HOME and have run  the start_crowd.bat file as the administrator.

Unfortunately your reply is not relevant to my issue. Appreciate your time.

Ayesha

Marcin Kempa Atlassian Team Dec 12, 2017

Hi @Ayesha Karunaratne

Sorry I did not search for your other questions previously, thus I probably did not see the whole picture.

My current understanding of your issue is that you are installing Crowd on some test environment. You've started with 3.0.2 version but once 3.1.1 was released you've decided to move on to the latest one.

From your previous questions I am not sure if you succeeded in spinning up Crowd 3.0.2 and if you've managed to connect it to database (MSSql in your example). Also I am not sure how did the upgrade process look like? I assume that you've stopped previous Crowd process (3.0.2) and then started 3.1.1 with the same config (crowd-init.properties, pointing to the same home directory).

If this is your test environment and provided that you do not have any crucial data / configuration in Crowd's database I would suggest to start installing Crowd 3.1.1 from scratch again.

First of all please select a dedicated machine for your test Crowd installation. Since you are setting up a test instance I assume that no other Crowd applications will be running on it (if you need to stop any Crowd instance make sure it is not in production use).

Once you are ready, please follow the instruction mentioned here https://confluence.atlassian.com/crowd/installing-crowd-24248834.html. For home directory I suggest using a new, empty one.

Please make sure you are running Crowd on supported platforms (for example Java9 is not yet supported).

If you happen to run into database connectivity issues, please let us know and post logs from the Crowd setup {crowd-home}\logs\atlassian-crowd.log. If possible I would go for JDBC connection rather than JNDI one.

Best Regards,

Marcin Kempa

I am doing a new installation. ( Not a upgrade). I have installed JAVA8U152. I am trying to use the wizard. http://localhost:8095/crowd

Cannot get to the first screen. says

'Page cannot be displayed' yesterday it said 'HTTP Status 404-Not Found'

Marcin Kempa Atlassian Team Dec 12, 2017

@Ayesha Karunaratne

 

Could you share the log files from your instance covering the Crowd application startup?

The logs are located here:

  • <crowd-home>/logs
  • <crowd-install>/apache-tomcat/logs

Please share both Crowd and Apache Tomcat log and send those files to my email address: mkempa@atlassian.com

 

Best Regards,

Marcin Kempa

I manage to install crowd 3.1.1 using the wizard successfully.

Unable to invoke crowd. using either of links

http://localhost:8095/crowdtest/

http://SOHCROWDT:8095/crowdtest/

 

SOHCROWDT = server on which Crowd is installed

Marcin Kempa Atlassian Team Dec 15, 2017

Hi @Ayesha Karunaratne,

I am glad that you was able to install Crowd using setup wizard.

As for your current problem, by default Crowd should be accessible on 8095 port and context root /crowd. For example:

http://localhost:8095/crowd

Did you modify the context path in the 

<Crowd-Install>/apache-tomcat/conf/server.xml

?

Or maybe did you modify Base URL in the setup wizard?

Right now it is hard for me to understand why so you expect Crowd to be running on /crowdtest context path.

Please note that by only changing the base url in the Crowd's setup wizard you actually do not change the url you would normally access Crowd's console in the web browser.

The base url defined in the setup wizard, which can also be changes in Crowd console config, is used for things like for example generated links for user's password reset.

 

I hope that this helps!

Marcin Kempa

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 27, 2018 in Crowd

The Crowd team is looking for feedback on Server & Data Center customers' identity strategies!

Do you own more than one Server or Data Center product? Do you have challenges provisioning users across your Atlassian products? Are you spending a lot of time integrating each Atlassian product wit...

1,573 views 6 14
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you