Confluence doesn't respond after upgrade to 5.1.4
Asked by Justin McCamish:

Just upgraded our Confluence instance from 4.2.13 to 5.1.4 using the .exe installer and when we go to localhost/confluence (yep, we've checked the path in server.xml) on the host server, the browser (up-to-date Firefox) eventually times out with:

"Service Temporarily Unavailable {#toc-hId-1846910851}
======================================================

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."

It's hosted on Windows (Server 2008) and we have Apache running as a proxy. Today we also upgraded Stash and Jira on the same box to the latest versions and they're running just fine.

We've always run it as a Windows Service but we've tried starting either as a Service or via startup/shutdown.bat but get the same result each time.

I'll come back and supply logs (confluence, tomcat, apache etc...) but wondering in the meantime if there's anything about this that triggers an immediate thought among the assembled minds here. Thanks in advance.

Ok, now for some real information. After attempting to go to localhost:8090/confluence in Firefox (which times out), the log files are as follows:

commons-daemon.2013-07-14

```
[2013-07-14 10:41:27] [info]  Commons Daemon procrun (1.0.7.0 32-bit) started[2013-07-14 10:41:27] [info]  Running 'Confluence280812111433' Service...[2013-07-14 10:41:27] [info]  Starting service...[2013-07-14 10:41:28] [info]  Service started in 1108 ms.
```

confluence280812111433-stdout.2013-07-14

```
2013-07-14 10:41:27 Commons Daemon procrun stdout initialized2013-07-14 10:41:28,526 INFO [main] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 5.1.4 [build 4249 based on commit hash 84a11b3502ae79dd6028856f37ff89838963c1cc]2013-07-14 10:41:30,181 WARN [main] [atlassian.config.xml.AbstractDom4jXmlConfigurationPersister] saveDocumentAtomically Unable to move E:\Atlassian\Application Data\Confluence\confluence.cfg.xml5087084629201407575tmp to E:\Atlassian\Application Data\Confluence\confluence.cfg.xml. Falling back to non-atomic overwrite.
```

confluence280812111433-stderr.2013-07-14

```
2013-07-14 10:41:27 Commons Daemon procrun stderr initializedJul 14, 2013 10:41:27 AM org.apache.tomcat.util.digester.SetPropertiesRule beginWARNING: [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not find a matching property.Jul 14, 2013 10:41:27 AM org.apache.tomcat.util.digester.SetPropertiesRule beginWARNING: [SetPropertiesRule]{Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.Jul 14, 2013 10:41:27 AM org.apache.tomcat.util.digester.SetPropertiesRule beginWARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'debug' to '0' did not find a matching property.Jul 14, 2013 10:41:27 AM org.apache.tomcat.util.digester.SetPropertiesRule beginWARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.Jul 14, 2013 10:41:27 AM org.apache.coyote.http11.Http11Protocol initINFO: Initializing Coyote HTTP/1.1 on http-8090Jul 14, 2013 10:41:27 AM org.apache.catalina.startup.Catalina loadINFO: Initialization processed in 249 msJul 14, 2013 10:41:27 AM org.apache.catalina.core.StandardService startINFO: Starting service Tomcat-StandaloneJul 14, 2013 10:41:27 AM org.apache.catalina.core.StandardEngine startINFO: Starting Servlet Engine: Apache Tomcat/6.0.35
```


Answers:
author: Justin McCamish
body: After severall roll-backs and re-upgrades with the same outcome, we've abandoned the idea of getting it done this weekend.

We're going to take it slowly over the week and call on Atlassian Support along the way. Will post the results (and anything we learn) on this thread.


Tags: confluence-administration