404 not found after server reboot. Confluence 3.5

I inherited an older version of Confluence Server 3.5. After a server reboot, the Confluence login page does not display. Instead, it's giving a 404 Apache Tomcat error. 

3 answers

1 accepted

Thank you for your suggestions Ann and Peter. Looks like I've got it worked out.


Turned out there was a redundant reference to an AD server in the Userconfig xml. After removing the second entry, I was able to restart the service to get it going again. I also had to reapply the redirector dll in IIS.

Peter DeWitt Community Champion Dec 07, 2017

Thanks for stopping back and adding your solution

0 vote
Peter DeWitt Community Champion Dec 05, 2017

@It Dept, check to make sure Tomcat is indeed running.  Are you running a proxy for Confluence?  If it's on the same server that may be the issue too.



As far as I can see, there is only one service related to Tomcat called "Apache Tomcat Confluence" and it is running. I don't believe there is a proxy for it.

Peter DeWitt Community Champion Dec 05, 2017

OK, that's the right service.  

A few troubleshooting thoughts:

  1. Check the logs to see if there is anything strange.
  2. Make sure you are using HTTPS / HTTP whichever is appropriate.
  3. Was confluence configured to require the port to be specified?
  4. Can you access Confluence directly from the server?  You may need to update the hosts file your web address at localhost.
  5. .pd

No access to Confluence from the server. Localhost is set to the loopback address.

Errors I see in the log are...

2017-12-05 16:14:37,862 ERROR [Thread-1] [ContainerBase.[Standalone].[localhost].[/confluence]] log Exception sending context initialized event to listener instance of class com.atlassian.confluence.upgrade.UpgradeLauncherServletContextListener
at com.atlassian.spring.container.ContainerManager.getComponent(ContainerManager.java:32)
at com.atlassian.confluence.upgrade.UpgradeLauncherServletContextListener.contextInitialized(UpgradeLauncherServletContextListener.java:24)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3972)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4467)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:519)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:581)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
2017-12-05 16:14:37,862 ERROR [Thread-1] [apache.catalina.core.StandardContext] log Error listenerStart
2017-12-05 16:14:37,862 ERROR [Thread-1] [apache.catalina.core.StandardContext] log Context [/confluence] startup failed due to previous errors

0 vote
Ann Worley Atlassian Team Dec 05, 2017

Please check the logs at:
<confluence_install>/logs/ (anything recent in this directory)
Note: The <confluence_home> directory is the path defined in the following file: <confluence_install>/confluence/WEB-INF/classes/confluence-init.properties

Find today's startup and scroll down the log until you find an ERROR message. If the message isn't obvious, please post it here so we can help.

If you are running Windows, you might try this to isolate the issue:

  1. Stop the service in services.msc 
  2. Open an elevated command prompt.
  3. Change directories to <confluence_home>/bin.
  4. Run the batch file, start-confluence.bat.
  5. Do not close the resulting command window as that will shut down Confluence.
  6. Wait for the line "Confluence is ready to serve" in the atlassian-confluence.log then see if you can access Confluence in the browser.

If you can access Confluence when starting with the batch file then the service may be the culprit.

There wasn't a start-confluence.bat, but there is a start.bat. Maybe they had it named this way because it's an older version.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Published yesterday in Confluence

Think you know shares vs. @mentions in Confluence? Take this collab quiz.

To anyone who doubts that Atlassians are a little too obsessed with collaboration, and tools related thereto, let me describe a recent discussion we had (which took place on our internal Confluence, ...

106 views 2 4
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