JIRA Throws an Exception due to MySQL Error 30
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Symptoms
The following error appears in the logs when starting JIRA:
1
2
3
4
5
6
7
8
Fcom.atlassian.jira.exception.DataAccessException: java.sql.SQLException:
Can't create/write to file '/tmp/#sql_7400_0.MYI' (Errcode: 30)
at com.atlassian.jira.upgrade.util.UpgradeUtils.getExactColumnName(UpgradeUtils.java:180)
at com.atlassian.jira.upgrade.util.UpgradeUtils.getJIRABuildVersionNumber(UpgradeUtils.java:258)
at com.atlassian.jira.appconsistency.db.MinimumUpgradableVersionCheck.getDbBuildNumber(MinimumUpgradableVersionCheck.java:81)
...
Caused by: java.sql.SQLException: Can't create/write to file '/tmp/#sql_7400_0.MYI' (Errcode: 30)
...Cause
The above error indicates that the MySQL database unable to write to the /tmp directory due to either one of the following reason:
The /tmp partition has run out of space and the file can't be created,
The mysqld process cannot write to that directory because of permission problems.
Any operation that requites a "temp file" will go into the /tmp directory by default. The name you're seeing is just some internal random name.
Resolution
Increase the amount of the /tmp directory
Clear the content of the /tmp directory
Was this helpful?