elastic / app-search-kb-demo

A beautiful, modern customer support/knowledge base search experience for App Search using Search UI.
Apache License 2.0
21 stars 7 forks source link

Could not start full stack with docker-compose #19

Open jetdream opened 3 years ago

jetdream commented 3 years ago

# docker-compose up -d
      <<< skipped the bulding process>>>
Successfully built fe370d6e4302
Successfully tagged app-search-kb-demo_dataimport:latest
WARNING: Image for service dataimport was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Creating app-search-kb-demo_frontend_1          ... done
Creating app-search-kb-demo_enterprise_search_1 ... done
Creating app-search-kb-demo_dataimport_1        ... done
Creating app-search-kb-demo_elasticsearch_1     ... done

#docker ps
CONTAINER ID        IMAGE                                                         COMMAND                  CREATED             STATUS              PORTS                                        NAMES
ed7d3e276db7        docker.elastic.co/elasticsearch/elasticsearch:7.8.0           "/tini -- /usr/local…"   12 seconds ago      Up 9 seconds        0.0.0.0:9200->9200/tcp, 9300/tcp             app-search-kb-demo_elasticsearch_1
1c4b5d59df3d        docker.elastic.co/enterprise-search/enterprise-search:7.8.0   "/usr/local/bin/dock…"   12 seconds ago      Up 9 seconds        0.0.0.0:3002->3002/tcp                       app-search-kb-demo_enterprise_search_1
66cf65712071        app-search-kb-demo_dataimport                                 "docker-entrypoint.s…"   12 seconds ago      Up 9 seconds                                                     app-search-kb-demo_dataimport_1
d65971f92daf        app-search-kb-demo_frontend                                   "docker-entrypoint.s…"   12 seconds ago      Up 9 seconds        0.0.0.0:5000->5000/tcp                 

after some time app-search-kb-demo_enterprise_search_1 container is dead:

# docker logs app-search-kb-demo_enterprise_search_1
Found java executable in PATH
Java version: 1.8.0_252

Enterprise Search is starting...

scripting container class loader urls: [file:/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/lib/jruby-stdlib-9.2.9.0.jar, file:/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/lib/jetty-util.jar, file:/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/lib/jruby-rack-1.1.21.jar, file:/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/lib/jetty-servlets.jar, file:/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/lib/jruby-core-9.2.9.0-complete.jar, file:/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/lib/jruby-rack-worker_0.14.1.jar]
setting GEM_HOME to /usr/share/enterprise-search/tmp/jruby5654986675178922316extract/gems
... and BUNDLE_GEMFILE to /usr/share/enterprise-search/tmp/jruby5654986675178922316extract/Gemfile
loading resource: /usr/share/enterprise-search/tmp/jruby5654986675178922316extract/./META-INF/rails.rb
invoking /usr/share/enterprise-search/tmp/jruby5654986675178922316extract/./META-INF/rails.rb with: [runner, SharedTogo.start_app_server!]
[2020-10-15T02:03:36.162+00:00][14][2002][app-server][INFO]: Failed to connect to Elasticsearch backend. Make sure it is running.
[2020-10-15T02:03:41.476+00:00][14][2002][app-server][INFO]: Successfully connected to Elasticsearch
[2020-10-15T02:03:41.726+00:00][14][2002][app-server][ERROR]: 
--------------------------------------------------------------------------------

Elasticsearch API key service must be enabled. It is enabled automatically when you configure Elasticsearch to use TLS on the HTTP interface.
Alternatively, you can explicitly enable the setting within Elasticsearch by opening config/elasticsearch.yml and adding:

xpack.security.authc.api_key.enabled: true

--------------------------------------------------------------------------------

ERROR: org.jruby.exceptions.SystemExit: (SystemExit) exit
org.jruby.exceptions.SystemExit: (SystemExit) exit
    at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:751)
    at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:714)
    at RUBY.fatal_error(/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/shared_togo/lib/shared_togo.class:1114)
    at RUBY.check_elasticsearch_features!(/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/shared_togo/lib/shared_togo.class:272)
    at RUBY.configure!(/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/shared_togo/lib/shared_togo.class:259)
    at RUBY.<main>(/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/config/application.class:19)
    at org.jruby.RubyKernel.load(org/jruby/RubyKernel.java:1013)
    at RUBY.<main>(/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/config/application.rb:1)
    at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:978)
    at RUBY.<main>(/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/gems/gems/railties-4.2.11.1/lib/rails/commands/runner.rb:51)
    at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:978)
    at RUBY.require_command!(/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/gems/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:123)
    at RUBY.runner(/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/gems/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:90)
    at RUBY.run_command!(/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/gems/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:39)
    at RUBY.<main>(/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/gems/gems/railties-4.2.11.1/lib/rails/commands.rb:17)
    at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:978)
    at usr.share.enterprise_minus_search.tmp.jruby5654986675178922316extract.$_dot_.META_minus_INF.rails.<main>(/usr/share/enterprise-search/tmp/jruby5654986675178922316extract/./META-INF/rails.rb:7)
switchnollie commented 3 years ago

I'm getting the same error. Any news on this issue?