Trouble Starting Confluence after Upgrade: One or more Filters failed to start
Asked by d-moore1:

Hello,

I recently upgraded our confluence server (linux) to the latest (from 5.3) in order deal with one of the recent security confluence vulnerabilities (which seemed to be affecting us - confluence was maxing out our CPU). I believe I've removed the malware and I've run the upgrade installer successfully. However I'm now getting a severe error in catalina.out followed by several warnings.

```
23-May-2019 07:06:35.763 INFO [Catalina-utility-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.register Mapped "{[/reload],methods=[PUT]}" onto publi$
23-May-2019 07:06:36.369 INFO [Catalina-utility-2] org.springframework.context.support.DefaultLifecycleProcessor.start Starting beans in phase 2147483647
23-May-2019 07:06:36.509 INFO [Catalina-utility-2] org.springframework.web.servlet.DispatcherServlet.initServletBean FrameworkServlet 'dispatcher': initialization completed in 7567 ms
23-May-2019 07:12:20.484 SEVERE [Catalina-utility-1] org.apache.catalina.core.StandardContext.startInternal One or more Filters failed to start. Full details will be found in the appropriate container log file
23-May-2019 07:12:20.485 SEVERE [Catalina-utility-1] org.apache.catalina.core.StandardContext.startInternal Context [] startup failed due to previous errors
23-May-2019 07:12:32.317 WARNING [Catalina-utility-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ROOT] registered the JDBC driver [com.micros$
23-May-2019 07:12:32.318 WARNING [Catalina-utility-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ROOT] registered the JDBC driver [org.h2.Dri$
23-May-2019 07:12:32.318 WARNING [Catalina-utility-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ROOT] registered the JDBC driver [org.postgr$
23-May-2019 07:12:32.319 WARNING [Catalina-utility-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ROOT] registered the JDBC driver [com.github$
23-May-2019 07:12:32.319 WARNING [Catalina-utility-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ROOT] registered the JDBC driver [net.source$
23-May-2019 07:12:32.319 WARNING [Catalina-utility-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ROOT] registered the JDBC driver [org.hsqldb$
23-May-2019 07:12:32.330 WARNING [Catalina-utility-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread na$
java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:543)
23-May-2019 07:12:32.332 WARNING [Catalina-utility-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread na$
java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:543)
23-May-2019 07:12:32.335 WARNING [Catalina-utility-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread na$
java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:543)
23-May-2019 07:12:32.336 WARNING [Catalina-utility-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread na$
java.lang.Object.wait(Native Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:543)
23-May-2019 07:12:32.337 WARNING [Catalina-utility-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread na$
java.lang.Object.wait(Native Method)
```

Several more warnings follow this. Several of the help articles I've found suggest checking the atlassian-confluence.log file. However I don't see one in my atlassian/confluence/logs directory. I can see that our dedicated confluence user is running a "java" process, and that java is bound to port 8090 (our confluence port). Yet still cannot access confluence in my browser.

Has anyone run into anything like this?

Thanks,  
Dan


Answers:
author: Diego
body: Hello there Daniel!

As I see, this could be caused by more than one thing. I would start by:
> **Checking folder permissions**
>
> 1. 
> 2. Check that **\<confluence-home\> folder** is owned by the user used to run Confluence and the user has enough permissions
> 3. Check that **\<confluence-install\> folder** is owned by the user used to run Confluence and the user has enough permissions
> 4. If the user does not have enough permissions, grant them.

**[How to Manage File and Folder Permissions in Linux](https://www.linux.com/learn/how-manage-file-and-folder-permissions-Linux)**

[**How to Set File and Folder Permissions in Windows**](https://www.online-tech-tips.com/computer-tips/set-file-folder-permissions-windows/)

If permissions are all correct and the issue still shows the same problem, we can try this:
> **Checking Database Password**
>
> 1. Shutdown Confluence
> 2. Go into **\<CONFLUENCE_HOME\>/.**
> 3. Open the **confluence.cfg.xml file**.
> 4. Check password and username for database

The main idea here is that something got lost during upgrade. Be it *Folder Permisions* or even *Database Credentials*. If you did not read it still, have a look here:

**[Upgrading Confluence](https://confluence.atlassian.com/doc/upgrading-confluence-4578.html)**

Let us know from you Daniel!


Tags: catalina

confluence-server

server

startup