re-index fail after upgrade to 8.5.9

Srikanth November 17, 2020

Re-indexing fails after upgrade from 7.6.6. to 8.5.9 

- We are on Data center,

- Service desk and all apps upgraded as per procedure

- While indexing Node is being added to load balancer

- Cache file taken backup and deleted before  re-index

Trouble shoot as of now

 - Service stopped and restarted

 -  Apps Safe mode and run the re-index

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

After click re-index tab, bellow is immediate message 

Sorry, we had some technical problems during your last operation.

Request assistance

Copy the content below and send it to your Jira Administrator

Technical details

Log's referral number: c85dd09f-afd2-40f3-8c8c-366970fae97b 

log message like below

 11-17 06:32:10,673-0800 http-nio-80-exec-11 ERROR [c.a.j.web.servlet.InternalServerErrorServlet] {errorId=e5f9dc1a-2658-4d69-88a7-ba7638c5abbe, interpretedMsg=, cause=com.google.template.soy.tofu.SoyTofuException: When evaluating "'IndexReIndex!reindex.jspa?atl_token=' + $atlToken + '&indexingStrategy=' + $indexingStrategy": Attempted to coerce undefined value into a string., stacktrace=com.google.template.soy.tofu.SoyTofuException: When evaluating "'IndexReIndex!reindex.jspa?atl_token=' + $atlToken + '&indexingStrategy=' + $indexingStrategy": Attempted to coerce undefined value into a string.

Cause

Referer URL: http://localhost/secure/admin/jira/IndexAdmin.jspa
com.google.template.soy.tofu.SoyTofuException: When evaluating "'IndexReIndex!reindex.jspa?atl_token=' + $atlToken + '&indexingStrategy=' + $indexingStrategy": Attempted to coerce undefined value into a string.

com.google.template.soy.tofu.SoyTofuException: When evaluating "'IndexReIndex!reindex.jspa?atl_token=' + $atlToken + '&indexingStrategy=' + $indexingStrategy": Attempted to coerce undefined value into a string.
at JIRA.Templates.Admin.Index.buttonContainer(confirm-reindex.soy:65) [?:?]
at JIRA.Templates.Admin.Index.confirmReindex(Unknown Source) [?:?]
at com.google.template.soy.tofu.internal.BaseTofu.renderMainHelper(BaseTofu.java:369) [?:?]
at com.google.template.soy.tofu.internal.BaseTofu.renderMain(BaseTofu.java:322) [?:?]
at com.google.template.soy.tofu.internal.BaseTofu.access$100(BaseTofu.java:66) [?:?]
at com.google.template.soy.tofu.internal.BaseTofu$RendererImpl.render(BaseTofu.java:476) [?:?]
at com.atlassian.soy.impl.DefaultSoyManager.render(DefaultSoyManager.java:154) [?:?]
at com.atlassian.soy.impl.DefaultSoyTemplateRenderer.render(DefaultSoyTemplateRenderer.java:45) [?:?]
at com.atlassian.soy.impl.DefaultSoyTemplateRenderer.render(DefaultSoyTemplateRenderer.java:39) [?:?]
at com.atlassian.jira.web.dispatcher.JiraSoyViewDispatcher.render(JiraSoyViewDispatcher.java:48) [classes/:?]
at com.atlassian.jira.web.dispatcher.JiraSoyViewDispatcher.dispatch(JiraSoyViewDispatcher.java:38) [classes/:?]
at com.atlassian.jira.web.dispatcher.JiraWebworkViewDispatcher

 

please advise , 

 

 

1 answer

1 accepted

0 votes
Answer accepted
Daniel Ebers
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.
November 17, 2020

Hi Srikanth,

while I cannot say anything specific to this error I just wanted to let you know following info.

In a similar case a user had specific Java Script snippets placed in Announcement Banner which prevented the Re-Index to go through.

Please check at first if in Banner some code is placed and if possible remove it for a second.

If this should not help please update Community here - maybe somebody else can then advise further.

Cheers,
Daniel

Srikanth November 18, 2020

Hi Daniel,

Thanks for quick response

Yes, removed banner. Also we have Jira watcher field plug in ,though it is not DC approved we should upgrade in order for a error free Re-indexing. 

https://confluence.atlassian.com/jirakb/soytofuexception-encountered-attempting-to-reindex-after-upgrading-to-jira-8-5-1026036354.html

 

Regards

Suggest an answer

Log in or Sign up to answer