nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Confluence 7.13.7 is down and cannot be restarted

EWM IT Support

]$ tail catalina.out
18:03:32 [Catalina-utility-2] o.a.c.c.C.[.[.[/synchrony-proxy][INFO] log - Initializing Spring DispatcherServlet 'dispatcher'
log4j:ERROR Could not find value for key log4j.appender.luceneQuery
log4j:ERROR Could not instantiate appender named "luceneQuery".
2023-11-15 18:03:34,920 INFO [Catalina-utility-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 7.13.7 [build 8703 based on commit hash b4077df4ef5cfb3a30780e1c3966e69e95e5156b] - synchrony version 4.1.0
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.

Accepted answers

Shawn Doyle - ReleaseTEAM

It doesn't look like this error is what is stopping Confluence from starting.

From this report, these errors can safely be ignored if not using Lucense logging.

https://jira.atlassian.com/browse/CONFSERVER-74303

"The above error comes from the log4j configuration that is related to Lucene query logging. It is safe to ignore this error unless Lucene query logging is needed."

To turn on and off the logging, read the following.

https://confluence.atlassian.com/adminjiraserver/logging-and-profiling-938847671.html

All comments

Shawn Doyle - ReleaseTEAM

It doesn't look like this error is what is stopping Confluence from starting.

From this report, these errors can safely be ignored if not using Lucense logging.

https://jira.atlassian.com/browse/CONFSERVER-74303

"The above error comes from the log4j configuration that is related to Lucene query logging. It is safe to ignore this error unless Lucene query logging is needed."

To turn on and off the logging, read the following.

https://confluence.atlassian.com/adminjiraserver/logging-and-profiling-938847671.html

EWM IT Support

Hi Shawn, thanks so much for your response. At least we can rule out that. Have you ever encountered a situation where you could not get Confluence to start?

Shawn Doyle - ReleaseTEAM

Yes I have. It's usually something like, out of disk space, some dependency changing, or permissions-related issues.

Can you expand on how you run Confluence? which OS, via a container, etc?

Also, have you tried starting it from a command line and see if there are any errors/warnings? Maybe explain what troubleshooting steps you have taken so far.

EWM IT Support

Hi Shawn, I do apologize for not having a lot of information for you. I don't ordinarily work on this. Below is the system information.
Icon name: computer-vm
Chassis: vm

Virtualization: kvm
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 5.16.3-x86_64-linode152
Architecture: x86-64

Is the latest version of Confluence compatible. Would backing up our data then re-installing Confluence be ok?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

server

confluence-server