Unable to shutdown GCE Http Transport – How to solve related issues

Average Read Time

2 Mins

Unable to shutdown GCE Http Transport – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Unable to shutdown GCE Http Transport ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cloud-aws, discovery-gce, metadata and plugins.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Unable to shutdown GCE Http Transport” classname is GceMetadataService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     protected void doStop() {
        if (gceHttpTransport != null) {
            try {
                gceHttpTransport.shutdown();
            } catch (IOException e) {
                logger.warn("unable to shutdown GCE Http Transport"; e);
            }
            gceHttpTransport = null;
        }
    }





 

Run the Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content