JIRA startup failed, JIRA has been locked

ruudgong April 29, 2017

Jira instance is unable to start and log show the error below.

 


[jira@optimus ~]$ tail -f /data/servers/jira-5.2.11/logs/catalina.out
---------------------------------------------------------------------------------
2017-04-29 20:48:44,855 localhost-startStop-1 WARN [c.a.j.config.properties.ApplicationPropertiesStore] Exception getting property 'jira.trustedapps.user.name.transformation.policy.class' from database. Using default
2017-04-29 20:48:44,955 localhost-startStop-1 ERROR [c.a.j.web.dispatcher.JiraWebworkActionDispatcher]

******************************************
JIRA startup failed, JIRA has been locked.
******************************************

29-Apr-2017 20:48:44.988 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
29-Apr-2017 20:48:44.995 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 5327 ms

 

[jira@optmimus ~]$ locate  .jira-home.lock
/var/content/optimus/should_be_able_to_delete-jiraHome/.jira-home.lock

 

[jira@optimus ~]$ rm  .jira-home.lock

 

[jira@optimus ~]$ /data/servers/jira-5.2.11/bin/startup.sh

 

 

I have completed all the steps indicated below, yet my JIRA Instance won't start. I have also read through this document on the URL below but not helpful pointers.

https://confluence.atlassian.com/jirakb/troubleshooting-jira-startup-failed-error-394464512.html 

 

3 answers

0 votes
Bhimsen Rao October 14, 2019

Both installation and data directory needs to be owned by Jira user.

0 votes
Dennis Guse April 30, 2017

To me it looks like the jira user used to run the application has no write credentials on the jira home directory. Are you using a special startup script ? Probably you have the wrong user in there? In a jira standard installation the user is supposed to be jira ,just check for the correct user you would like to have the jira application running and do a chown a+x jirauser /var/atlassian/application-data/jira

ruudgong May 1, 2017

I have completed the steps below and the issues aren't resolved. Btw, Jira is the user running Jira. 

 

[root@optimus]$ ls -ld /var/atlassian/application-data/jira-5.2.11
drwx--x--x 11 jira jira 4096 May 1 10:43 /var/atlassian/application-data/jira-5.2.11

ruudgong May 1, 2017

Additional information

[root@optimus ~]$ uptime
11:23:42 up 12 min, 1 user, load average: 0.00, 0.08, 0.05
[root@optimus ~]$

 

 

Server startup logs are located in /data/servers/jira-5.2.11/logs/catalina.out
Using CATALINA_BASE: /data/servers/jira-5.2.11
Using CATALINA_HOME: /data/servers/jira-5.2.11
Using CATALINA_TMPDIR: /data/servers/jira-5.2.11/temp
Using JRE_HOME: /data/servers/jira-5.2.11/jre/
Using CLASSPATH: /data/servers/jira-5.2.11/bin/bootstrap.jar:/data/servers/jira-5.2.11/bin/tomcat-juli.jar
Using CATALINA_PID: /data/servers/jira-5.2.11/work/catalina.pid
Existing PID file found during start.
Removing/clearing stale PID file.
Tomcat started.

 

 

[jira@optimus ~]$ tail -f /data/servers/jira-5.2.11/logs/catalina.out
---------------------------------------------------------------------------------
2017-05-01 11:18:08,575 localhost-startStop-1 WARN [c.a.j.config.properties.ApplicationPropertiesStore] Exception getting property 'jira.trustedapps.user.name.transformation.policy.class' from database. Using default
2017-05-01 11:18:08,986 localhost-startStop-1 ERROR [c.a.j.web.dispatcher.JiraWebworkActionDispatcher]

******************************************
JIRA startup failed, JIRA has been locked.
******************************************

01-May-2017 11:18:09.106 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
01-May-2017 11:18:09.130 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 33876 ms

 

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 29, 2017

There's not enough here to diagnose the problem.

If I were doing this, I would drop back on brute force.  Reboot the server to get a clean run.  If JIRA is set up to start on boot, and tries to, great, what does the log say after the startup?  If it's not set up for automatic start, that's also fine, but what does the log say when you try the startup script?

ruudgong April 30, 2017

I have rebooted the server yet it won't start. 

 

 

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 30, 2017

And the rest of the questions I asked?

ruudgong April 30, 2017

log.JPG

ruudgong April 30, 2017

@NIC 

I tried to send the log output in the comment but it wont let me

ruudgong April 30, 2017

I have done these and verified the ownership and permission of the files.

[jira@optimus ~]$ ls -ld /var/atlassian/application-data/jira/
drwx------ 13 jira jira 4096 Apr 29 16:25 /var/atlassian/application-data/jira/

 

[jira@optimus ~]$ ls -ld /var/atlassian/application-data/jira/*
drwx------ 2 jira jira 4096 Dec 22 2015 /var/atlassian/application-data/jira/analytics-logs
drwx------ 4 jira jira 4096 Dec 13 2015 /var/atlassian/application-data/jira/caches
drwx------ 3 jira jira 4096 Dec 13 2015 /var/atlassian/application-

 

 

[jira@optimus ~]$ find /var/atlassian/application-data/jira/ -exec ls -ld \{\} \; | awk '{print $3, $4, $9}'
jira jira /var/atlassian/application-data/jira/
jira jira /var/atlassian/application-data/jira/plugins
jira jira /var/atlassian/application-data/jira/plugins/install-app-info
jira jira /var/atlassian/application-data/jira/plugins/install-app-info/jira-software-application.properties

 

 

ruudgong April 30, 2017

[jira@optimus ~]$ tail -100 /data/servers/jira-5.2.11/logs/catalina.out

JIRA has no permission to either create or write to subdirectory 'data/attachments' of jira.home '/var/atlassian/application-data/jira'.
****************************************************************************************************************************************

2017-04-30 10:26:55,042 localhost-startStop-1 INFO [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks.
2017-04-30 10:26:55,043 localhost-startStop-1 FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. JIRA will be locked.
2017-04-30 10:26:55,081 localhost-startStop-1 INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml
2017-04-30 10:26:55,173 localhost-startStop-1 INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 111 MiB. Committed: 3680 MiB. Max: 3680 MiB
Non-heap memory : Used: 34 MiB. Committed: 35 MiB. Max: 1264 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 145 MiB. Committed: 3715 MiB. Max: 4944 MiB
---------------------------------------------------------------------------------
2017-04-30 10:26:55,383 localhost-startStop-1 WARN [c.a.j.config.properties.ApplicationPropertiesStore] Exception getting property 'jira.trustedapps.user.name.transformation.policy.class' from database. Using default
2017-04-30 10:26:55,474 localhost-startStop-1 ERROR [c.a.j.web.dispatcher.JiraWebworkActionDispatcher]

******************************************
JIRA startup failed, JIRA has been locked.
******************************************

30-Apr-2017 10:26:55.501 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
30-Apr-2017 10:26:55.507 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 4994 ms
30-Apr-2017 10:32:05.913 INFO [main] org.apache.catalina.core.StandardServer.await A valid shutdown command was received via the shutdown port. Stopping the Server

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 30, 2017

You say you've checked the permissions and ownership, but are you sure the user running JIRA is correct?

ruudgong May 1, 2017

yes, the user is verified. 

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 4, 2017

Ok, so the user is jira, the data directory is owned by jira and the owner permissions are rwx, which is correct.

My next guesses are:

1.  SELinux is interfering with file access

2.  Your attachment directory is a remotely mounted file system (NFS or something, so you can store attachments on shared disks to allow for backups or fail-over).  It is possible to have a directory that locally looks accessible, but the permissions on the remote side actually block it.

Suggest an answer

Log in or Sign up to answer