ES6.4 will not start up with gce discovery


(Francis Lapique) #1

My elasticsearch.yml looks like this:

network.host: gce:hostname
cloud.gce.project_id: my_id
cloud.gce.zone: europe-west1-b
discovery.zen.hosts_provider: gce

Which account is gce-discovery running under?

The logs

[2018-09-30T13:11:46,828][INFO ][o.e.n.Node ] [instance-fondation] starting ...
[2018-09-30T13:11:47,453][INFO ][o.e.t.TransportService ] [instance-fondation] publish_address {10.132.0.4:9300}, bound_addresses {10.132.0.4:9300}
[2018-09-30T13:11:47,513][INFO ][o.e.b.BootstrapChecks ] [instance-fondation] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2018-09-30T13:11:47,678][INFO ][o.e.c.g.GceInstancesServiceImpl] [instance-fondation] starting GCE discovery service
[2018-09-30T13:11:48,055][WARN ][o.e.c.g.GceInstancesServiceImpl] [instance-fondation] Problem fetching instance list for zone europe-west1-b
com.google.api.client.googleapis.json.GoogleJsonResponseException: 403 Forbidden
{
"code" : 403,
"errors" : [ {
"domain" : "global",
"message" : "Insufficient Permission",
"reason" : "insufficientPermissions"
} ],
"message" : "Insufficient Permission"


(David Pilato) #2

Make sure you set the rights compute-rw for the instance as described here: https://www.elastic.co/guide/en/elasticsearch/plugins/6.4/discovery-gce-usage-long.html#discovery-gce-usage-long-first-instance


(system) #3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.