Comments (17)
Hopefully the referenced pull request clears up some of these issues. The setup script seems to hang for me, I suspect it should be doing more work past the output below.
Environment:
- Docker version 18.09.1, build 4c52b90
- Ubuntu 18.10
$ docker-compose -f setup.yml up
WARNING: Found orphan containers (setup_kibana, setup_logstash) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
Starting stack-docker_setup_1 ... done
Attaching to stack-docker_setup_1
setup_1 | Found orphan containers (stack-docker_setup_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
Recreating setup_elasticsearch ... done
Attaching to setup_elasticsearch
setup_1 | setup_elasticsearch | Determining if x-pack is installed...
setup_1 | setup_elasticsearch | === CREATE Keystore ===
setup_1 | setup_elasticsearch | Elastic password is: 4F7BBILOZavEQjQyLIN2Cg==
setup_1 | setup_elasticsearch | Created elasticsearch keystore in /usr/share/elasticsearch/config
setup_1 | setup_elasticsearch | Setting bootstrap.password...
setup_1 | setup_elasticsearch | === CREATE SSL CERTS ===
setup_1 | setup_elasticsearch | Remove old ca zip...
setup_1 | setup_elasticsearch | Creating docker-cluster-ca.zip...
setup_1 | setup_elasticsearch | CA directory exists, removing...
setup_1 | setup_elasticsearch | Unzip ca files...
setup_1 | setup_elasticsearch | Archive: /config/ssl/docker-cluster-ca.zip
setup_1 | setup_elasticsearch | creating: /config/ssl/ca/
setup_1 | setup_elasticsearch | inflating: /config/ssl/ca/ca.crt
setup_1 | setup_elasticsearch | inflating: /config/ssl/ca/ca.key
setup_1 | setup_elasticsearch | Remove old docker-cluster.zip zip...
setup_1 | setup_elasticsearch | Create cluster certs zipfile...
setup_1 | setup_elasticsearch | Unzipping cluster certs zipfile...
setup_1 | setup_elasticsearch | Archive: /config/ssl/docker-cluster.zip
setup_1 | setup_elasticsearch | creating: /config/ssl/docker-cluster/elasticsearch/
setup_1 | setup_elasticsearch | inflating: /config/ssl/docker-cluster/elasticsearch/elasticsearch.crt
setup_1 | setup_elasticsearch | inflating: /config/ssl/docker-cluster/elasticsearch/elasticsearch.key
setup_1 | setup_elasticsearch | creating: /config/ssl/docker-cluster/kibana/
setup_1 | setup_elasticsearch | inflating: /config/ssl/docker-cluster/kibana/kibana.crt
setup_1 | setup_elasticsearch | inflating: /config/ssl/docker-cluster/kibana/kibana.key
setup_1 | setup_elasticsearch | creating: /config/ssl/docker-cluster/logstash/
setup_1 | setup_elasticsearch | inflating: /config/ssl/docker-cluster/logstash/logstash.crt
setup_1 | setup_elasticsearch | inflating: /config/ssl/docker-cluster/logstash/logstash.key
setup_1 | setup_elasticsearch | Move logstash certs to logstash config dir...
setup_1 | setup_elasticsearch | Move kibana certs to kibana config dir...
setup_1 | setup_elasticsearch | Move elasticsearch certs to elasticsearch config dir...
setup_1 | setup_elasticsearch exited with code 0
setup_1 | Found orphan containers (stack-docker_setup_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
Recreating elasticsearch ... done
Recreating setup_kibana ... done
Recreating setup_logstash ... done
Attaching to setup_kibana, setup_logstash
setup_1 | setup_kibana | -rw-rw-r-- 1 root root 1200 Jan 30 12:12 /usr/share/kibana/config/ca/ca.crt
setup_1 | setup_logstash | -rw-rw-r-- 1 root root 1200 Jan 30 12:12 /usr/share/logstash/config/ca/ca.crt
from stack-docker.
Hopefully the referenced pull request clears up some of these issues. The setup script seems to hang for me, I suspect it should be doing more work past the output below.
Environment:
- Docker version 18.09.1, build 4c52b90
- Ubuntu 18.10
$ docker-compose -f setup.yml up WARNING: Found orphan containers (setup_kibana, setup_logstash) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. Starting stack-docker_setup_1 ... done Attaching to stack-docker_setup_1 setup_1 | Found orphan containers (stack-docker_setup_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. Recreating setup_elasticsearch ... done Attaching to setup_elasticsearch setup_1 | setup_elasticsearch | Determining if x-pack is installed... setup_1 | setup_elasticsearch | === CREATE Keystore === setup_1 | setup_elasticsearch | Elastic password is: 4F7BBILOZavEQjQyLIN2Cg== setup_1 | setup_elasticsearch | Created elasticsearch keystore in /usr/share/elasticsearch/config setup_1 | setup_elasticsearch | Setting bootstrap.password... setup_1 | setup_elasticsearch | === CREATE SSL CERTS === setup_1 | setup_elasticsearch | Remove old ca zip... setup_1 | setup_elasticsearch | Creating docker-cluster-ca.zip... setup_1 | setup_elasticsearch | CA directory exists, removing... setup_1 | setup_elasticsearch | Unzip ca files... setup_1 | setup_elasticsearch | Archive: /config/ssl/docker-cluster-ca.zip setup_1 | setup_elasticsearch | creating: /config/ssl/ca/ setup_1 | setup_elasticsearch | inflating: /config/ssl/ca/ca.crt setup_1 | setup_elasticsearch | inflating: /config/ssl/ca/ca.key setup_1 | setup_elasticsearch | Remove old docker-cluster.zip zip... setup_1 | setup_elasticsearch | Create cluster certs zipfile... setup_1 | setup_elasticsearch | Unzipping cluster certs zipfile... setup_1 | setup_elasticsearch | Archive: /config/ssl/docker-cluster.zip setup_1 | setup_elasticsearch | creating: /config/ssl/docker-cluster/elasticsearch/ setup_1 | setup_elasticsearch | inflating: /config/ssl/docker-cluster/elasticsearch/elasticsearch.crt setup_1 | setup_elasticsearch | inflating: /config/ssl/docker-cluster/elasticsearch/elasticsearch.key setup_1 | setup_elasticsearch | creating: /config/ssl/docker-cluster/kibana/ setup_1 | setup_elasticsearch | inflating: /config/ssl/docker-cluster/kibana/kibana.crt setup_1 | setup_elasticsearch | inflating: /config/ssl/docker-cluster/kibana/kibana.key setup_1 | setup_elasticsearch | creating: /config/ssl/docker-cluster/logstash/ setup_1 | setup_elasticsearch | inflating: /config/ssl/docker-cluster/logstash/logstash.crt setup_1 | setup_elasticsearch | inflating: /config/ssl/docker-cluster/logstash/logstash.key setup_1 | setup_elasticsearch | Move logstash certs to logstash config dir... setup_1 | setup_elasticsearch | Move kibana certs to kibana config dir... setup_1 | setup_elasticsearch | Move elasticsearch certs to elasticsearch config dir... setup_1 | setup_elasticsearch exited with code 0 setup_1 | Found orphan containers (stack-docker_setup_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. Recreating elasticsearch ... done Recreating setup_kibana ... done Recreating setup_logstash ... done Attaching to setup_kibana, setup_logstash setup_1 | setup_kibana | -rw-rw-r-- 1 root root 1200 Jan 30 12:12 /usr/share/kibana/config/ca/ca.crt setup_1 | setup_logstash | -rw-rw-r-- 1 root root 1200 Jan 30 12:12 /usr/share/logstash/config/ca/ca.crt
docker-compose -f setup.yml up --> This helped me setup everything. Thank you!
from stack-docker.
This is, Setup is dosent creating de .keystore in all diretorys.
I will try to copy then to others.
from stack-docker.
I had an issue with this today. My problem was with autocrlf. I had cloned down the repo with autocrlf=true, and that caused the compose to hang and not create any of the keystores because of the new line characters in the shell scripts. When I set "git config core.autocrlf false" and re-cloned, then it started working for me.
Edit: Forgot to mention, for the issue creator's original issue. The issue is with kernel 3.10 not knowing what "CAP_AUDIT_READ" is. Source: #14
from stack-docker.
@perfecto25 I'm not sure what leads to this condition (I suspect it has something to do with the way docker-compose issues the mount command behind the scenes), but I was able to get this going by simply creating the directories, and then running docker-compose up -d
.
from stack-docker.
@perfecto25 I'm curious if there's some permission errors going on and the process isn't able to create those keystores at the defined locations.
from stack-docker.
I just got bit by the same issue. creating the auditbeat.keystore solved my problem. Thanks for posting that solution.
from stack-docker.
I'm curious if the auditbeat service failing to start cause auditd isn't enabled for the kernel is breaking something in the whole process...
from stack-docker.
I had the same issue and @fxdgear your solutions worked
from stack-docker.
Same problem here, can't start the auditbeat container.
uname -r
--> 4.15.0-43-generic
sudo apt-get install auditd audispd-plugins
sudo systemctl status auditd
--> active (running)
docker-compose up
--> ERROR: for auditbeat Cannot start service auditbeat: invalid mount config for type "bind": bind source path does not exist: /home/user/stack-docker/config/auditbeat/auditbeat.keystore
For the test, if I touch /home/user/stack-docker/config/auditbeat/auditbeat.keystore
and docker-compose up auditbeat
, the container manages to start, but I get: Exiting: could not initialize the keystore: keystore format doesn't match expected version: 'v1' got ''
, hence - it can read the file.. (but ofcourse, it's invalid, empty).
All other containers are up, no permission issue in the config folder..
any idea?
from stack-docker.
Can you run auditbeat outside a container?
from stack-docker.
I guess so... I've quickly did a test - installed auditbeat deb, and started the service. it's running. but haven't really tested thoroughly, @fxdgear please point me at specifics.
from stack-docker.
@oori soo I've found that auditbeat can be kinda troublesome on linux. I personally run arch and I don't have auditd enabled and as a result auditbeat fails to start. Since this project is designed to be for "demo purposes" I consider not seeing audit beat data on my linux laptop ok cause I know that auditbeat won't run.
I'd suggest maybe doing a clean up (containers, volumes, networks etc...) and trying again.
from stack-docker.
@mjpowersjr I'm guessing that something failed to start in Elasticsearch. And what's happening is the setup for kibana and logstash are hung cause elasticsearch isn't up (or hasn't come up yet).
If you like you can take a look at the referenced PR and give that a shot. Please note that the README has changed as well, so please read over that too.
from stack-docker.
Looks like this issue has not been resolved in master branch.
from stack-docker.
I'm getting the same issue as mjpowersjr
Managed to get it working at some point but its hit or miss. Any idea when this can be resolved?
from stack-docker.
Dont work, just copy the keystore... This is a error inside the development... I choose to use a total source, without docker.
https://www.digitalocean.com/community/tutorials/how-to-install-elasticsearch-logstash-and-kibana-elastic-stack-on-centos-7
from stack-docker.
Related Issues (20)
- Stuck at setup_logstash ca.cert HOT 6
- Not working with version 7.4.0. HOT 5
- Cannot launch stack on Ubuntu; chdir to cwd permission denied HOT 1
- Kibana Reporting failing HOT 1
- Issue in sudo docker-compose -f setup.yml up
- Logstash created pipeline in Kibana Management doesn't work, while same pipeline work as main HOT 1
- Kibana 6.6.0 crashes with Fatal error after initial setup HOT 2
- can't open './scripts/setup.sh': No such file or directory HOT 1
- Fails on Windows Toolbox due to win paths of the secrets
- Ok but how in the dock do I find the hash in "TAG=6.0.0-beta1-3eab5b40"
- docker-compose -f setup.yml up does not work on Windows 10 HOT 9
- ~ HOT 1
- Fails on arm64 HOT 1
- 'docker-compose -f setup.yml' fails one container HOT 1
- elasticsearch.keystore Not Created HOT 2
- Authentication error HOT 1
- The Docker-compose.yml for 3 node elastic cluster HOT 2
- Elasticsearch 7.x support HOT 11
- Implementing Winlogbeat for Stack-Docker
- Add support for Elastic App-Search
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from stack-docker.