Could not locate that index-pattern (id: [Index_Name]), click here to re-create it

OpenSearch Dashboards
1

Versions (relevant - OpenSearch/Dashboard/Server OS/Browser): v 2.5.0

Describe the issue: We have created a new dashboard using the Index Pattern. When we try to view the Dashboard, it works fine, but sometimes it shows an error saying Could not locate that index-pattern (id: [Index_Name]), [click here to re-create it]. I don’t know what we can do to resolve this error. Please help me to fix the error.

Configuration: OpenSearch Dashboard is working with docker image

Relevant Logs or Screenshots: Sometimes it doesn’t work and gives an error

image
image1914×881 106 KB

Below is a web console error

visualizations.plugin.js:6 Error: Could not locate that index-pattern (id: email_analytics_index_pattern), [click here to re-create it](management/opensearch-dashboards/indexPatterns)
    at _callee11$ (data.plugin.js:1:835707)
    at tryCatch (customImportMapDashboards.plugin.js:13:125095)
    at Generator.invoke [as _invoke] (customImportMapDashboards.plugin.js:13:129111)
    at Generator.next (customImportMapDashboards.plugin.js:13:126290)
    at index_patterns_asyncGeneratorStep (data.plugin.js:1:822086)
    at _next (data.plugin.js:1:822411)

discover.plugin.js:6 Error: Could not locate that index-pattern (id: email_analytics_index_pattern), [click here to re-create it](management/opensearch-dashboards/indexPatterns)
    at _callee11$ (data.plugin.js:1:835707)
    at tryCatch (customImportMapDashboards.plugin.js:13:125095)
    at Generator.invoke [as _invoke] (customImportMapDashboards.plugin.js:13:129111)
    at Generator.next (customImportMapDashboards.plugin.js:13:126290)
    at index_patterns_asyncGeneratorStep (data.plugin.js:1:822086)
    at _next (data.plugin.js:1:822411)
2

@VijayKansagara How did you deploy your cluster?
Do you have more than one instance of OpenSearch Dashboards connecting to the same OpenSearch cluster?

Could you share your opensearch_dashboads.yml file?

Is the OpenSearch Dashboards and OpenSearch located on the same machine?

3

@pablo We are deploying the OpenSearch dashboard using the docker-compose.yml file. Below is the code to deploy the OpenSearch Dashboard and OpenSearch instance.


 elasticsearch:
    image: opensearchproject/opensearch:2.5.0
    ports:
      - 9200:9200
      - 9300:9300
    environment:
      - bootstrap.memory_lock=true
      - discovery.type=single-node
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
      - plugins.security.ssl.http.enabled=false
    volumes:
      - ./volumes/esdata:/usr/share/elasticsearch/data
  kibana:
    image: opensearchproject/opensearch-dashboards:2.5.0
    ports:
      - 5601:5601
    environment:
      - OPENSEARCH_HOSTS=http://admin:admin@elasticsearch:9200
      - SERVER_XSRF_DISABLEPROTECTION=true

Below are the Docker images generated after running that file.

image
image1213×316 24.1 KB

4

@pablo We have deploy one instance OpenSearch and one instance OpenSearch Dashboard? Do you have any idea about this error?

5

@VijayKansagara I’ve checked your docker-compose.yml and used in my local deployment.
I didn’t experience the reported issue at any time. I had this running for a couple of days. I’ve used pfsense as test data.

My cluster was deployed on the Ubuntu 22 VMware VM. I’ve noticed that you’ve used Docker Desktop. Was it on your local machine or Windows Server? Is that your target production environment or you will switch to a Linux server?

6

Hello @pablo, I’m currently working with Windows Server and have encountered a similar issue through an alternative method. Here is the approach:

I have successfully downloaded the OpenSearch and OpenSearch Dashboard zip files, followed by their extraction. After modifying the configurations in the ‘opensearch.yml’ and ‘opensearch_dashboards.yml’ files accordingly, I proceeded to launch both instances. Subsequently, I navigated to an OpenSearch Dashboard (accessible via http://localhost:5601), from which I generated a shareable URL with the intent of accessing that specific Dashboard in a web browser. However, upon attempting to open this shared URL, I occasionally encounter an error stating Could not locate that dashboard (id: e7cfabd0-228e-11ec-8113-a935c9c5bf51).

OpensearchDashboardSharedURL

Below are the opensearch.yml and opensearch_dashboards.yml files

opensearch.yml

plugins.security.disabled: false
discovery.type: single-node
plugins.security.ssl.transport.pemcert_filepath: esnode.pem
plugins.security.ssl.transport.pemkey_filepath: esnode-key.pem
plugins.security.ssl.transport.pemtrustedcas_filepath: root-ca.pem
plugins.security.ssl.transport.enforce_hostname_verification: false
plugins.security.ssl.http.enabled: false
plugins.security.ssl.http.pemcert_filepath: esnode.pem
plugins.security.ssl.http.pemkey_filepath: esnode-key.pem
plugins.security.ssl.http.pemtrustedcas_filepath: root-ca.pem
plugins.security.allow_unsafe_democertificates: true
plugins.security.allow_default_init_securityindex: true
plugins.security.authcz.admin_dn: CN=kirk,OU=client,O=client,L=test, C=de
plugins.security.audit.type: internal_opensearch
plugins.security.enable_snapshot_restore_privilege: true
plugins.security.check_snapshot_restore_write_privileges: true
plugins.security.restapi.roles_enabled: ["all_access", "security_rest_api_access"]
plugins.security.system_indices.enabled: true
plugins.security.system_indices.indices: [".plugins-ml-model", ".plugins-ml-task",
“.opendistro-alerting-config", ".opendistro-alerting-alert*",
".opendistro-anomaly-results*", ".opendistro-anomaly-detector*", ".opendistro-anomaly-checkpoints",
“.opendistro-anomaly-detection-state", ".opendistro-reports-",
".opensearch-notifications-", ".opensearch-notebooks", ".opensearch-observability", ".opendistro-asynchronous-search-response*", ".replication-metadata-store"]
node.max_local_storage_nodes: 3
bootstrap.memory_lock: true
plugins.security.cache.ttl_minutes: 0

opensearch_dashboards.yml

opensearch.hosts: [http://localhost:9200]
opensearch.ssl.verificationMode: none
opensearch.username: [username]
opensearch.password: [password]
opensearch.requestHeadersWhitelist: [authorization, securitytenant]

opensearch_security.multitenancy.enabled: true
opensearch_security.multitenancy.tenants.preferred: [Private, Global]
opensearch_security.readonly_mode.roles: [kibana_read_only]
# Use this setting if you are running opensearch-dashboards without https
opensearch_security.cookie.secure: false
server.xsrf.disableProtection: true
server.host: "0.0.0.0"

Could you kindly take a moment to see if you’re familiar with this issue or have any insights that might help resolve it?

7

@VijayKansagara Is that still 2.5.0? Have you tried latest versions?
Is there any reason why you’ve tested against 2.5.0 initially?

8

No, I’ve also run tests on version 2.10.0 and encountered the same result. I will verify it using the latest version and provide you with an update accordingly.

9

@pablo Even with the most recent update, version 2.16.0, I’m still encountering the same error.

image
image1578×811 53.3 KB