"The JIRA search index is missing" error

[Nitin Benjamin]

Hi All,

I am working on upgrading Jira for my project. So I replicated the existing Production instance ( v6.3.9#6) to make a dev instance and have pointed to DEV database that we already have for this upgrade. I brought up DEV Jira instance but while accessing I have getting "JIRA search index is missing error". Please let me know what I need to do for this error. My real intention is to upgrade our Production Jira to the latest.  So I am trying to create dev instance and upgrage before I touch Prod. Quick response is most most welcome,

Kindly find the screenshot for the error.

Thanks,

Nitin.

[Vickey Palzor Lepcha]

I am assuming - there is a filesystem/path problem with your setup , can you verify your file paths ?

Your DB Config file is under ..../DEV/....

but your indexes are under ...../PROD/....

Is everything right out there ?

/opt/customer/Atlassian/DEV/Jira_Home/dbconfig.xml

/opt/customer/Atlassian/PROD/Jira_Home/caches/indexes] 

[Vickey Palzor Lepcha]

Have you run a reindex already or not yet ?

[Nitin Benjamin]

Not yet. Since I am not not able to login and I see the above error in login page itself.

[Vickey Palzor Lepcha]

rename the current index directories that you have and restart the application - it should create a new set of index files by itself as it restarts and see how it goes.

[Nitin Benjamin]

Hi Vickey,

Thanks for your response. I have already tried it with deleting and renaming index directory but still I am facing same issue.

[Vickey Palzor Lepcha]

Are there any more error messages in the logfile ?

[Vickey Palzor Lepcha]

I'm surprised that even new indexes aren't working - how good are your exports that you've taken from the current production setup ?

And how does your database for the dev look like ? does it have all the prerequisites before you populated it with your data from production?

[Nitin Benjamin]

Hi Vickey,

I have taken exports of current Production setup cleanly and I don't think we have an issue there. As far ad DB is concerned, we already have separate DEV data created and given to me and I ma using that so I am not sure the full details for this. I will send you a logs of tomcat while brining it up. That would hopefully help to throw light and see picture clearly. 

=============================================

019-12-02 00:53:14,074 localhost-startStop-1 INFO [atlassian.jira.startup.JiraStartupLogger]

___ Plugin System Started _________________

2019-12-02 00:53:14,308 localhost-startStop-1 WARN [atlassian.jira.scheduler.OfBizRunDetailsDao] Should not call getLastRunForJ
ob() when the scheduler is in standby; returning null for jobId=com.atlassian.jira.service.JiraService:10000
2019-12-02 00:53:14,421 localhost-startStop-1 INFO [jira.config.database.SystemDatabaseConfigurationLoader] Reading database co
nfiguration from /opt/customer/Atlassian/DEV/Jira_Home/dbconfig.xml
2019-12-02 00:53:14,430 localhost-startStop-1 INFO [jira.instrumentation.external.DatabaseExternalGauges] Installing DBCP monit
oring instruments: DatabaseExternalGauges.JiraDbcpInstruments[instruments=[DBCP_MAX, DBCP_ACTIVE, DBCP_IDLE],objectName=com.atlassia
n.jira:name=BasicDataSource]
2019-12-02 00:53:15,035 localhost-startStop-1 INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Checking JIRA consistency
2019-12-02 00:53:15,061 localhost-startStop-1 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Indexing is turned on, but in
dex path [/opt/customer/Atlassian/PROD/Jira_Home/caches/indexes] invalid - disabling indexing
2019-12-02 00:53:15,066 localhost-startStop-1 INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] The Server ID for this JIRA in
stance is: [AS7N-U1BD-D6N6-R2XO]
2019-12-02 00:53:15,147 localhost-startStop-1 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number to
6339
2019-12-02 00:53:15,187 localhost-startStop-1 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current version to 6.3.9
2019-12-02 00:53:15,191 localhost-startStop-1 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting downgrade version to 6.2
.6
2019-12-02 00:53:18,244 localhost-startStop-1 INFO [ext.bamboo.service.PlanStatusUpdateServiceImpl] Job 'com.atlassian.jira.plu
gin.ext.bamboo.service.PlanStatusUpdateServiceImpl:job' scheduled to run every 60000ms
2019-12-02 00:53:18,245 localhost-startStop-1 INFO [plugins.dvcs.scheduler.DvcsScheduler] DvcsScheduler job handler registered
2019-12-02 00:53:18,320 localhost-startStop-1 INFO [jira.whatsnew.listeners.WhatsNewUpgradeFinishedListenerImpl] Enabling show-
whats-new-flag for all users
2019-12-02 00:53:18,345 localhost-startStop-1 INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler not started:
Johnson events detected.
2019-12-02 00:53:18,484 UpmScheduler:thread-1 WARN anonymous [atlassian.upm.pac.PacClientImpl] Update check request may take lon
ger because of the number of add-ons
Dec 02, 2019 12:53:18 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-5901"]
Dec 02, 2019 12:53:18 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8443"]
Dec 02, 2019 12:53:18 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 86528 ms
^C
nbenjami@phx-epro-app47>