I hard rebooted my Ubuntu computer that was running my JIRA installation (which has been working fine for 6 months now). And I can't get JIRA to run (even if I do /etc/init.d/jira stop ; /etc/init.d/jira start). The /opt/atlassian/jira/logs/catalina.out log says:
2012-05-11 10:02:22,735 main INFO [atlassian.jira.startup.JiraStartupLogger]
___ Environment _____________________________
JIRA Build : 5.0#713-sha1:aec58e27a0d402341b1f1be2fc8c0204a0b070f6
Build Date : Wed Feb 15 00:00:00 EST 2012
JIRA Installation Type : Standalone
Application Server : Apache Tomcat/6.0.32 - Servlet API 2.5
Java Version : 1.6.0_26 - Sun Microsystems Inc.
Current Working Directory : /opt/atlassian/jira/bin
Maximum Allowable Memory : 682MB
Total Memory : 245MB
Free Memory : 182MB
Used Memory : 63MB
Memory Pool: Code Cache : Code Cache: init = 2555904(2496K) used = 1102400(1076K) committed = 2555904(2496K) max = 50331648(49152K)
Memory Pool: PS Eden Space : PS Eden Space: init = 67174400(65600K) used = 66079888(64531K) committed = 67174400(65600K) max = 246153216(240384K)
Memory Pool: PS Survivor Space : PS Survivor Space: init = 11141120(10880K) used = 0(0K) committed = 11141120(10880K) max = 11141120(10880K)
Memory Pool: PS Old Gen : PS Old Gen: init = 178978816(174784K) used = 0(0K) committed = 178978816(174784K) max = 536870912(524288K)
Memory Pool: PS Perm Gen : PS Perm Gen: init = 21757952(21248K) used = 16248392(15867K) committed = 21757952(21248K) max = 268435456(262144K)
JVM Input Arguments : -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties -XX:MaxPermSize=256m -Xms256m -Xmx768m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -XX:+PrintGCDateStamps -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/opt/atlassian/jira/endorsed -Dcatalina.base=/opt/atlassian/jira -Dcatalina.home=/opt/atlassian/jira -Djava.io.tmpdir=/opt/atlassian/jira/temp
I've seen exactly the same - you have to shut down Jira cleanly well before you reboot or HSQL gets corrupted.
You might be able to rescue the database with a little inventive hacking, but there's a good chance that even if you can get back in, you'll have lost data.
As Dieter says, HSQL is not suitable for production instances, so you should treat this as a learning experience, swap this dev/test system to PostgreSQL or MySQL and rebuild it from your production data.
I was thinking that was the issue. However I have the following questions:
* The atlassian-jira-5.0.4-x64.bin doesn't have an option to select a MySQL database, and it seems I need a working JIRA installation to get JIRA setup with MySQL as outlined in http://confluence.atlassian.com/display/JIRA/Setting+Up+a+MySQL+Database+on+Linux+for+JIRA - however I each time I do a fresh re-install - after stopping and removing the old broken HSQLDB installation - I get the same HSQLDB error - so how can I re-install a fresh copy of atlassian-jira-5.0.4-x64.bin ?
* I assume once I have JIRA 5.0.4 up and running with a MySQL database, I can import the backups from my old installation (which used HSQLDB)?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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