docker-compose-with-elasticsearch throws the following error on appbase container startup · Issue #4 · appbaseio/reactivesearch-api-docker · GitHub
Skip to content

docker-compose-with-elasticsearch throws the following error on appbase container startup #4

Open
Open
docker-compose-with-elasticsearch throws the following error on appbase container startup#4

Description

@rajeshkp
rajeshkp
opened on Apr 10, 2021

time="2021/04/10 13:50:31" level=error msg="[ElasticSearch: Error] => elastic: http://172.30.0.2:9200 is dead" file=" entry.go:359"
time="2021/04/10 13:50:31" level=fatal msg="Error encountered: error while initializing elastic v7 client: no active connection found: no Elasticsearch node available" file=" logger.go
:192"
=> port used 8000
time="2021/04/10 13:51:39" level=error msg="[ElasticSearch: Error] => elastic: http://172.30.0.2:9200 is dead" file=" entry.go:359"
time="2021/04/10 13:51:39" level=fatal msg="Error encountered: error while initializing elastic v7 client: no active connection found: no Elasticsearch node available" file=" logger.go
:192"
=> port used 8000
time="2021/04/10 13:52:46" level=error msg="[ElasticSearch: Error] => elastic: http://172.30.0.2:9200 is dead" file=" entry.go:359"
time="2021/04/10 13:52:46" level=fatal msg="Error encountered: error while initializing elastic v7 client: no active connection found: no Elasticsearch node available" file=" logger.go
:192"

Activity

  1. rajeshkp commented on Apr 13, 2021

    @rajeshkp
    rajeshkp
    on Apr 13, 2021
    Author

    Appreciate any inputs on this

  2. rajeshkp commented on Apr 22, 2021

    @rajeshkp
    rajeshkp
    on Apr 22, 2021
    Author

    Appreciate any inputs on this

  3. Better-Boy commented on May 6, 2021

    @Better-Boy
    Better-Boy
    on May 6, 2021

    @siddharthlatest Can you please help here as I'm facing the same problem too?

  4. Better-Boy commented on May 6, 2021

    @Better-Boy
    Better-Boy
    on May 6, 2021

    @lakhansamani Facing the following problem

    appbase_configure    | starter.sh: applet not found
appbase_configure    | starter.sh: applet not found
appbase_configure    | starter.sh: applet not found
appbase              | => port used 8000
appbase              | time="2021/05/06 08:30:15" level=fatal msg="ES_CLUSTER_URL env required but not present" file=" entry.go:359"
appbase              | => port used 8000

  5. rajeshkp commented on May 8, 2021

    @rajeshkp
    rajeshkp
    on May 8, 2021
    Author

    @lakhansamani @siddharthlatest appreciate your inputs on this issue

  6. lakhansamani commented on May 8, 2021

    @lakhansamani
    lakhansamani
    on May 8, 2021
    Contributor

    @rajeshkp @Better-Boy thanks for reporting looking into it

  7. lakhansamani commented on May 8, 2021

    @lakhansamani
    lakhansamani
    on May 8, 2021
    Contributor

    @rajeshkp @Better-Boy we have seen the applet issue with non intel machines.
    This happens because we trying to listen to file change in one of the containers.
    We trying to come up with a generic solution here, but till that this is an alternative that you can follow by using

    docker-compose -f docker-compose-with-elasticsearch-without-nginx.yml up

    Here is a quick demo of it
    https://www.loom.com/share/9f8d81c6ba5849dd9b373cec030d337d

  8. Better-Boy commented on May 12, 2021

    @Better-Boy
    Better-Boy
    on May 12, 2021

    Thanks @lakhansamani It's working now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions