Strange errors in JIRA

I have found that I am getting all kinds of random errors in JIRA.

  • data exception errors
  • users who randomly get 500 errors when trying to log into JIRA
  • Module errors on every ticket in a single project

All of these errors fix themselves within 1 -2 hours if you don't do anything.   I have found that the quick fix is to do a background index or do some database integrity check.

I have sent logs to Atlassian and have opened may cases but Atlassian says that there is no issue with the queries or the database from what they can tell.    They suggest I look at the proxy settings.   Which seem to be fine.

I have removed and added back plugins as well, but with no fix.   I am running on version 6.3.8.    I can't upgrade right now.

The only way to have a normal business day is to run a background index every 2 hours.   I find that by doing this, I get no reported errors.

Suggestions?

2 answers

Somehow, somewhere, something/someone is doing it. Not plugins? Did you do any customizations? What plugins do you have? Is there something directly manipulating the database? (ALM QC synchronizer plugin maybe)?

Plugins in use are:

  • Email This Issue - v.6.3.0.3
  • Enterprise Message Handler for JIRA - v.1.6.77
  • Insight - v.2.30.2
  • JIRA Timesheet Reports and Gadgets - v.2.9.2.0
  • nFeed v.5.3.4
  • The Secheduler - v.3.2.13
  • Adaptavist ScriptRunner for JIRA Standard - v.4.1.3.3
  • Intenso Utils - v. 1.8
  • JIRA Service Desk - 2.3.6
  • JIRA Suite Utilities - v.1.4.10
  • JIRA Toolkit - v0.35.11
  • Minyaa - 3.4.3
  • Workflow Enhancer for JIRA - v.3.2
  • JIRA Linker Plugin - v.1.4.0

 

We don't have anything directly manipulating the database as far as I know.   I have asked our DBA to responds as well.

Something like this happened to us a long time ago and we found out it's database related (ALM QC sync)

Yup, if there's nothing in the logs, then it's unlikely to be code. If your indexing is drifting off, then there's going to be a strong suspect in "something else changing the database". I'd be tempted to get your DBA to change the password on the database alongside the same change in JIRA, so that you know there's nothing else doing it. If anybody screams that it breaks something, great, discipline them for breaking your JIRA ;-)

+1 for the "discipline them" approach

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

922 views 5 18
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot