No such index [.opendistro-alerting-config]

Opendistro is not enabled in_ Security, this problem occurs.

Alerting - DestinationService - getEmailGroups: { Error: [index_not_found_exception] no such index [.opendistro-alerting-config], with { resource.type="index_or_alias" &".opendistro-alerting-config" & index_uuid="_na_" & index=".opendistro-alerting-config" }
  at respond (/home/ek/kibana/node_modules/elasticsearch/src/lib/transport.js:349:15)
  at checkRespForFailure (/home/ek/kibana/node_modules/elasticsearch/src/lib/transport.js:306:7)
  at HttpConnector.<anonymous> (/home/ek/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:173:7)
  at IncomingMessage.wrapper (/home/ek/kibana/node_modules/lodash/lodash.js:4949:19)
  at IncomingMessage.emit (events.js:203:15)
  at endReadableNT (_stream_readable.js:1145:12)
  at process._tickCallback (internal/process/next_tick.js:63:19)
status: 404,
displayName: 'NotFound',
 '[index_not_found_exception] no such index [.opendistro-alerting-config], with { resource.type="index_or_alias" &".opendistro-alerting-config" & index_uuid="_na_" & index=".opendistro-alerting-config" }',
path: '/_opendistro/_alerting/destinations/email_groups/_search',
query: {},
 { error:
    { root_cause: [Array],
      type: 'index_not_found_exception',
      reason: 'no such index [.opendistro-alerting-config]',
      'resource.type': 'index_or_alias',
      '': '.opendistro-alerting-config',
      index_uuid: '_na_',
      index: '.opendistro-alerting-config' },
   status: 404 },
statusCode: 404,
 '{"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index [.opendistro-alerting-config]","resource.type":"index_or_alias","":".opendistro-alerting-config","index_uuid":"_na_","index":".opendistro-alerting-config"}],"type":"index_not_found_exception","reason":"no such index [.opendistro-alerting-config]","resource.type":"index_or_alias","":".opendistro-alerting-config","index_uuid":"_na_","index":".opendistro-alerting-config"},"status":404}',
toString: [Function],
toJSON: [Function] }

@shichw Can you explain what you are trying to do, it’s not clear. Are you trying to install just the alerting odfe plugin?

Can you also provide elasticsearch.yml and kibana.yml? (redact any sensitive details)
Also if you are just installing odfe plugins on top of elasticsearch 7.10.2, can you confirm if it’s OSS version and which plugins are installed.

Thank you for your attention. I installed opendistroforelasticsearch and opendistroforelasticsearch-1.13.2 on a single node. After installation, I only modified the IP address without other configurations.

@shichw When do you see the error? Can you provide the steps so I can try and reproduce.

After installing and setting the IP, click alerting for the first time. at this time ,I’m not running opendistro_Security script.

@shichw What do you mean by you installed odfe and odfe-1.13.2? Do you mean elasticsearch and odfe-1.13.2?

Which OS are you testing this one? (How did you install odfe tar/deb/docker?).

I would recommend to test it via docker to remove any dependency issues. The images are already baked to have elasticsearch with all the plugins. So you are up and running in minutes. Docker-compose can be found here

I installed version 1.13.2 of odfe and odfe-kibana through tar. I can’t use docker skillfully.

Which OS are you running odfe on?

running on CentOS 8.4.2105

I have just tested odfe 1.13.2 on centOS 8.5 and cannot reproduce the error you are describing. Further more I think there is some confusion regarding the security script.

Below are the step I performed to set everything up:
Set up odfe (with all plugins):

curl -o opendistroforelasticsearch-1.13.2-linux-x64.tar.gz

tar -zxf opendistroforelasticsearch-1.13.2-linux-x64.tar.gz
cd opendistroforelasticsearch-1.13.2

You should now be able to run below command and get the usual elasticsearch output (“You know, for Search”)

curl -XGET https://localhost:9200 -u 'admin:admin' --insecure

Notice that the above command connects to https and uses default username and password, indicating that the security has already been initialised.

Next Set up Kibana

In new terminal issue below commands:

curl -o opendistroforelasticsearch-kibana-1.13.2-linux-x64.tar.gz

tar -zxf opendistroforelasticsearch-kibana-1.13.2-linux-x64.tar.gz
cd opendistroforelasticsearch-kibana

In the browser (on the same machine) type localhost:5601 and you should be able to login with the same admin:admin credentials, go to alerts and everything should work.

Before making any changes, can you ensure the above is working as expected?

If it is, please confirm which line in which config file is being changed and any actions taken to reload the config (odfe restart or otherwise).

The changes made in elasticsearch.yml are my-application node-1
discovery.seed_hosts: [""]
cluster.initial_master_nodes: ["node-1"]

The changes made in kibana.yml are

This problem occurred during the first startup. When I checked elasticsearch.yml again, I found that there were more SSL configurations in it, and this problem was eliminated.

Glad to hear it was resolved.