Jira on Docker startup failure with lock error
The content on this page relates to platforms which are not supported by JIRA. Consequently, Atlassian can not guarantee providing any support for it. Please be aware that this material is provided for your information only and using it is done so at your own risk.
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
Jira running on Docker fails to start due to the 'jira.home' directory locking mechanism.
For non-docker environments, please see our JIRA applications are locked article.
Cause
- The docker container is killed too quickly with the 'docker stop' command.
- The docker container is shutdown forcibly.
Resolution
The '--time' parameter/flag can be passed into the 'docker stop' command to allow additional time before the container is killed.
We found a timeout of between 60-90 seconds provides the necessary time for a graceful Jira shutdown.
docker stop ContainerName --time 60
AWS ECS
ECS utilizes the StopTask API endpoint which is the equivalent of 'docker stop'. This results in a SIGTERM with a 30-second timeout, after which SIGKILL is sent and the container(s) are forcibly shutdown.
The 30-second timeout can be adjusted on the container agent with the 'ECS_CONTAINER_STOP_TIMEOUT' variable.