본문 바로가기

카테고리 없음

elastic search 설치

반응형

시팔 새벽 3시 반이 넘었다.

 


sudo docker rmi $(sudo docker images -a -q)
sudo docker volume rm es-config
docker volume create --name es-config
종료된 컨테이너 조회
sudo docker ps -a -f status=exited

sudo docker rm $(sudo docker ps -a -f status=exited -q)

sudo docker network create elastic

Enterprise: sudo docker pull docker.elastic.co/enterprise-search/enterprise-search:8.3.2
Elastic search: sudo docker pull docker.elastic.co/elasticsearch/elasticsearch:8.3.2
kibana: sudo docker pull docker.elastic.co/kibana/kibana:8.3.2

 

docker run --name es-node01 --net elastic -p 9200:9200 -p 9300:9300 -t docker.elastic.co/elasticsearch/elasticsearch:8.3.2



sudo docker volume list
sudo docker volume inspect es-config
[
    {
        "CreatedAt": "2022-03-08T16:08:55Z",
        "Driver": "local",
        "Labels": {},
        "Mountpoint": "/var/lib/docker/volumes/es-config/_data",
        "Name": "es-config",
        "Options": {},
        "Scope": "local"
    }
]


<Enterprise 호환 es 실행> - https://www.elastic.co/guide/en/enterprise-search/current/docker.html
 
sudo docker run --name es01 --net elastic -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" --privileged=true --volume es-config:/usr/share/elasticsearch/config:rw -it docker.elastic.co/elasticsearch/elasticsearch:8.0.1
sudo docker run --name es01 --net elastic -p 9200:9200 -p 9300:9300 -it docker.elastic.co/elasticsearch/elasticsearch:8.0.1

docker run --name es01 --net elastic -p 9200:9200 -p 9300:9300 -it docker.elastic.co/elasticsearch/elasticsearch:8.1.2



sudo docker logs kibana | grep 'public_address'
sudo docker  inspect ipadress 확인
172.19.0.3


sudo docker logs es01 | grep 'publish_address'
 {172.19.0.2:9300}
"publish_address {172.19.0.2:9200},

sudo docker run --name kibana --net elastic -p 5601:5601 --env "ENTERPRISESEARCH_HOST=http://203.245.157.104:3002" -it docker.elastic.co/kibana/kibana:8.0.1
sudo docker run --name kib-01 --net elastic -p 5601:5601 docker.elastic.co/kibana/kibana:8.0.1
enterpriseSearch.host: 'http://172.19.0.4:3002'

server.publicBaseUrl is missing and should be configured when running in a production environment. Some features may not behave correctly. See the documentation.
server.publicBaseUrl: "http://203.245.157.104:5601"
openssl rand -hex 32

sudo firewall-cmd --permanent --zone=public --add-port=3002/tcp
sudo ufw allow 3002


sudo docker run --name enterprise-search --net elastic -p 3002:3002 --volume es-config:/usr/share/enterprise-search/es-config:ro \
--env "secret_management.encryption_keys=['40fd6404b8ab12431f9f4216d3932e064b915a8959c3a417bbd39e87ac2b0bf3']" \
--env "allow_es_settings_modification=true" \
--env "elasticsearch.host=https://elastic:ppp123@172.19.0.2:9200" \
--env "elasticsearch.username=elastic" --env "elasticsearch.password=ppp123" \
--env "elasticsearch.ssl.enabled=true" --env "allow_es_settings_modification=true" \
--env "elasticsearch.ssl.certificate_authority=/usr/share/enterprise-search/es-config/certs/http_ca.crt" \
--env "kibana.external_url=http://172.19.0.3:5601" \
"docker.elastic.co/enterprise-search/enterprise-search:8.0.1" 





!XX--enable-read-only-mode

http://203.245.157.104:5601/app/enterprise_search/overview

enterpriseSearch.host: 'http://172.19.0.4:3002'
https://203.245.157.104:9200/_xpack?accept_enterprise=true


Add your Enterprise Search host URL to your Kibana configuration
In your config/kibana.yml file, set enterpriseSearch.host to the URL of your Enterprise Search instance. For example:

enterpriseSearch.host: 'http://localhost:3002'
Step 22
Reload your Kibana instance
Restart Kibana to pick up the configuration changes from the previous step.

Step 33
Troubleshooting issues


Enterprise Search and Kibana are on different Elasticsearch clusters

[2022-03-08T17:24:46.578+00:00][7][2000][app-server][WARN]: [pre-flight] 
Unexpected HTTP response from Elasticsearch backend: {"error":{"root_cause":[{"type":"security_exception","reason":"unable to authenticate user [elastic] 
for REST request [/]","header":{"WWW-Authenticate":["Basic realm=\"security\" charset=\"UTF-8\"","Bearer realm=\"security\"","ApiKey"]}}],"type":"security_exception","reason":
"unable to authenticate user [elastic] for REST request [/]","header":{"WWW-Authenticate":["Basic realm=\"security\" charset=\"UTF-8\"","Bearer realm=\"security\"","ApiKey"]}},"status":401}
. Make sure Elasticsearch is running and healthy.





키바나 익명계정 생성
https://www.elastic.co/guide/en/kibana/current/kibana-authentication.html

http://203.245.157.104:5601/?code=969774

server.publicBaseUrl is missing and should be configured when running in a production environment. Some features may not behave correctly. See the documentation.

sudo docker run \
--name "elasticsearch" \
--network "elastic" \
--publish "9200:9200" \
--volume "es-config:/usr/share/elasticsearch/config:rw" \
--interactive \
--tty \
--rm \
"docker.elastic.co/elasticsearch/elasticsearch:8.0.1"

반응형