How To Solve Issues Related to Log – Unable to start GCE discovery service

How To Solve Issues Related to Log – Unable to start GCE discovery service

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Unable to start GCE discovery service” it’s important to understand a few problems related to Elasticsearch concepts cloud-aws, discovery, discovery-gce, instances, plugins. See bellow important tips and explanations on these concepts

Log Context

Log”Unable to start GCE discovery service” classname is GceInstancesServiceImpl.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 builder.setHttpRequestInitializer(credential);
            }

            this.client = builder.build();
        } catch (Exception e) {
            logger.warn("unable to start GCE discovery service"; e);
            throw new IllegalArgumentException("unable to start GCE discovery service"; e);
        }

        return this.client;
    }




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Unable to Start ElasticSearch with Public IP instead of localhost

0.85 K 

Es 5 5 0 Will Not Start Up With Gce  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now