Receiving error 500 when accessing to Confluence hosted on Openshift platform

Question

Hello everyone,

I would like to use an Atlassian Confluence on an Openshift 3.11 platform so I used the docker image "atlassian/confluence-server" and deployed it.

I created a route and tried to access it but I stumble on an error 500 page with the logs displaying an error message : org.apache.jasper.JasperException: java.lang.ClassNotFoundException: org.apache.jsp.errors_jsp

I am pretty new to Confluence and a kind of beginner to Openshift. What is the reason of this error and how is it be possible to fix it and access to Confluence ?

Shannon S · Answer

Thomas,

I don't believe that's the location of your Confluence home directory, which is where your logs are located.

* Working with Confluence Logs
* Confluence Home and Other Important Directories

You seem to have a large number of permissions errors as well, which you can resolve with the following:

* The scratchDir specified is unusable

Please try to first correct your directory permissions issues, and then if you're still having issues we can proceed by looking into the Confluence server logs.

Regards,

Shannon

Thomas Montcuquet · Answer

Thank you Shannon for your answer,

I tried to fix the issue while assuming it was disk space related but I didn't find any change. It's strange because the server has normally enough disk space to run a Confluence. I even tried to create a persistent storage on the Openshift plateform dedicated to the Confluence pod with enough space but it didn't worked out (perhaps I got it wrong).

Here is the logs I get : https://drive.google.com/file/d/1K5dokkUHFhL0GmGrwKGxJLhc6BVyCVfR/view?usp=sharing

But when I access to the /opt/atlassian/confluence/logs/ directory there is no files in it.

Thank you,

Thomas

Shannon S · Answer

Thomas,

I'd be interested to see the more detailed Confluence server logs, but I suspect you might not have enough disk space.

See Confluence starts up with error message Unable to load class for JSP for further details.

If this doesn't help resolve your issue, then have a look at what errors are being produced in the server logs when you encounter this error in the UI, and share them here.

Regards,

Shannon