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

Jira Installation failed - EKS cluster - container start and stop exit code =1 and Permision Denied

Ranendra Das_7cu9gb

Hello,

I am trying to install Jra 10.3.3 in eks using cdk deploy.

I am facing this error-

Container start and stop with

Last State: Terminated

Reason: Error

Exit Code: 1

And when I look at pod log file, I see this error

[0.000s][error][logging] Error opening log file '/opt/atlassian/jira/logs/atlassian-jira-gc-2025-05-15_16-14-52.log': Permission denied

[0.001s][error][logging] Initialization of output 'file=/opt/atlassian/jira/logs/atlassian-jira-gc-%t.log' using options 'filecount=5,filesize=20M' failed.

Invalid -Xlog option '-Xlog:gc*:file=/opt/atlassian/jira/logs/atlassian-jira-gc-%t.log:tags,time,uptime,level:filecount=5,filesize=20M', see error log for details.

Error: Could not create the Java Virtual Machine.

Error: A fatal exception has occurred. Program will exit.

Can someone tell me where am I wrong, I to debug and fix this issue?

Accepted answers

Jeroen Poismans

Hi and welcome to the Atlassian community!

This typically has to do with folder permissions. What it looks like to me is that the user stating the Jira application does not have permission or insufficient on the /opt/atlassian folder.

Make sure that this user is owner of the folder and its subfolders.

There is a KB article about it here:
https://support.atlassian.com/jira/kb/fix-directory-and-file-permissions-in-linux-for-jira-server-or-data-center/

Hope this helps!

All comments

Jeroen Poismans

Hi and welcome to the Atlassian community!

This typically has to do with folder permissions. What it looks like to me is that the user stating the Jira application does not have permission or insufficient on the /opt/atlassian folder.

Make sure that this user is owner of the folder and its subfolders.

There is a KB article about it here:
https://support.atlassian.com/jira/kb/fix-directory-and-file-permissions-in-linux-for-jira-server-or-data-center/

Hope this helps!

Ranendra Das_7cu9gb

Thanks for the reply.

Here is the issue how it's resolved, during cdk deploy - JIRA creates different folder like cache, log etc. Jira changes the user from 'root' to 'jira'(jira is my user). But in log folder it does not changed the root user and pod gets permission denied error and bcoz of that eks container start and stop immediately . To resolve it - I did delay the container stop and then went inside container and change log folder user from root to jira. Now pod is not getting permission denied error and container starts exit code = 0. All good.

Thanks

Ranendra Das_7cu9gb

I have another issue now, can someone answer this one please.

I am upgrading JIRA from 9.12 to 10.3.3 in AWS environment(EKS).

I get this error

2025-05-20 12:37:40,302+0000 main INFO [c.a.jira.startup.TemporaryDirectoryCleaner] Cleaning the temporary directory located at /opt/atlassian/jira/temp

2025-05-20 12:37:40,305+0000 main INFO [c.a.jira.startup.TemporaryDirectoryCleaner] Finished cleaning the temporary directory.

2025-05-20 12:37:40,679+0000 main INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml

2025-05-20 12:37:40,750+0000 main INFO [c.a.j.config.database.DatabaseConfigHandler] Trying to get encrypted password from xml and decrypt it

2025-05-20 12:37:40,752+0000 main INFO [c.a.j.config.database.DatabaseConfigHandler] Database password decryption not performed.

2025-05-20 12:37:41,545+0000 main INFO [c.a.jira.startup.JiraStartupLogger] Running Jira startup checks.

2025-05-20 12:37:41,546+0000 main FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. Jira will be locked.

2025-05-20 12:37:41,645+0000 main INFO [c.a.jira.startup.LauncherContextListener] Startup is complete. Jira is ready to serve.

2025-05-20 12:37:41,649+0000 main INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:

And I see this in dbconfig.xml

<password>{ATL_SECURED}</password>

In our prod environment, I dont see password secured- I see the proper password in the dbconfig.xml- not ATL_SECURED - is this the reason, I am getting fatal error. I can login to DB using user name/password, I can run the Select 1 query, jdk - I have is 17+, so I should be okay.

Let me know the answer.

Thanks

Welcome!

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

Quick Links

Find more posts tagged with

jira

data-center