Hi there, we are trying to do a local restore of a backup we made with our On-Demand instance of Jira.
We get this error:
This is the version we are using locally (latest as far as we know): v5.1.4#783-sha1:a7d8d2c
Can someone help please?
If you are importing by project, what does your pre-import report tell you?
If you are restoring a full backup make sure specified where to get the attachments from and where to write the attachments to. Also check that the write area is writable by Jira.
So, I rebooted the server and now it's really bad. I get this upgrade error:
You cannot access JIRA at present.
Failed to start due to your data being too old to be able to be upgraded by this version of JIRA.
Database version is: 60
Minimum version required is: 4.0-#466
You are running: 5.1.4#783-sha1:a7d8d2c5c246cbbb4ffca1b8350df93f9d8a2b57
For information on how to upgrade your data, please see our documentation.
|An error occurred performing JIRA upgrade||2012-09-13 11:34:18||error||
Exception thrown during upgrade: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:FieldScreen][id,1][description,Allows to update all system fields.][name,Default Screen] (SQL Exception while executing the following:INSERT INTO public.fieldscreen (ID, NAME, DESCRIPTION) VALUES (?, ?, ?) (ERROR: duplicate key value violates unique constraint "pk_fieldscreen" Detail: Key (id)=(1) already exists.)) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:FieldScreen][id,1][description,Allows to update all system fields.][name,Default Screen] (SQL Exception while executing the following:INSERT INTO public.fieldscreen (ID, NAME, DESCRIPTION) VALUES (?, ?, ?) (ERROR: duplicate key value violates unique constraint "pk_fieldscreen" Detail: Key (id)=(1) already exists.)) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:379) at com.atlassian.jira.issue.fields.screen.DefaultFieldScreenStore.createFieldScreen(DefaultFieldScreenStore.java:72) at com.atlassian.jira.issue.fields.screen.CachingFieldScreenStore.createFieldScreen(CachingFieldScreenStore.java:70) at com.atlassian.jira.issue.fields.screen.DefaultFieldScreenManager.createFieldScreen(DefaultFieldScreenManager.java:62) at com.atlassian.jira.issue.fields.screen.FieldScreenImpl.store(FieldScreenImpl.j
Here is what I see. First, if you followed the post in the answer you should be running a Jira 5.2-m4 version but you are still running your original Jira version of 5.1. So I am guessing you have a 5.2 database being accessed by Jira 5.1.
You are probably getting duplicate keys due to this mixture.
So get yourself running again on the 5.2 release with a clean install and database and try importing your data checking the logs to see why your attachments did not load up.
You were right. For some reason, I managed to skip reading over the first article you posted (https://confluence.atlassian.com/display/ONDEMANDKB/JIRA+OnDemand+export+does+not+import+into+standalone+JIRA ). EAP relase worked pretty good. I still had to manually copy the attachments and avatars. I almost have everything working now. I am now struggling with the System Admin's password. Thanks for all your help, this has not been easy.
All I see in the log is this:
2012-09-14 14:17:28,101 INFO [http-8090-4] [confluence.security.login.DefaultLoginManager] recordLoginFailure Failed login attempt for user 'sysadmin': Request URL: http://developers.intelli-focus.com/confluence/dologin.action User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_1) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1 Remote Address: 127.0.0.1
I've followed the https://confluence.atlassian.com/display/DOC/Restoring+Passwords+To+Recover+Admin+User+Rights and none of the options work.
So, I ran into an article that talks about how this should be done before the backup is restored.
Norman, can you help with this please? I kinda feel like doing everything from scratch again anyway. For the 6th time...
I found my answer. As far as I can figure it out, this has to be done as soon as you restore. So, your first log in. Change the password once you are in. And don't forget it :) before you config your email server settings.<h6>To log in for the first time after the import:</h6>
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
...there's anything I've learnt from working, it's that people are lazy! No offense to anyone reading this, but it's true and we can all admit it. The easier you make something for someone, the more...
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