JIRA throws SQLException with Table is read only errno 165 when starting

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Server と Data Center のみ - この記事は、サーバーおよびデータセンター プラットフォームのアトラシアン製品にのみ適用されます。

問題

After starting JIRA the following error is displayed when attempting to access the application:

atlassian-jira.log に次の出力が記録される。

2015-06-08 14:53:14,682 localhost-startStop-1 ERROR      [atlassian.event.internal.AsynchronousAbleEventDispatcher] There was an exception thrown trying to dispatch event '[com.atlassian.plugin.event.events.PluginEnabledEvent@59cad9e6, SingleParameterMethodListenerInvoker{method=public void com.atlassian.webhooks.plugin.WebHookEventsProcessor.onEvent(java.lang.Object), listener=com.atlassian.webhooks.plugin.WebHookEventsProcessor@2fffef24}]' from the invoker 'java.lang.RuntimeException: Generic Entity Exception occurred in deleteByAnd (SQL Exception while executing the following:DELETE FROM propertytext WHERE ID=? (Can't lock file (errno: 165 "Table is read only")))'

診断

環境

  • JIRA is connected to a MySQL database server

診断ステップ

  • Any specific steps necessary to reproduce the issue that will ensure that the customer is actually experiencing the same problem as the one that that is being described. 
  • Steps like these will often involve checking data using SQL SELECT queries to see if the application is in a particular state OR any checks to ensure that the customers environment is in a state that will bring about the described problem

This section is optional, especially if the problem is triggered regardless of the environment and diagnosis

原因

Corrupted InnoDB tables due to unknown reasons. 

ソリューション

Edit the MySQL option file (eg. /etc/my.cnf) to include the innodb_force_recovery option.

(info) See MySQL documentation for details on what values to use when setting this option: Forcing InnoDB Recovery

Last modified on Mar 30, 2016

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.