No index-level perm match

Hey all,

All of a sudden, I see these errors in my Elasticsearch logs:
[2017-06-09T16:27:54,004][ERROR][c.f.s.a.BackendRegistry ] Not yet initialized (you may need to run sgadmin)
[2017-06-09T16:27:54,008][ERROR][c.f.s.a.BackendRegistry ] Not yet initialized (you may need to run sgadmin)
[2017-06-09T16:27:54,021][INFO ][o.e.c.r.a.AllocationService] [sHQzypY] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.kibana][0]] …]).
[2017-06-09T16:27:54,071][INFO ][c.f.s.c.IndexBaseConfigurationRepository] Node ‘sHQzypY’ initialized
[2017-06-09T16:27:55,499][INFO ][c.f.s.c.PrivilegesEvaluator] No index-level perm match for User [name=kibanaserver, roles=] [IndexType [index=_all, type=esqueue]] [Action [indices:data/read/search]] [RolesChecked [sg_kibana_server, sg_own_index, sg_public]]
[2017-06-09T16:27:55,499][INFO ][c.f.s.c.PrivilegesEvaluator] No permissions for {sg_public=[IndexType [index=_all, type=esqueue]], sg_own_index=[IndexType [index=_all, type=esqueue]], sg_kibana_server=[IndexType [index=_all, type=esqueue]]}

``

If I add permission for it, then this error appears:
[2017-06-09T15:46:53,705][WARN ][c.f.s.c.PrivilegesEvaluator] _all does not exist in cluster metadata
[2017-06-09T15:46:53,705][WARN ][c.f.s.c.PrivilegesEvaluator] _all does not exist in cluster metadata

``

Because of it, Kibana is not able to connect.

Does anyone have any clue why is this happening?

Thank you very much,
Ádám

It looks like I forgot to re-disable monitoring and Watcher in Kibana.
After I did that, the errors went away.

···

On Friday, June 9, 2017 at 4:31:39 PM UTC+2, ezegyfelh...@gmail.com wrote:

Hey all,

All of a sudden, I see these errors in my Elasticsearch logs:
[2017-06-09T16:27:54,004][ERROR][c.f.s.a.BackendRegistry ] Not yet initialized (you may need to run sgadmin)
[2017-06-09T16:27:54,008][ERROR][c.f.s.a.BackendRegistry ] Not yet initialized (you may need to run sgadmin)
[2017-06-09T16:27:54,021][INFO ][o.e.c.r.a.AllocationService] [sHQzypY] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.kibana][0]] …]).
[2017-06-09T16:27:54,071][INFO ][c.f.s.c.IndexBaseConfigurationRepository] Node ‘sHQzypY’ initialized
[2017-06-09T16:27:55,499][INFO ][c.f.s.c.PrivilegesEvaluator] No index-level perm match for User [name=kibanaserver, roles=] [IndexType [index=_all, type=esqueue]] [Action [indices:data/read/search]] [RolesChecked [sg_kibana_server, sg_own_index, sg_public]]
[2017-06-09T16:27:55,499][INFO ][c.f.s.c.PrivilegesEvaluator] No permissions for {sg_public=[IndexType [index=_all, type=esqueue]], sg_own_index=[IndexType [index=_all, type=esqueue]], sg_kibana_server=[IndexType [index=_all, type=esqueue]]}

``

If I add permission for it, then this error appears:
[2017-06-09T15:46:53,705][WARN ][c.f.s.c.PrivilegesEvaluator] _all does not exist in cluster metadata
[2017-06-09T15:46:53,705][WARN ][c.f.s.c.PrivilegesEvaluator] _all does not exist in cluster metadata

``

Because of it, Kibana is not able to connect.

Does anyone have any clue why is this happening?

Thank you very much,
Ádám