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



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

Opster Team

Jan-20, Version: 1.7-8.0



Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “Unable to start GCE discovery service” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cloud-aws, discovery, discovery-gce, instances, plugins.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations. 

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 -views 0.85 K ,score –

Es 5 5 0 Will Not Start Up With Gce  

 

About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now