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

the jira.home directory is locked by another running instance of jira

Kalyan Kumar Das

Hi ,

I am getting these error at the time of stating jira.

May you please recommend that how to check whether another running instance of jira is running or not on ubuntu server. I am stucked on this.

Please suggest on same. I am using jira 8.2.3 that is on ubuntu os.

Accepted answers

All comments

Nic Brough -Adaptavist-

Not the "best" way to do it, but a simple "show me what (processes) you got" will do.

Try

ps -ef

which will give you a moderate amount of information on everything that is running on the machine. To narrow it down to Jira so you don't have to plough through all processes, try

ps -ef | grep -i jira

It will list all the instances currently running, and tell you where they are being run from.

Kalyan Kumar Das

hi @Nic Brough -Adaptavist- :,

i getting these output while executing the ps -ef | grep -i jira command:

avahi 1116 1 0 15:33 ? 00:00:00 avahi-daemon: running [jiratests rv.local]
jiratest 2997 1 0 15:34 ? 00:00:00 /lib/systemd/systemd --user
jiratest 3000 2997 0 15:34 ? 00:00:00 (sd-pam)
root 3079 1 0 15:34 ? 00:00:00 /sbin/runuser -m jira -c ./catal ina.sh run
jira 3080 3079 69 15:34 ? 00:03:23 /opt/atlassian/jira/jre//bin/java -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties -D java.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms384m -Xmx2048m -XX:InitialCodeCacheSize=32m -XX:ReservedCodeCacheSize=512m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory -XX:-OmitStackTraceInFastThrow -Djava.locale.providers=COMPAT -Datlassian.plugins.startup.options=-fg -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -D org.apache.catalina.security.SecurityListener.UMASK=0027 -Xloggc:/opt/atlassianjira/logs/atlassian-jira-gc-%t.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=20M -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintGCCause -Dignore.endorsed.dirs= -classpath /opt/atlassian/jira/bin/bootstrap.jar:/opt/atlassian/jira/bin/tomcat-juli.jar -Dcatalina.base=/opt/atlassian/jira -Dcatalina.home=/opt/atlassian/jira -Djava.io.tmpdir=/opt/atlassian/jira/temp org.apache.catalina.startup.Bootstrap start
root 3500 2108 0 15:38 ? 00:00:00 sshd: jiratest [priv]
jiratest 3518 3500 0 15:38 ? 00:00:00 sshd: jiratest@pts/1
jiratest 3531 3518 0 15:38 pts/1 00:00:00 -bash
jiratest 3553 3531 0 15:39 pts/1 00:00:00 ps -ef
jiratest 3554 3531 0 15:39 pts/1 00:00:00 grep --color=auto -i jira

As i m so not familiar with server side. That's why need your suggestion.

I had also performed the operation like delete .lockfile inside jira home directory and also deleted the osgi-plugins and bundled-plugins but not yet started the jira.

Please suggest on same.

Nic Brough -Adaptavist-

Right, so you are running one already.

You should not be trying to start another one as well, just use the running one.

For a completely clean start, shut the running one down, check it has stopped with ps again, and then start it.

Kalyan Kumar Das

@Nic Brough -Adaptavist- request you to explain these point in a better way:

For a completely clean start, shut the running one down, check it has stopped with ps again, and then start it.

Patrice E.

After hours of search.. i've just found a .jira-home.lock file owned by root in the jira home folder.. Probably there because of a failed test (normally our jira instance is launched by a dedicated jira user)

After removing the file.. works perfectly like a charm again

Kalyan Kumar Das

@Patrice E. : Thank you for sharring the answer. But in my case all port and service is blocked by server team. That's the reason jira is not running on localhost also.

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-software

jira-software-server