We startup our machine every morning. It is a Linux host running Confluence 7.2
Some mornings, the confluence process is not running. It appears to have crashed (ps -ef | grep java --- shows no process). There is no sign in any log files of why this is or what has happened to the java JVM process. We can see from standard log files that the process is starting up to the point of:
catalina.out
24-Apr-2020 06:46:35.445 INFO [Catalina-utility-2] org.apache.catalina.core.ApplicationContext.log Initializing Spring DispatcherServlet 'dispatcher'
2020-04-24 06:46:36,787 INFO [Catalina-utility-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 7.2.0 [build 8401 based on commit hash 912a577971fe711d4a876d9130277d03b009a0bf] - synchrony version 3.1.0-master-0f086db5
There are no further logs. The process is not running.
Restarting confluence always works first time.
Why is this happening? Any pointers of how to debug this?
Thank you
Could the Confluence process be started too early? Maybe certain system processes (network, database ...) are not yet 100% up and running?
What is used systemd or init.d
Hi,
Thank you for the response.
This is something we are investigating. We are fairly certain it is coming up okay. However, we do use the network DHCP which may be causing an issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.