Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrading 4.2 -> 4.4 not going smoothly

Everend Thorne November 13, 2011

I am trying to move JIRA to another harddrive and found documentation on doing this during an upgrade.

http://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server

I've tried the install 2-3 times now and each time I get stuck trying to get the server to start (section 3.5 in doc link above). The new instance fails to start:

JIRA Startup Failed - You cannot access JIRA at present. Look at the table below to identify the reasons

Description - The following plugins are required by JIRA, but have not been started:

Gadget Directory Plugin (com.atlassian.gadgets.directory)

Embedded Gadgets Plugin (com.atlassian.gadgets.embedded)

Gadget Dashboard Plugin (com.atlassian.gadgets.dashboard)

Atlassian JIRA - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets)

The only plugin's that I have added to the 4.2 install is the JEMH email handler, I haven't figured out what these other plugin's are.

These failures are directly related to pointing to a copy of the 4.2v home directory. If I do the 4.4 install and point to a blank folder to use as the home directory, the install happens correctly but then I'd have to do a lot of setup trying to recreate the existing data.

I'm done messing with this tonight, perhaps I'll figure it out this week. In the mean time, if anyone recognizes what's going on here and has a direction to point me in, I thank you.

3 answers

2 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 13, 2011

Those plugins are all core system ones, they are off-the-shelf.

I don't know what you've got in your 4.2 home directory that may be causing the problem, but you could spend weeks trying to work it out. The best route for your upgrade is to use an empty 4.4 home directory, but copy some of the 4.2 data across. The only thing you really need is the 4.2 attachments, everything else is actually in the database.

Jira will be able to re-create the index from scratch, so you can loose that.

You should look into plugins/installed plugins to find out what version 2 plugins you've added.

My best guess is that there's a version 1 plugin that's failing - they live in <your jira>\WEB-INF\lib and because they're mixed into the main install, they're a bit of a pain to identify (I always cheat - there's an edit-webapp directory in source control whereever I go, so I always know what I've added to a Jira). But you're going to need to check the versions of them for compatibility and probably upgrade them anyway. You'll probably find it a lot more simple to start "clean", but with some missing plugins and add them back as your testing finds them.

Everend Thorne November 13, 2011

The most recient install I did to an empty home directory, I went through much of the setup and then copied/merged the 4.2 home directory into the new 4.4 home dir. Only copying the files that were new, any conflicts in the copying I skipped. So this morning after reading Nic's post I started looking through the new merged home dir to see what was actually copied. I found a directory /plugins/.osgi-plugins with three folders in it. felix, framework-bundles and transformed-plugins. I deleted these three folders and restarted 4.4 service. Now it all seems to work! I'm working on upgrading JEMH now.

thanks

Everend

0 votes
Everend Thorne January 31, 2012

This JIRA Startup Failed message continues to plague me. I have been able to start JIRA but it takes several attempts each time. And regardless of how or why I need to restart JIRA (W7 crash/power loss/Win update) I get this same message the first 2-3-4 times I attempt to start JIRA. I created a batch script to Stop the Atlassian service, remove the lock file, erase the \Atlassian\Application Data\plugins\.osgi-plugins directory and the another script to start the service. After the 3-4 time through this process of the stop.bat and the start.bat JIRA will come up. The other times I get the Failed message above.

In Nov I tried the install a few times before I got this far but I haven't tried to reinstall since then. I'm saving for a new motherboard/memory/CPU for this machine, I hope to upgrade the hardware in the next month or two and will reinstall then. But since it will be a few weeks and this is happening 1-2 times per week I'm getting frustrated so I hope someone will see this and know how to solve it.

thanks

Everend

0 votes
Everend Thorne November 13, 2011

Well Actually it did startup once. I shut JIRA down to install the JEMH plugin and starting it up again takes me back to the same original problem. I checked permissions on the .osgi-plugins folder, it looks good w/

Authenticated Users - full control

SYSTEM - full control

Administrators - full control

Users - limited control

I then changed all these to full control and deleted the contents of the folder again and JIRA started again.

I stopped JIRA and restarted and get the following (similar) failure. It's pretty consistant. IF I clear out the .osgi-plugin's folder before restarting JIRA it works. If I don't delete the contents of this folder I get the following failure.

JIRA Startup Failed

You cannot access JIRA at present. Look at the table below to identify the reasons

The following plugins are required by JIRA, but have not been started:

  • Embedded Gadgets Plugin (com.atlassian.gadgets.embedded)
  • Gadget Dashboard Plugin (com.atlassian.gadgets.dashboard)
  • Atlassian JIRA - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events