Structure plug-in: derby.log and db directory disk usage

Systems Support
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 4, 2015

Hi there,

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?

Thanks!

1 answer

1 vote
Eugene Sokhransky _ALM Works_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 11, 2015

Hello,

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.

Kind regards,

Eugene

Suggest an answer

Log in or Sign up to answer