Confluence not starting No error in Log
Asked by Paul Dennis:

Anyone help with this as confulence not starting. After clearing the log and restart the server the application-confluence.log contains the following.

*** ** * ** ***

2022-09-01 10:12:44,170 INFO \[Catalina-utility-1\] \[com.atlassian.confluence.lifecycle\] contextInitialized Starting Confluence 7.13.0 \[build 8703 based on commit hash 791df1c41ad1e432a490f9fc6f60e3ea49358bee\] - synchrony version 4.0.0-master-f680ea21  
2022-09-01 10:12:48,685 INFO \[Catalina-utility-1\] \[springframework.web.context.ContextLoader\] initWebApplicationContext Root WebApplicationContext: initialization started  
2022-09-01 10:12:54,309 INFO \[Catalina-utility-1\] \[com.atlassian.confluence.lifecycle\] \<init\> Loading EhCache cache manager

*** ** * ** ***

These do not appear to be errors. However cannot access confluence and non of the other log files show an error. Postgres is running.

This is running in a debian vm and I see the error failed to start and I have this in the daemon.log. The cpu is at 100%

*** ** * ** ***

Sep 1 10:33:20 postgresql confluence\[906\]: 2022-09-01 10:33:20,775 INFO \[main\] \[atlassian.confluence.bootstrap.SynchronyProxyWatchdog\] A Context element for ${confluence.context.path}/synchrony-proxy is found in /opt/atlassian/confluence/conf/server.xml. No further action is required  
Sep 1 10:33:20 postgresql confluence\[906\]: ---------------------------------------------------------------------------  
Sep 1 10:33:20 postgresql confluence\[906\]: Existing PID file found during start.  
Sep 1 10:33:20 postgresql confluence\[906\]: Tomcat appears to still be running with PID 1134. Start aborted.  
Sep 1 10:33:20 postgresql confluence\[906\]: If the following process is not a Tomcat process, remove the PID file and try again:  
Sep 1 10:33:20 postgresql confluence\[906\]: UID PID PPID C STIME TTY TIME CMD  
Sep 1 10:33:20 postgresql confluence\[906\]: postfix 1134 1126 0 10:33 ? 00:00:00 smtp -t unix -u -c  
Sep 1 10:33:20 postgresql systemd\[1\]: confluence.service: Control process exited, code=exited status=1  
Sep 1 10:33:20 postgresql systemd\[1\]: Failed to start confluence.service.  
Sep 1 10:33:20 postgresql systemd\[1\]: confluence.service: Unit entered failed state.  
Sep 1 10:33:20 postgresql systemd\[1\]: confluence.service: Failed with result 'exit-code'.

*** ** * ** ***

Then in catalina.out log I have this

*** ** * ** ***

\[0.001s\]\[warning\]\[gc\] -Xloggc is deprecated. Will use -Xlog:gc:/opt/atlassian/confluence/logs/gc-2022-09-01_10-12-40.log instead.  
01-Sep-2022 10:12:40.850 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server\] failed to set property \[debug\] to \[0\]  
01-Sep-2022 10:12:40.938 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Connector\] failed to set property \[debug\] to \[0\]  
01-Sep-2022 10:12:40.959 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine\] failed to set property \[debug\] to \[0\]  
01-Sep-2022 10:12:40.965 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine/Host\] failed to set property \[debug\] to \[0\]  
01-Sep-2022 10:12:41.023 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine/Host/Context\] failed to set property \[debug\] to \[0\]  
01-Sep-2022 10:12:41.066 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine/Host/Context\] failed to set property \[debug\] to \[0\]  
01-Sep-2022 10:12:41.503 INFO \[main\] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler \["http-nio-8090"\]  
01-Sep-2022 10:12:41.557 INFO \[main\] org.apache.catalina.startup.Catalina.load Server initialization in \[871\] milliseconds  
01-Sep-2022 10:12:41.566 INFO \[main\] org.apache.catalina.core.StandardService.startInternal Starting service \[Tomcat-Standalone\]  
01-Sep-2022 10:12:41.566 INFO \[main\] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: \[Apache Tomcat/9.0.45\]  
01-Sep-2022 10:12:43.383 INFO \[Catalina-utility-2\] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.  
01-Sep-2022 10:12:43.644 INFO \[Catalina-utility-2\] org.apache.catalina.core.ApplicationContext.log 1 Spring WebApplicationInitializers detected on classpath  
log4j:ERROR Could not find value for key log4j.appender.luceneQuery  
log4j:ERROR Could not instantiate appender named "luceneQuery".  
2022-09-01 10:12:44,170 INFO \[Catalina-utility-1\] \[com.atlassian.confluence.lifecycle\] contextInitialized Starting Confluence 7.13.0 \[build 8703 based on commit hash 791df1c41ad1e432a490f9fc6f60e3ea49358bee\] - synchrony version 4.0.0-master-f680ea21  
01-Sep-2022 10:12:44.274 WARNING \[Catalina-utility-2\] org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom Creation of SecureRandom instance for session ID generation using \[SHA1PRNG\] took \[568\] milliseconds.  
10:12:44 \[Catalina-utility-2\] o.a.c.u.SessionIdGeneratorBase\[WARN\] log - Creation of SecureRandom instance for session ID generation using \[SHA1PRNG\] took \[568\] milliseconds.  
01-Sep-2022 10:12:44.460 INFO \[Catalina-utility-2\] org.apache.catalina.core.ApplicationContext.log Initializing Spring DispatcherServlet 'dispatcher'  
10:12:44 \[Catalina-utility-2\] o.a.c.c.C.\[.\[.\[/synchrony-proxy\]\[INFO\] log - Initializing Spring DispatcherServlet 'dispatcher'  
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

*** ** * ** ***

Thanks

Paul


Answers:
author: Mayur Jadhav
body: Hello [@Paul Dennis](/t5/user/viewprofilepage/user-id/3752273) ,

Hope you are doing good!!!

As you have mentioned the CPU load on the vm reaches to 100% due that Jira is unable to start, I would suggest to monitor the CPU load and if needed please increase the core.

Regards,  
Mayur


author: Paul Dennis
body: After rebooting the Vm a couple of times it started. No idea why.


Tags: confluence-server

server