We're finding the the structure derby.log file grows quickly, consuming large amounts of disk (usually around 10GB in a few days). Can the logging to this file be made less verbose?
The /db/ directory in the structure directory also grows quickly. Can any maintenance be performed within Structure to control the size of this directory?
Normally derby.log should stay very small. Extensive logging is enabled explicitly or when JIRA is in “development” mode. You can check if Structure turns on verbose logging by searching atlassian-jira.log for the line "Structure turns Derby verbose logging on” - it would happen shortly after JIRA start or Structure enablement. (You can disable / enable Structure to see if that produces this message.)
If it’s on, you can force it to be off with “-Dstructure.derby.verbose.log=false” system variable (added in setenv.sh / setenv.bat).
Another possibility is that Derby database became corrupt on your server, and derby.log contains errors. In that case, the users should also experience problems with Structure. If that seems to be the case, we'll need the ZIP of the derby.log file so we can take a look.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs