Upgrade to Jira 5.2, MySQL 5.5, and Greenhopper 6.1 leaves greenhopper unavailable

[Robert Matthews]

We are upgrading from Jira 4.3.4, MySQL 5.0.9, and Greenhopper 5.8.6 to Jira 5.2, MySQL 5.5 and the latest Greenhopper version. This is going on a sandbox server to validate prior to going to our live environment. Jira and MySQL are working; allowing login, queries, issue creation, etc. All other plugin-ins that are used have been successfully updated.

Documentation said greenhopper requires mysql 5.1 (not 5.0), so we have upgraded to the next release (v5.5) that our Systems team plans to support. The memory requirements have already been reset to more that the minimum suggested in documentation.

The Greenhopper plugin appears to correctly install, but an error message displays stating: "GreenHopper is currently unavailable. This might be because an upgrade task has failed to run or has not not yet completed."

Logs do not show any greenhopper installation or startup errors.

Suggestions?

[Robert Matthews]

Here's more details about our installation:along with mysql 5.5 we use MyISAM as well. The greenhopper plugin seems to want to use InnoDB. Any idea if this is causing the failure to create either the database tables or the custom components? The Hercules log scanner did not find anything. the 'raw' logs only show that greenhopper plugin start(ed) but no info about table creates.

[JoanneA]

Hi Robert,

I'm not aware of any known issues relating to this upgrade, but you could try a couple of things:

1. Run the Hercules Log Scanner to see if it finds information relating to a known issue - here is some more info: https://ecosystem.atlassian.net/wiki/display/STP/Hercules+Log+Scanner

2. Raise a ticket with our support team, so that they can try and fix the problem for you - here's the link to raise a ticket: https://support.atlassian.com

If you find the cause, please do post the answer back here.

Thanks