Failure to Start the confluence when upgrading the confluence from 7.4.13 to 7.15.0 and getting ESAP

ramesh.borusu February 7, 2022

Hello,

 

We are upgrading the confluence server from 7.4.13 to 7.15.0 and receiving the below error. we tried to troubleshoot but still confluence is failing to start.

 

07-Feb-2022 20:36:30.124 INFO [Catalina-utility-2] org.apache.catalina.core.ApplicationContext.log 1 Spring WebApplicationInitializers detected on classpath
07-Feb-2022 20:36:30.533 INFO [Catalina-utility-2] org.apache.catalina.core.ApplicationContext.log Initializing Spring DispatcherServlet 'dispatcher'
20:36:30 [Catalina-utility-2] o.a.c.c.C.[.[.[/synchrony-proxy][INFO] log - Initializing Spring DispatcherServlet 'dispatcher'
2022-02-07 20:36:30,706 INFO [Catalina-utility-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 7.13.4 [build 8703 based on commit hash a33d810b18d3e48dc65591b5aef7f541f30b71b6] - synchrony version 4.0.0-master-bfb398fb
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.atlassian.hibernate.adapter.proxy.BytecodeProviderImpl_ImplementV2Proxy (file:/opt/atlassian/confluence/confluence/WEB-INF/lib/hibernate.adapter-1.0.3.jar) to field java.lang.reflect.Field.modifiers
WARNING: Please consider reporting this to the maintainers of com.atlassian.hibernate.adapter.proxy.BytecodeProviderImpl_ImplementV2Proxy
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Warning: validation was turned on but an org.xml.sax.ErrorHandler was not
set, which is probably not what is desired. Parser will use a default
ErrorHandler to print the first 10 errors. Please call
the 'setErrorHandler' method to fix this.
Error: URI=null Line=1: Document is invalid: no grammar found.
Error: URI=null Line=1: Document root element "atlassian-plugin", must match DOCTYPE root "null".
Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
ESAPI: WARNING: System property [org.owasp.esapi.opsteam] is not set
ESAPI: WARNING: System property [org.owasp.esapi.devteam] is not set
ESAPI: Attempting to load ESAPI.properties via file I/O.
ESAPI: Attempting to load ESAPI.properties as resource file via file I/O.
ESAPI: Not found in 'org.owasp.esapi.resources' directory or file not readable: /opt/atlassian/confluence/bin/ESAPI.properties
ESAPI: Not found in SystemResource Directory/resourceDirectory: .esapi/ESAPI.properties
ESAPI: Not found in 'user.home' (/home/confluence) directory: /home/confluence/esapi/ESAPI.properties
ESAPI: Loading ESAPI.properties via file I/O failed. Exception was: java.io.FileNotFoundException
ESAPI: Attempting to load ESAPI.properties via the classpath.
ESAPI: SUCCESSFULLY LOADED ESAPI.properties via the CLASSPATH from '/ (root)' using class loader for DefaultSecurityConfiguration class!
ESAPI: SecurityConfiguration for Validator.ConfigurationFile.MultiValued not found in ESAPI.properties. Using default: false
ESAPI: SecurityConfiguration for Validator.ConfigurationFile not found in ESAPI.properties. Using default: validation.properties
ESAPI: Attempting to load validation.properties via file I/O.
ESAPI: Attempting to load validation.properties as resource file via file I/O.
ESAPI: Not found in 'org.owasp.esapi.resources' directory or file not readable: /opt/atlassian/confluence/bin/validation.properties
ESAPI: Not found in SystemResource Directory/resourceDirectory: .esapi/validation.properties
ESAPI: Not found in 'user.home' (/home/confluence) directory: /home/confluence/esapi/validation.properties
ESAPI: Loading validation.properties via file I/O failed.
ESAPI: Attempting to load validation.properties via the classpath.
ESAPI: validation.properties could not be loaded by any means. fail.. Caught java.lang.IllegalArgumentException; exception message was: java.lang.IllegalArgumentException: Failed to load ESAPI.properties as a classloader resource.
ESAPI: SecurityConfiguration for ESAPI.printProperties not found in ESAPI.properties. Using default: false
ESAPI: SecurityConfiguration for Encryptor.CipherTransformation not found in ESAPI.properties. Using default: AES/CBC/PKCS5Padding
ESAPI: SecurityConfiguration for ESAPI.Logger not found in ESAPI.properties. Using default: org.owasp.esapi.reference.JavaLogFactory
ESAPI: SecurityConfiguration for Logger.LogApplicationName not found in ESAPI.properties. Using default: true
ESAPI: SecurityConfiguration for Logger.LogServerIP not found in ESAPI.properties. Using default: true
ESAPI: SecurityConfiguration for Logger.ApplicationName not found in ESAPI.properties. Using default: DefaultName
ESAPI: SecurityConfiguration for ESAPI.Logger not found in ESAPI.properties. Using default: org.owasp.esapi.reference.JavaLogFactory
ESAPI: SecurityConfiguration for ESAPI.Logger not found in ESAPI.properties. Using default: org.owasp.esapi.reference.JavaLogFactory

 

 

We also tried upgrading to the 7.13.4 and received the same above error. Can you please help us trying to troubleshoot the issue. Thanks!

Support Entitlement Number  : SEN-20818702

1 answer

0 votes
Daniel Ebers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 18, 2022

Hi @ramesh.borusu

seeing this question is a bit old but same time seeing similar requests here for posterity a more general knowledge base entry which can help guiding the way to some basic troubleshooting considerations.

Often, from plain static logfile reading it is hard to pinpoint the reason for Confluence not starting up.

It is easier when sitting in front of the server to check basic things like filesystem healthiness, disk space, memory consumption and so on.

https://confluence.atlassian.com/confkb/confluence-startup-problems-troubleshooting-180846988.html

Regards,
Daniel

Srikanth Kakarla January 10, 2023

@ramesh.borusu

Please check conf/server.xml file, if there are any changes related to SSL password or something similar to that

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events