Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Index Not Found Exception after installing Shield #5644

Closed
kpcool opened this issue Dec 11, 2015 · 2 comments
Closed

Index Not Found Exception after installing Shield #5644

kpcool opened this issue Dec 11, 2015 · 2 comments

Comments

@kpcool
Copy link

kpcool commented Dec 11, 2015

I had ELK setup working with basic auth via HTTP Proxy. However, today I decided to give Shield a try and installed Shield and added kibana4 user for Kibana Dashboard user and kibana_admin for use in kibana.yml file to connect to ES instance.

After restarting ES and Kibana, I keep running into this problem when I select one of my private indices. The indice is there with all the data, but Kibana is refusing to load the data.

Doesn't the kiban4 user role have read access to all indices?

Error: [index_not_found_exception] no such index, with: {"index":"[kpcool-*]"}
    at respond (http://209.133.206.193:5601/bundles/kibana.bundle.js:63640:16)
    at checkRespForFailure (http://209.133.206.193:5601/bundles/kibana.bundle.js:63603:8)
    at http://209.133.206.193:5601/bundles/kibana.bundle.js:62221:8
    at processQueue (http://209.133.206.193:5601/bundles/commons.bundle.js:41809:29)
    at http://209.133.206.193:5601/bundles/commons.bundle.js:41825:28
    at Scope.$eval (http://209.133.206.193:5601/bundles/commons.bundle.js:43053:29)
    at Scope.$digest (http://209.133.206.193:5601/bundles/commons.bundle.js:42864:32)
    at Scope.$apply (http://209.133.206.193:5601/bundles/commons.bundle.js:43161:25)
    at done (http://209.133.206.193:5601/bundles/commons.bundle.js:37610:48)
    at completeRequest (http://209.133.206.193:5601/bundles/commons.bundle.js:37808:8)

However, interesting thing is that if I select '[packetbeat-]YYYY.MM.DD' as the default index and visit Discover or any other tab in Kibana, it shows the data. So I am puzzled as to where the real bug or issue is.

Can someone help me out with this?

@rashidkpc
Copy link
Contributor

You need to add the _field_stats permission to your roles.yml in shield:

(Note the "<-- THIS LINE")

kibana4:
  cluster: 
      - cluster:monitor/nodes/info
      - cluster:monitor/health 
  indices:
    '*':
      privileges: indices:admin/mappings/fields/get, indices:admin/validate/query, indices:data/read/search, indices:data/read/msearch, indices:admin/get, indices:data/read/field_stats  # <-- THIS LINE 
    '.kibana':
      privileges: indices:admin/exists, indices:admin/mapping/put, indices:admin/mappings/fields/get, indices:admin/refresh, indices:admin/validate/query, indices:data/read/get, indices:data/read/mget, indices:data/read/search, indices:data/write/delete, indices:data/write/index, indices:data/write/update

@kpcool
Copy link
Author

kpcool commented Dec 11, 2015

I added the line and restarted elastic search, but that's didn't solve the issue. Still getting same error.

Here's the kibana4 section from elasticsearch/shield/roles.yml

   # The required permissions for kibana 4 users.
kibana4:
  cluster:
      - cluster:monitor/nodes/info
      - cluster:monitor/health
  indices:
    '*':
      privileges: indices:admin/mappings/fields/get, indices:admin/validate/query, indices:data/read/search, indices:data/read/msearch, indices:admin/get, indices:data/read/field_stats
    '.kibana':
      privileges: indices:admin/exists, indices:admin/mapping/put, indices:admin/mappings/fields/get, indices:admin/refresh, indices:admin/validate/query, indices:data/read/get, indices:data/read/mget, indices:data/read/search, indices:data/write/delete, indices:data/write/index, indices:data/write/update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants