Searching Using Quick Search Does Not Work
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Symptoms
Normal search works as expected but searches using Quick Search return no results. Rebuilding the index does not resolve the issue.
The following appears in the atlassian-confluence.log:
1
Caused by: com.google.common.util.concurrent.UncheckedExecutionException: java.lang.IllegalStateException: Required plugin module com.atlassian.plugins.atlassian-nav-links-plugin:rotp-menu was either missing or disabledDiagnosis
Check if the Atlassian Navigation Links Plugin is disabled in the UPM (Universal Plugin Manager). This plugin supplies the functionality of Quick Search. It is a system plugin which should be enabled by default. If it's disabled, it cannot be enabled through the UI.
If the plugin is disabled in the UPM, check if this plugin is also disabled in the database by running this query:
1
select BANDANAVALUE from BANDANA where BANDANAKEY = 'plugin.manager.state.Map';Cause
Atlassian Navigation Links Plugin is disabled. This can also occur because it is reaching the plugin timeout.
Solution
Resolution
To resolve the problem, the plugin needs to be enabled.
Follow workaround #3 from this KB: Plugins are Disabled at Startup and Various Timeout Errors Appear in the Logs After Startup to manually enable the plugin from the database, if the query in the diagnosis section above returned com.atlassian.plugins.atlassian-nav-links-plugin with boolean false.
Otherwise, increase the plugin timeout value to 600 (-Datlassian.plugins.enable.wait=600) and restart Confluence as per the workaround #2 mentioned in the same KB.
Was this helpful?