JIRA entered startup mode after defragment and reboot

Isaac_Kramer

JIRA is in startup mode after I used the windows disk cleanup utility, defragmented the host it runs on, and rebooted. Previous to that the host had run out of space and was generating errors like  "com.atlassian.jira.index.IndexingFailureException: Indexing completed with 1 errors" when a change was made.

The dbconfig.xml file seems to be missing and JIRA was using the default h2db so I think I need to regenerate that file and connect to it, but I can't find instructions on how to that.

Isaac_Kramer

Found a copy of someone else's and that fixed it. It should really be in the documentation somewhere though.

<?xml version="1.0" encoding="UTF-8"?>

<jira-database-config>
<name>defaultDS</name>
<delegator-name>default</delegator-name>
<database-type>h2</database-type>
<schema-name>PUBLIC</schema-name>
<jdbc-datasource>
<url>jdbc:h2:file:C:\Program Files\Atlassian\Application Data\JIRA/database/h2db</url>
<driver-class>org.h2.Driver</driver-class>
<username>sa</username>
<password></password>
<pool-min-size>20</pool-min-size>
<pool-max-size>20</pool-max-size>
<pool-max-wait>30000</pool-max-wait>
<min-evictable-idle-time-millis>4000</min-evictable-idle-time-millis>
<time-between-eviction-runs-millis>5000</time-between-eviction-runs-millis>
<pool-max-idle>20</pool-max-idle>
<pool-remove-abandoned>true</pool-remove-abandoned>
<pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout>
</jdbc-datasource>
</jira-database-config>