Error rendering widget after Jira upgrade 7.4 to 7.1.10

[zeramu]

Today we’ve upgraded from 7.4 to 7.10.1. We did everything as described in you upgrade manual.

After the upgrade the Issue page (like http://jira.goodcustomers.ru/browse/DEV-172) started showing Render error message «com.pyxis.greenhopper.jira:greenhopper-agile-issue-web-panel» instead of widget.

Kindly see the screenshot attached.

My setup is Linux + mysql (actually mariaDB 5.5.56).

[Andy Heinzer]

There are lots of SQL errors when starting 7.10 such as this:

2017-07-12 23:21:06,448 JIRA-Bootstrap WARN      [o.o.c.entity.jdbc.DatabaseUtil] Entity "Application" has no table in the database
2017-07-12 23:21:06,449 JIRA-Bootstrap ERROR      [o.o.c.entity.jdbc.DatabaseUtil] Could not create table "cwd_application"
2017-07-12 23:21:06,449 JIRA-Bootstrap ERROR      [o.o.c.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:
    CREATE TABLE cwd_application (ID DECIMAL(18,0) NOT NULL, application_name VARCHAR(255), lower_application_name VARCHAR(255), created_date DATETIME, updated_date DATETIME, active DECIMAL(9,0), description VARCHAR(255), application_type VARCHAR(255), credential VARCHAR(255), CONSTRAINT PK_cwd_application PRIMARY KEY (ID))
    Error was: java.sql.SQLSyntaxErrorException: Table 'cwd_application' already exists
    Query is : CREATE TABLE cwd_application (ID DECIMAL(18,0) NOT NULL, application_name VARCHAR(255), lower_application_name VARCHAR(255), created_date DATETIME, updated_date DATETIME, active DECIMAL(9,0), description VARCHAR(255), application_type VARCHAR(255), credential VARCHAR(255), CONSTRAINT PK_cwd_application PRIMARY KEY (ID))

This indicates that Jira is not able to see the tables in the database needed, but also unable to create them.   That's very strange.  However from looking at more details about your database:

Database Version   : MySQL - 5.5.52-MariaDB
Database Driver    : MariaDB connector/J - 1.4.4

MariaDB is not actually supported by Atlassian on the Supported Platforms documentation for Jira.  Because of this, I think it would be best to get your Jira data onto a supported platform, like MySQL 5.7 or Postgres 9.6 first.   I suspect the problem could be with the jdbc driver, or with the database itself, but this is difficult to know because I don't see MariaDB databases with Jira very often.   I recommend creating a new supported database version, connecting this to Jira and following the steps in Switching databases in order to get your existing data into a supported database for Jira.

If you choose a MySQL database, then please note that this database type does require you to download the 5.1.x jdbc driver into the $JIRAINSTALL/lib/ directory before Jira can connect to this kind of database.

This way we can at least eliminate your unsupported database as the cause of this problem.

[zeramu]

Hi, @Andy Heinzer,

Thanks for reply.

Migration to MySQL from MariaDB is not that easy option for me. It will take the same amount of time as migration to Youtrack which has no issue with MariaDB.

So to save my time I just made

alter table customfieldvalue add UPDATED datetime null default null;

And that has solved all the problems. Thanks.

[Andy Heinzer]

There is likely a system plugin (or module of a plugin) that is not loading correctly in your Jira site.  However I have no idea what the source cause is from just that screenshot.   I would like to take a closer look at your Jira logs from this instance in order to make a determination here.

Please create a support zip, and then if you can post that file to a service like Google Drive or Dropbox and then share the link with us here, I'd be happy to take a closer look to see if we can understand what is causing this error.

Andy

[zeramu]

Hi, @Andy Heinzer!

Thanks for willing to help me.

Here is the link https://drive.google.com/open?id=1Q7jgaBBGLR39EWEyQLW-Pp9L5hhfGzOv

I believe the reason is here:

```

2018-06-26 14:38:57,658 http-nio-8081-exec-12 WARN artem 878x802x5 odrb7 37.193.244.121,127.0.0.1 /secure/AjaxIssueAction!default.jspa [c.atlassian.ozymandias.SafePluginPointAccess] Unable to run

 plugin code because of 'com.atlassian.jira.exception.DataAccessException - org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, ISSUE, CUSTOMFIELD, UPDATED, PARENTKEY, STRINGVALUE, NUMBERVALUE, TEXTVALUE, DATEVALUE, VALUETYPE FROM customfieldvalue WHERE ISSUE=? ORDER BY UPDATED ASC, ID ASC (Unknown column 'UPDATED' in 'field list'

    Query is : SELECT ID, ISSUE, CUSTOMFIELD, UPDATED, PARENTKEY, STRINGVALUE, NUMBERVALUE, TEXTVALUE, DATEVALUE, VALUETYPE FROM customfieldvalue WHERE ISSUE=10405 ORDER BY UPDATED ASC, ID ASC)'.

2018-06-26 14:38:58,160 http-nio-8081-exec-12 ERROR artem 878x802x5 odrb7 37.193.244.121,127.0.0.1 /secure/AjaxIssueAction!default.jspa [c.a.j.web.component.ModuleWebComponentImpl] An exception occured while rendering the web panel: com.pyxis.greenhopper.jira:greenhopper-agile-issue-web-panel (null)

com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, ISSUE, CUSTOMFIELD, UPDATED, PARENTKEY, STRINGVALUE, NUMBERVALUE, TEXTVALUE, DATEVALUE, VALUETYPE FROM customfieldvalue WHERE ISSUE=? ORDER BY UPDATED ASC, ID ASC (Unknown column 'UPDATED' in 'field list'

Query is : SELECT ID, ISSUE, CUSTOMFIELD, UPDATED, PARENTKEY, STRINGVALUE, NUMBERVALUE, TEXTVALUE, DATEVALUE, VALUETYPE FROM customfieldvalue WHERE ISSUE=10405 ORDER BY UPDATED ASC, ID ASC)

```

You see there is reference to non existent column in a table.

I have a number of similar issues after upgrade, see the screenshot attached.

I made this shot after preparing the logs for you, but the  reason is the same:

```

SQL Exception while executing the following:SELECT ID, ISSUE, CUSTOMFIELD, UPDATED, PARENT

KEY, STRINGVALUE, NUMBERVALUE, TEXTVALUE, DATEVALUE, VALUETYPE FROM customfieldvalue WHERE ISSUE=? ORDER BY UPDATED ASC, ID ASC (Unknown column 'UPDATED' in 'field list'

```

Also please take a look at related issue here https://community.atlassian.com/t5/Jira-Software-questions/After-upgrade-7-4-gt-7-10-1-JIRA-fails-with-SQL-error/qaq-p/830444#M28607

Thanks for your efforts!