Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker-compose doesn't work #114

Closed
seifreed opened this issue Jul 3, 2019 · 7 comments
Closed

Docker-compose doesn't work #114

seifreed opened this issue Jul 3, 2019 · 7 comments
Labels
question Further information is requested solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@seifreed
Copy link

seifreed commented Jul 3, 2019

Description

I just did docker-compose up and I can't get up the environment:

Environment

  1. Ubuntu 18
  2. Last version

Reproducible Steps

git clone opencti

docker-compose up

Expected Output

integration_1    | Waiting for token in shared config...
worker_1         | Waiting for token in shared config...
opencti_1        | Waiting ElasticSearch to launch...
integration_1    | Waiting for token in shared config...
worker_1         | Waiting for token in shared config...
opencti_1        | Waiting ElasticSearch to launch...
integration_1    | Waiting for token in shared config...
worker_1         | Waiting for token in shared config...
openctidocker_elasticsearch_1 exited with code 1
opencti_1        | elasticsearch: forward host lookup failed: Unknown host
opencti_1        | Waiting ElasticSearch to launch...
integration_1    | Waiting for token in shared config...
worker_1         | Waiting for token in shared config...
opencti_1        | elasticsearch: forward host lookup failed: Unknown host
opencti_1        | Waiting ElasticSearch to launch...
integration_1    | Waiting for token in shared config...
worker_1         | Waiting for token in shared config...
opencti_1        | elasticsearch: forward host lookup failed: Unknown host
opencti_1        | Waiting ElasticSearch to launch...
integration_1    | Waiting for token in shared config...
@SamuelHassine
Copy link
Member

Hello,

The problem come from openctidocker_elasticsearch_1 exited with code 1. Could you check why the ElasticSearch Docker container is exiting?

@seifreed
Copy link
Author

seifreed commented Jul 3, 2019

Yup, I saw that the thing is. Did you guys try to spin up opencti on a clean ubuntu 18?
Before start to troubleshooting it myself, I wanna know which versions are compatible and if it's work by default ^_^!

@cdiraimondi
Copy link

I've had problems similar in the past due to the the docker-compose.yml containing options for volumes in order to make the data persistent. I resorted back to the previous version of docker-compose.yml which did not have the volumes configuration. Are you noticing any exceptions being thrown by ElasticSearch?

@soreno123
Copy link

soreno123 commented Jul 4, 2019

Same problem here, where i can find the previous version of docker-compose.yml ?
Anyway i'm getting also this exception:
elasticsearch_1 | [2019-07-04T12:24:50,509][WARN ][o.e.b.ElasticsearchUncaughtExceptionHandler] [unknown] uncaught exception in thread [main]
elasticsearch_1 | org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: Failed to create node environment
elasticsearch_1 | at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:163) ~[elasticsearch-6.7.1.jar:6.7.1]
elasticsearch_1 | at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:150) ~[elasticsearch-6.7.1.jar:6.7.1]
elasticsearch_1 | at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-6.7.1.jar:6.7.1]
elasticsearch_1 | at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) ~[elasticsearch-cli-6.7.1.jar:6.7.1]
elasticsearch_1 | at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-6.7.1.jar:6.7.1]
elasticsearch_1 | at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:116) ~[elasticsearch-6.7.1.jar:6.7.1]
elasticsearch_1 | at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:93) ~[elasticsearch-6.7.1.jar:6.7.1]
elasticsearch_1 | Caused by: java.lang.IllegalStateException: Failed to create node environment
elasticsearch_1 | at org.elasticsearch.node.Node.(Node.java:299) ~[elasticsearch-6.7.1.jar:6.7.1]
elasticsearch_1 | at org.elasticsearch.node.Node.(Node.java:266) ~[elasticsearch-6.7.1.jar:6.7.1]
elasticsearch_1 | at org.elasticsearch.bootstrap.Bootstrap$5.(Bootstrap.java:212) ~[elasticsearch-6.7.1.jar:6.7.1]
elasticsearch_1 | at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:212) ~[elasticsearch-6.7.1.jar:6.7.1]
elasticsearch_1 | at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:333) ~[elasticsearch-6.7.1.jar:6.7.1]
elasticsearch_1 | at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159) ~[elasticsearch-6.7.1.jar:6.7.1]
elasticsearch_1 | ... 6 more

SamuelHassine pushed a commit that referenced this issue Jul 5, 2019
#109 Use workers to import, #113 Fix, #85 More Observables types
@SamuelHassine
Copy link
Member

Hello there,

We refactor the volumes configuration of Docker compose. We come back to a more classic configuration compliant with most of cloud platforms.

Could you please clear all your config (stop Docker daemon, rm -R /var/lib/docker/*, start Docker daemon) and start fresh (git pull this repository and docker-compose up) ?

@soreno123
Copy link

soreno123 commented Jul 5, 2019

Hello @SamuelHassine, i followed your advice and now is working, i can correctly login in the platform.
Thanks!

@SamuelHassine
Copy link
Member

@soreno123 : Yes sorry, we are aware of this bug #118.

@SamuelHassine SamuelHassine added question Further information is requested solved use to identify issue that has been solved (must be linked to the solving PR) labels Jul 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

4 participants