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; } } }

My Jira-8.0.1 server running in alpine was starting, but isn't any longer.

admin admin_trokdm

It isn't starting, and is providing these errors in ${JIRA_INSTALL}/logs/catalina.YYYY-MM-DD.log
NOTING NO errors precede this;

SEVERE [localhost-startStop-1] org.apache.catalina.startup.ContextConfig.configureStart Marking this application unavailable due to previous error(s)
12-Mar-2019 17:26:47.532 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more components marked the context as not correctly configured
12-Mar-2019 17:26:47.542 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [] startup failed due to previous errors

Accepted answers

admin admin_trokdm

Hi Brant,

Thanks for your response. Your response is the likely a derivative symptom, although the issue is no longer replicable;

I reviewed the contents of the server and determined that the earlier release I had initially designed my server to apply was not consistent with some un-recorded changes that occurred in the tar.gz file, and as such the delivery in question had some ulterior behaviours (inability to operate) which were unexpected. I have since re-developed my environment to suit the new installation;
For point of record, the version of tomcat was changed from 1.2.17-src to 1.2.18-src, so my delivery was no longer providing the appropriate file locations for the tomcat app.

I'm not sure how frequently 'unrecorded' changes such as this occur in the server packages, but it is a new release so this may be expected.

All comments

Brant Schroeder

Sounds like a Java issue. This could be a SQL connector or some other configuration it is causing the error. Have you made any changes recently? Have you tried starting in safe mode to make sure that it is not an app preventing startup (most likely not the issue)? https://confluence.atlassian.com/jirakb/add-on-tips-and-tricks-779168621.html

Have you submitted a support ticket to Atlassian? https://support.atlassian.com/contact/ You should include all of your JIRA logs.

Are there other items in the logs that are out of the ordinary?

admin admin_trokdm

Hi Brant,

Thanks for your response. Your response is the likely a derivative symptom, although the issue is no longer replicable;

admin admin_trokdm

I run a Linux server, not a Windows distro, so it isn't so simple as starting a server in safe-mode, and considering it is delivered in alpine, there is no more bare-bones distro that I am aware of, so it isn't another app regardless.

The logs were my primary interest in discussion, as the server's issues were discovered to be not configuring the server.xml file for the server not being imported as expected.

The server is starting as expected now in any case; there were a number of issues misconfigured server.xml and dbconfig.xml primarily.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server