Elastic search curl -X GET “localhost:9200/” Connection Refused





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















I have followed the instructions at https://www.elastic.co/guide/en/elasticsearch/reference/current/deb.html to install elasticsearch on a clean install of Ubuntu Server 16.04.



I have run the following commands through terminal to install.



wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.3.0.deb

sudo dpkg -i elasticsearch-6.3.0.deb

sudo /bin/systemctl daemon-reload

sudo /bin/systemctl enable elasticsearch.service

sudo systemctl start elasticsearch.service


However when I run curl -X GET "localhost:9200/" I get the following error



curl: (7) Failed to connect to localhost port 9200: Connection refused


This is the contents of /etc/elasticsearch/elasticsearch.yml



# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
# Before you set out to tweak and tune the configuration, make sure you
# understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
#cluster.name: my-application
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
#node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
path.data: /var/lib/elasticsearch
#
# Path to log files:
#
path.logs: /var/log/elasticsearch
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: localhost
#
# Set a custom port for HTTP:
#
http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when new node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.zen.ping.unicast.hosts: ["host1", "host2"]
#
# Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):
#
#discovery.zen.minimum_master_nodes:
#


Any suggestions or advice would be appreciated to help me get elasticsearch up and running.



Also worth pointing out that I am running on a 32 bit system










share|improve this question

























  • Did you modify the network.host? The documentation here suggests it should read _local_

    – steeldriver
    Jun 16 '18 at 16:39











  • @steeldriver yes I did. The initial value was 127.0.0.1 which didn't work and after a quick google I read somewhere to try localhost i will try _local_ now.

    – Conor
    Jun 16 '18 at 17:07


















1















I have followed the instructions at https://www.elastic.co/guide/en/elasticsearch/reference/current/deb.html to install elasticsearch on a clean install of Ubuntu Server 16.04.



I have run the following commands through terminal to install.



wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.3.0.deb

sudo dpkg -i elasticsearch-6.3.0.deb

sudo /bin/systemctl daemon-reload

sudo /bin/systemctl enable elasticsearch.service

sudo systemctl start elasticsearch.service


However when I run curl -X GET "localhost:9200/" I get the following error



curl: (7) Failed to connect to localhost port 9200: Connection refused


This is the contents of /etc/elasticsearch/elasticsearch.yml



# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
# Before you set out to tweak and tune the configuration, make sure you
# understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
#cluster.name: my-application
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
#node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
path.data: /var/lib/elasticsearch
#
# Path to log files:
#
path.logs: /var/log/elasticsearch
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: localhost
#
# Set a custom port for HTTP:
#
http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when new node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.zen.ping.unicast.hosts: ["host1", "host2"]
#
# Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):
#
#discovery.zen.minimum_master_nodes:
#


Any suggestions or advice would be appreciated to help me get elasticsearch up and running.



Also worth pointing out that I am running on a 32 bit system










share|improve this question

























  • Did you modify the network.host? The documentation here suggests it should read _local_

    – steeldriver
    Jun 16 '18 at 16:39











  • @steeldriver yes I did. The initial value was 127.0.0.1 which didn't work and after a quick google I read somewhere to try localhost i will try _local_ now.

    – Conor
    Jun 16 '18 at 17:07














1












1








1


1






I have followed the instructions at https://www.elastic.co/guide/en/elasticsearch/reference/current/deb.html to install elasticsearch on a clean install of Ubuntu Server 16.04.



I have run the following commands through terminal to install.



wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.3.0.deb

sudo dpkg -i elasticsearch-6.3.0.deb

sudo /bin/systemctl daemon-reload

sudo /bin/systemctl enable elasticsearch.service

sudo systemctl start elasticsearch.service


However when I run curl -X GET "localhost:9200/" I get the following error



curl: (7) Failed to connect to localhost port 9200: Connection refused


This is the contents of /etc/elasticsearch/elasticsearch.yml



# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
# Before you set out to tweak and tune the configuration, make sure you
# understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
#cluster.name: my-application
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
#node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
path.data: /var/lib/elasticsearch
#
# Path to log files:
#
path.logs: /var/log/elasticsearch
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: localhost
#
# Set a custom port for HTTP:
#
http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when new node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.zen.ping.unicast.hosts: ["host1", "host2"]
#
# Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):
#
#discovery.zen.minimum_master_nodes:
#


Any suggestions or advice would be appreciated to help me get elasticsearch up and running.



Also worth pointing out that I am running on a 32 bit system










share|improve this question
















I have followed the instructions at https://www.elastic.co/guide/en/elasticsearch/reference/current/deb.html to install elasticsearch on a clean install of Ubuntu Server 16.04.



I have run the following commands through terminal to install.



wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.3.0.deb

sudo dpkg -i elasticsearch-6.3.0.deb

sudo /bin/systemctl daemon-reload

