Errors deleteing tasks from a project

[Jason Mulreany]

Hi there,

We have recently completed an installation of Jira Core and Jira Software. Everything appears to be working correctly with the exception of one issue.

When we try to delete a subtask from one of the projects Jira throws an exception and spits out the following debug output.

I did notice several posts on a similar nature that refer to this issue after upgrades or backups. However, this is a new install so I am not completely sure if this relates to the same issue.

We are running this on an Ubuntu 18.04 LTS EC2 instance with a MySql RDS version MySQL 5.7.16

Any guidance or suggestions around correcting the error below would be greatly apreciated. 

Technical details

Log's referral number: b27aa98a-13ac-421d-87ce-7aea80350dbf

Cause

Referer URL: https://jira.genomicsmed.ie/secure/RapidBoard.jspa?rapidView=5&view=detail&selectedIssue=TEST-2

com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected exactly 2 rows; the maximum marker row and the lowest ranked row for rank field[id=10100]com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected exactly 2 rows; the maximum marker row and the lowest ranked row for rank field[id=10100]        at com.atlassian.greenhopper.manager.lexorank.LexoRankDaoImpl.getMaximumMarkerRowAndPreviousRow(LexoRankDaoImpl.java:399) [?:?] 

......

.....

.....

[Alexey Matveev]

Hello,

Kindly have a look at this KB:

https://confluence.atlassian.com/jirakb/cannot-reindex-jira-due-to-expected-exactly-2-rows-the-maximum-marker-row-and-the-lowest-ranked-row-for-rank-field-779158916.html?_ga=2.95687196.1295891213.1536040679-65270402.1526147845

[Jason Mulreany]

Hi Alexey,

I'm not sure if this relates to my install, It's a fresh install and I'm using MySql rather than MSSQL or Postgres. As this is a new install with no live data in it would it make more sense to drop the DB and allow Jira to re-create the DB with the correct tables/values?

[Alexey Matveev]

I figured out the you've got the same error. It could be connected

[Jason Mulreany]

As this was a new installation I stopped Jira dropped the database and allowed the app to re-create the database on the next startup.