You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
I am just starting with Jira so I have no much knowledge. I’m here to get some insights from you and maybe help back in the future.
Our environment was reset this morning and, after trying to bring it up, it failed 3 or 4 times.
After that, our team recovered a backup and the environment is now back up, but we would like to understand what problem was preventing Jira from starting.
Some warns I got from the logs are:
“Caesium-1-1 WARN [c.a.jira.ofbiz.IssueGenericValue] Issue (id=0) has empty field 'num'. Returning null for 'key'.“
”JIRA-Bootstrap WARN [c.a.jira.health.HealthChecks] JIRA runs in a Java virtual machine (JVM), and this JVM is allocated an amount of memory to enable JIRA to run. These amounts can be manually configured.”
”- The initial memory allocation pool (-Xms) is recommended to be at least 384m.”
This last one caught my attention because the total memory amount is below the recommended value. Is set with a total of 320. But the used amount is below that. Like 183. So I don’t know for sure.
Any insights where should I look after?
Welcome to the Atlassian Community!
These warnings really are just warnings, they're not the errors that are preventing startup.
The usual recommendation is to simply set the startup allocation to the same as the maximum heap size, as that's going to make starting up a bit faster, and as you're allocating the memory already, you might as well. But you don't need to do this.
I would want to check the memory first - what is the maximum heap size? I wouldn't try to run a Jira with less than 1Gb nowadays, and that's for a small, single user, zero addons, system for dev, test, or demonstration. For a real service, I'd start with 2Gb and be looking for 4!
If it's not the memory, then you're going to read the rest of the logs for the startup errors.