Okey, remove that. and restart kibana
and then status is like this
[root@localhost kibana]# systemctl status kibana -l
● kibana.service - Kibana
Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled)
Active: active (running) since 수 2019-05-29 17:14:17 KST; 8s ago
Main PID: 12061 (node)
Tasks: 11
CGroup: /system.slice/kibana.service
└─12061 /usr/share/kibana/bin/../node/bin/node --no-warnings --max-http-header-size=65536 /usr/share/kibana/bin/../src/cli -c /etc/kibana/kibana.yml
5월 29 17:14:23 localhost.localdomain kibana[12061]: {"type":"log","@timestamp":"2019-05-29T08:14:23Z","tags":["warning","elasticsearch","admin"],"pid":12061,"message":"No living connections"}
5월 29 17:14:23 localhost.localdomain kibana[12061]: {"type":"log","@timestamp":"2019-05-29T08:14:23Z","tags":["warning","elasticsearch","admin"],"pid":12061,"message":"Unable to revive connection: https://192.168.0.92:9200/"}
5월 29 17:14:23 localhost.localdomain kibana[12061]: {"type":"log","@timestamp":"2019-05-29T08:14:23Z","tags":["warning","elasticsearch","admin"],"pid":12061,"message":"No living connections"}
5월 29 17:14:23 localhost.localdomain kibana[12061]: {"type":"log","@timestamp":"2019-05-29T08:14:23Z","tags":["reporting","warning"],"pid":12061,"message":"Could not retrieve cluster settings, because of No Living connections"}
5월 29 17:14:23 localhost.localdomain kibana[12061]: {"type":"log","@timestamp":"2019-05-29T08:14:23Z","tags":["warning","task_manager"],"pid":12061,"message":"PollError No Living connections"}
5월 29 17:14:23 localhost.localdomain kibana[12061]: {"type":"log","@timestamp":"2019-05-29T08:14:23Z","tags":["warning","maps"],"pid":12061,"message":"Error scheduling telemetry task, received NotInitialized: Tasks cannot be scheduled until after task manager is initialized!"}
5월 29 17:14:23 localhost.localdomain kibana[12061]: {"type":"log","@timestamp":"2019-05-29T08:14:23Z","tags":["warning","telemetry"],"pid":12061,"message":"Error scheduling task, received NotInitialized: Tasks cannot be scheduled until after task manager is initialized!"}
5월 29 17:14:24 localhost.localdomain kibana[12061]: {"type":"log","@timestamp":"2019-05-29T08:14:24Z","tags":["debug","legacy-proxy"],"pid":12061,"message":""getConnections" has been called."}
5월 29 17:14:25 localhost.localdomain kibana[12061]: {"type":"log","@timestamp":"2019-05-29T08:14:25Z","tags":["warning","elasticsearch","admin"],"pid":12061,"message":"Unable to revive connection: https://192.168.0.92:9200/"}
5월 29 17:14:25 localhost.localdomain kibana[12061]: {"type":"log","@timestamp":"2019-05-29T08:14:25Z","tags":["warning","elasticsearch","admin"],"pid":12061,"message":"No living connections"}
i have a question for here why machine use admin user??
["warning","elasticsearch","admin"]
before i was using this
$ /usr/share/elasticsearch/bin/elasticsearch-setup-passwords auto
And i was folloe this eLearning
Fundamentals of Securing Elasticsearch