JIRA fails to start

[Everend Thorne]

Local version of JIRA won't start. Here is the log file

http://etshomerepair.com/link/atlassian-jira.log

Jobin suggested the db may be corrupted, since that means I've lost about a month's data, I don't want to believe that answer :)

Any other ideas?

I did notice the failing command swaps the hash marks in the command. "C:\Atlassian\Application Data/database/jiradb" - is this correct or is this why it's failing?

thanks

This is a related question to https://answers.atlassian.com/questions/24927/can-i-use-a-local-jiradb-script-to-update-ondemand-s-db

[Everend Thorne · Accepted solution]

JIRA started but didn't open my db, created another (since the filename was still changed). I opened the jiradb.script file in notepad++ and see NUL NUL NUL repeated hundreds of thousands of times in the first line. I conceed Jobin, your right, it's courupted :(

[Everend Thorne]

yea! The backup service WAS running every 12hrs and I found where it was hiding the backups. So I was able to restore from a current backup!

[Everend Thorne]

there is only one row in the file, it contains only the nulls

http://etshomerepair.com/link/jiradb.script

[Jobin Kuruvilla [Adaptavist]]

Oops. I thought you got it right! Try manually removing the NULL rows and see if it helps!

[Everend Thorne]

Jobin, thanks for the suggestion. I changed the names to jiradb1.script and jiradb1.properties The log file shows the same errors. But then I noticed a few lines above the error that it had read the dbconfig.xml for the location of the db. I checked that file and that was where it was picking up the mixed up hash marks. Swaping those didn't solve the problem but it did help me notice the URL was wrong! So I updated the dbconfig.xml file with the correct path. That fixed that error.

I do have another error now (but this one I've seen before).

[Jobin Kuruvilla [Adaptavist]]

I am guessing that you wouldn't take 'Jobin is right' as an answer ;) Anyways, the path is fine as it is just Windows path convention got messed up while printing to logs. You should get a different error if the path was wrong. Can you check by just changing the spelling on the DB? i.e rename as jiradb to jirab1 or something? I am hoping you will get a different error.