-
-
Notifications
You must be signed in to change notification settings - Fork 97
two questions: blacktop/elasticsearch exits automatically && the uploaded files' status are in pending all the time #19
Comments
I will look into elasticsearch later today. It might be pending because you aren't using one of the hypervisors currently supported by this docker image as mentioned in the beginning of the README? |
this might be related to #18 |
what do you see when you run |
Hi wuliqilin I think your issue may be related to something simlar that I brought up in isssue #30 I used a similar workaround of updating the elasticsearch image, and I believe this has no impact. |
I am having a similar problem as described here. I am using macOS High Sierra with the docker-cuckoo 2.0. I run with docker-compose up -d and elasticsearch_1 and cuckoo_1 images keep exiting. $ docker ps -a And looking at the logs: $ docker-compose logs |
I tried with image blacktop/elasticsearch:6.5 and also with some environments like "ES_JAVA_OPTS=-Xms4g -Xmx4 g". However, the behaviour is the same, elasticsearch exits without any error. |
Any updates on how to resolve? I am having the same issue as @amnorcross. docker ps -a Also docker-compose logs -f cuckoo shows The submitted samples show up as pending. |
I'm curious if anyone came around to resolving this? I'm currently having this issue and all my samples are showing up as pending. |
Under Linux Environment:
after execute cmd: docker-compose up -d , the service blacktop/elasticsearch will exit automatically after a few seconds. In order to run successfully, had to replace blacktop/elsaticsearch with elasticsearch in yml. Then it worked. but brings the next problem. What impact does this bring? Or Which step did I wrong?
when I start all the services, then upload a file to the cuckoo. the status of the file will always be in pending. Did not switch to running,did not produce analysis results. I can not get what I want.
Can you solve my problem? Very Thanks~
The text was updated successfully, but these errors were encountered: