Error encountered upgrading from Jira v7.0.10 to v7.2.7

Hi everybody,

At the weekend, I attempted to upgrade our JIRA production server from Jira v7.0.10 to v7.2.7.

This failed with the below error and I was forced to abandon the procedure.

This upgrade was successfully previously attempted on our development server.

As you will see from the below dialog, the problem occurred in the installation directory backup part; this part does not seem to be optional whereas the previous home directory backup part is.

Is there a way to switch off the installation directory backup part?

What does the 'i' (ignore) option do just after the error; is this equivalent to carrying out the upgrade, but without the installation directory backup part?

Thanks,

 

 

bernard gorman

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

[root@camsvujir01 /]# ./atlassian-jira-software-7.2.7-x64.bin

Unpacking JRE ...

Starting Installer ...

 

This will install JIRA Software 7.2.7 on your computer.

OK [o, Enter], Cancel [c]

o

Choose the appropriate installation or upgrade option.

Please choose one of the following:

Express Install (use default settings) [1], Custom Install (recommended for advanced users) [2], Upgrade an existing JIRA installation [3, Enter]

3

Existing installation directory:

[/opt/jira/application]

 

Back up JIRA home directory

The upgrade process will automatically back up your JIRA installation

directory. You can also choose to back up your existing JIRA home directory.

Both directories are backed up as zip archive files in their respective

parent directory locations.

 

We strongly recommend choosing this option in the unlikely event that you

experience problems with the upgrade and may require these backups to

restore your existing JIRA installation.

 

If you have many attachments in your JIRA home directory, the zip archive of

this directory may consume a significant amount of disk space.

Back up JIRA home directory?

Yes [y, Enter], No [n]

n

 

Checking for local modifications.

Unable to check for modifications.

 

Checking if your instance of JIRA Software is running

Upgrade check list

Back up your external database

We strongly recommend you back up your JIRA Software database if you have

not already done so.

 

Please refer to the following URL for back up guidelines:

http://docs.atlassian.com/jira/jadm-docs-072/Backing+up+data

 

Check plugin compatibility

Check that your non-bundled plugins are compatible with JIRA Software 7.2.7.

 

For more information see our documentation at the following URL:

http://docs.atlassian.com/jira/jadm-docs-072/Upgrading+JIRA+applications

 

Please ensure you have read the above checklist before upgrading.

Your existing JIRA installation is about to be upgraded! Do you want to proceed?

Upgrade [u, Enter], Exit [e]

u

 

Your instance of JIRA is currently being upgraded.

Checking if JIRA has been shutdown...

Backing up the JIRA installation directory

                                                                          

An error occurred:

java.lang.NullPointerException

Error log: /install4jError6775836751308206843.log

java.lang.NullPointerException

            at com.install4j.runtime.beans.actions.files.AbstractRecursiveFileAction.recurse(Unknown Source)

            at com.install4j.runtime.beans.actions.files.AbstractRecursiveFileAction.executeForSingleFile(Unknown Source)

            at com.install4j.runtime.beans.actions.files.AbstractRecursiveFileAction.recurse(Unknown Source)

            at com.install4j.runtime.beans.actions.files.AbstractRecursiveFileAction.executeForSingleFile(Unknown Source)

            at com.install4j.runtime.beans.actions.files.AbstractRecursiveFileAction.recurse(Unknown Source)

            at com.install4j.runtime.beans.actions.files.AbstractRecursiveFileAction.executeForSingleFile(Unknown Source)

            at com.install4j.runtime.beans.actions.files.AbstractRecursiveFileAction.recurse(Unknown Source)

            at com.install4j.runtime.beans.actions.files.AbstractRecursiveFileAction.executeForSingleFile(Unknown Source)

            at com.install4j.runtime.beans.actions.files.AbstractRecursiveFileAction.executeForSingleFile(Unknown Source)

            at com.install4j.runtime.beans.actions.files.AbstractFileAction.executeForMultipleFilesAction(Unknown Source)

            at com.install4j.runtime.beans.actions.files.AbstractRecursiveFileAction.executeForMultipleFilesAction(Unknown Source)

            at com.install4j.runtime.beans.actions.files.AbstractFileAction.execute(Unknown Source)

            at com.install4j.runtime.beans.actions.files.CreateZipFileAction.execute(Unknown Source)

            at com.install4j.runtime.beans.actions.SystemInstallOrUninstallAction.install(Unknown Source)

            at com.install4j.runtime.installer.InstallerContextImpl.performActionInt(Unknown Source)

            at com.install4j.runtime.installer.ContextImpl.performAction(Unknown Source)

            at com.install4j.runtime.installer.controller.Controller.executeActions(Unknown Source)

            at com.install4j.runtime.installer.controller.Controller.handleCommand(Unknown Source)

            at com.install4j.runtime.installer.controller.Controller.start(Unknown Source)

            at com.install4j.runtime.installer.Installer.main(Unknown Source)

            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

            at java.lang.reflect.Method.invoke(Method.java:498)

            at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)

            at com.install4j.runtime.launcher.Launcher.main(Unknown Source)

com.install4j.runtime.beans.actions.files.CreateZipFileAction failed

 

Ignore [i, Enter], Quit [q]

q

Rolling back changes ...

[root@camsvujir01 /]#

2 answers

Add this to the jira-config.properties file . this will disable autobackup 

#jira.autoexport=false

#jira.upgrade.force.manual.schedule=true


Abyakta

Thanks for your reply abyakta.

I have searched for the file you mentioned in our JIRA home and installation directories but can't locate it.

Please advise of it's location.

 

bernard

 

You have to manually create it and put it in the jira-home folder

Sorry for the delay .

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Jun 14, 2018 in Jira Service Desk

How the Telegram Integration for Jira helps Sergey's team take their support efficiency to the bank

...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...

491 views 2 5
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you