After upgrading Jira to 5.1.2, Greenhopper fails + Plugin search fails + many errors in jira240711185949-stdout.2012-08-16.log

Mehmet Bayraktar August 15, 2012

Hello,

Jira screen shows on top the following:

GreenHopper is currently unavailable. This might be because an upgrade task has failed to run or has not not yet completed.

Please contact your system administrator if you continue to see this message.

Plugin search fails to find plugins (so that I can reinstall, eg SVN, Greenhoppers, etc)

Some errors from jira240711185949-stdout.2012-08-16.log:

2012-08-16 15:50:10,760 main ERROR core.entity.jdbc.DatabaseUtil WARNING: Column ID of table dbo.jiraaction of entity Action is of type NUMERİC in the database, but is defined as type NUMERIC in the entity definition.

2012-08-16 15:50:10,760 main ERROR core.entity.jdbc.DatabaseUtil WARNING: Column İSSUEİD of table dbo.jiraaction of entity Action is of type NUMERİC in the database, but is defined as type NUMERIC in the entity definition.

2012-08-16 15:50:10,760 main ERROR core.entity.jdbc.DatabaseUtil WARNING: Column ROLELEVEL of table dbo.jiraaction of entity Action is of type NUMERİC in the database, but is defined as type NUMERIC in the entity definition.

2012-08-16 15:50:10,760 main ERROR core.entity.jdbc.DatabaseUtil WARNING: Column CREATED of table dbo.jiraaction of entity Action is of type DATETİME in the database, but is defined as type DATETIME in the entity definition.

2012-08-16 15:50:10,760 main ERROR core.entity.jdbc.DatabaseUtil WARNING: Column UPDATED of table dbo.jiraaction of entity Action is of type DATETİME in the database, but is defined as type DATETIME in the entity definition.

2012-08-16 15:50:10,760 main ERROR core.entity.jdbc.DatabaseUtil WARNING: Column ACTİONNUM of table dbo.jiraaction of entity Action is of type NUMERİC in the database, but is defined as type NUMERIC in the entity definition.

2012-08-16 15:50:10,760 main ERROR core.entity.jdbc.DatabaseUtil WARNING: Column ID of table dbo.cwd_application of entity Application is of type NUMERİC in the database, but is defined as type NUMERIC in the entity definition.

2012-08-16 15:50:10,760 main ERROR core.entity.jdbc.DatabaseUtil WARNING: Column CREATED_DATE of table dbo.cwd_application of entity Application is of type DATETİME in the database, but is defined as type DATETIME in the entity definition.

2012-08-16 15:50:10,760 main ERROR core.entity.jdbc.DatabaseUtil WARNING: Column UPDATED_DATE of table dbo.cwd_application of entity Application is of type DATETİME in the database, but is defined as type DATETIME in the entity definition.

2012

2012-08-16 15:51:33,443 main INFO com.atlassian.greenhopper.upgrade Starting upgrade task (buildNumber=12) : Migrate labs ranking data to multi-rank-field implementation

2012-08-16 15:51:35,017 main ERROR sal.core.upgrade.PluginUpgrader Upgrade failed: Attempting to migrate data from Labs ranking table to new ranking table, but new table already contains data.

com.atlassian.greenhopper.upgrade.UpgradeException: Attempting to migrate data from Labs ranking table to new ranking table, but new table already contains data.

at com.atlassian.greenhopper.upgrade.GhUpgradeTask012Dao.migrate(GhUpgradeTask012Dao.java:30)

at com.atlassian.greenhopper.upgrade.GhUpgradeTask012.performUpgrade(GhUpgradeTask012.java:35)

at com.atlassian.greenhopper.upgrade.AbstractGhUpgradeTask.doUpgrade(AbstractGhUpgradeTask.java:50)

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

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

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

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

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)

at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:58)

at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:62)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)

at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)

at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)

at org.springframework.osgi.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:56)

...

3 answers

1 accepted

0 votes
Answer accepted
Mehmet Bayraktar July 18, 2013

Hi,

We will upgrade Jira from v5.1.7 to the newest version, next month.

And we will see if Greenhopper on that.

Regards,

Mehmet

0 votes
pschaff01
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.
July 3, 2013

Hi there,

This problem is possibly related to this KB:

https://confluence.atlassian.com/display/GHKB/GreenHopper+Upgrade+Fails+with+a+NullPointerException

Could you please verify if this is the case and check if this helps?

Regards

Pietro Schaff

0 votes
Foong
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 15, 2012
2012-08-16 15:51:35,017 main ERROR sal.core.upgrade.PluginUpgrader Upgrade failed: Attempting to migrate data from Labs ranking table to new ranking table, but new table already contains data.

That error usually happen due to importing XML backup for multiple times in the same database.

Redo the upgrade with an empty database and the old XML backup will solve those errors

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events