sudo /bin/systemctl enable elasticsearch.service

sudo systemctl start elasticsearch.service


However when I run curl -X GET "localhost:9200/" I get the following error



curl: (7) Failed to connect to localhost port 9200: Connection refused


This is the contents of /etc/elasticsearch/elasticsearch.yml



# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
# Before you set out to tweak and tune the configuration, make sure you
# understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
#cluster.name: my-application
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
#node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
path.data: /var/lib/elasticsearch
#
# Path to log files:
#
path.logs: /var/log/elasticsearch
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: localhost
#
# Set a custom port for HTTP:
#
http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when new node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.zen.ping.unicast.hosts: ["host1", "host2"]
#
# Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):
#
#discovery.zen.minimum_master_nodes:
#


Any suggestions or advice would be appreciated to help me get elasticsearch up and running.



Also worth pointing out that I am running on a 32 bit system







server curl elasticsearch






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 16 '18 at 22:50







Conor

















asked Jun 16 '18 at 16:27









ConorConor

614




614













  • Did you modify the network.host? The documentation here suggests it should read _local_

    – steeldriver
    Jun 16 '18 at 16:39











  • @steeldriver yes I did. The initial value was 127.0.0.1 which didn't work and after a quick google I read somewhere to try localhost i will try _local_ now.

    – Conor
    Jun 16 '18 at 17:07



















  • Did you modify the network.host? The documentation here suggests it should read _local_

    – steeldriver
    Jun 16 '18 at 16:39











  • @steeldriver yes I did. The initial value was 127.0.0.1 which didn't work and after a quick google I read somewhere to try localhost i will try _local_ now.

    – Conor
    Jun 16 '18 at 17:07

















Did you modify the network.host? The documentation here suggests it should read _local_

– steeldriver
Jun 16 '18 at 16:39





Did you modify the network.host? The documentation here suggests it should read _local_

– steeldriver
Jun 16 '18 at 16:39













@steeldriver yes I did. The initial value was 127.0.0.1 which didn't work and after a quick google I read somewhere to try localhost i will try _local_ now.

– Conor
Jun 16 '18 at 17:07





@steeldriver yes I did. The initial value was 127.0.0.1 which didn't work and after a quick google I read somewhere to try localhost i will try _local_ now.

– Conor
Jun 16 '18 at 17:07










1 Answer
1






active

oldest

votes


















1














network.host: 127.0.0.1 did the thing in my case.



I had the same exact issue with ES 6.7.1. But neither 0.0.0.0 nor localhost worked for me as network.host values.



I ran the following command:



netstat -natp


I noticed I had this line in the list:



127.0.0.1:9200          :::*                    LISTEN


So I just put the listed host and it worked.






share|improve this answer








New contributor




Vladislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1047155%2felastic-search-curl-x-get-localhost9200-connection-refused%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    network.host: 127.0.0.1 did the thing in my case.



    I had the same exact issue with ES 6.7.1. But neither 0.0.0.0 nor localhost worked for me as network.host values.



    I ran the following command:



    netstat -natp


    I noticed I had this line in the list:



    127.0.0.1:9200          :::*                    LISTEN


    So I just put the listed host and it worked.






    share|improve this answer








    New contributor




    Vladislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.

























      1














      network.host: 127.0.0.1 did the thing in my case.



      I had the same exact issue with ES 6.7.1. But neither 0.0.0.0 nor localhost worked for me as network.host values.



      I ran the following command:



      netstat -natp


      I noticed I had this line in the list:



      127.0.0.1:9200          :::*                    LISTEN


      So I just put the listed host and it worked.






      share|improve this answer








      New contributor




      Vladislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.























        1












        1








        1







        network.host: 127.0.0.1 did the thing in my case.



        I had the same exact issue with ES 6.7.1. But neither 0.0.0.0 nor localhost worked for me as network.host values.



        I ran the following command:



        netstat -natp


        I noticed I had this line in the list:



        127.0.0.1:9200          :::*                    LISTEN


        So I just put the listed host and it worked.






        share|improve this answer








        New contributor




        Vladislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.










        network.host: 127.0.0.1 did the thing in my case.



        I had the same exact issue with ES 6.7.1. But neither 0.0.0.0 nor localhost worked for me as network.host values.



        I ran the following command:



        netstat -natp


        I noticed I had this line in the list:



        127.0.0.1:9200          :::*                    LISTEN


        So I just put the listed host and it worked.







        share|improve this answer








        New contributor




        Vladislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer






        New contributor




        Vladislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered yesterday









        VladislavVladislav

        111




        111




        New contributor




        Vladislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        Vladislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        Vladislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1047155%2felastic-search-curl-x-get-localhost9200-connection-refused%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            GameSpot

            connect to host localhost port 22: Connection refused

            Getting a Wifi WPA2 wifi connection