Install Monitor failed
daoxuans opened this issue · 1 comments
I have a virtual machine, 16GB mem and 16 vCpus
i want to install monitor in this, and another vm deploy agent, Unfortunately,i always fail to install monitor , the log as below.
[?] Enter the password for logging into ElasticSearch: develop
[?] Confirm Password: develop
root@earth:~# dynamite monitor install --es-heap-size=5 --ls-heap-size=3 --ls-listen-addr 192.168.11.44 --kb-listen-addr 192.168.11.44 --kb-listen-port 5601
2020-08-07 02:09:17 DYNAMITE_CMD INFO | LOG LEVEL: 20
2020-08-07 02:09:17 DYNAMITE_CMD INFO | LOG FILE: /var/log/dynamite/dynamite-07-08-2020.log
[?] Enter the password for logging into ElasticSearch:
[?] Confirm Password:
2020-08-07 02:09:20 ELASTICSEARCH ERROR | Could not resolve ES_PATH_CONF environment variable. Is ElasticSearch installed?
2020-08-07 02:09:20 LOGSTASH ERROR | Could not resolve LS_PATH_CONF environment variable. Is Logstash installed?
2020-08-07 02:09:20 ELASTICSEARCH ERROR | Could not resolve ES_PATH_CONF environment variable. Is ElasticSearch installed?
2020-08-06 18:09:22 DOWNLOAD_MANAGER | 2.55 MB/s |#############################| (elasticsearch-7.2.0.tar.gz) Time: 0:02:11
2020-08-06 18:11:40 DOWNLOAD_MANAGER | 1.36 MB/s |#####################################| (java-11.0.2.tar.gz) Time: 0:02:18
useradd: user 'dynamite' already exists
2020-08-07 02:14:01 ELASTICSEARCH INFO | Creating ElasticSearch installation, configuration, and logging directories.
2020-08-07 02:14:02 ELASTICSEARCH INFO | Updating ElasticSearch default configuration path [/etc/dynamite/elasticsearch/]
2020-08-07 02:14:02 ELASTICSEARCH INFO | Updating ElasticSearch default home path [/opt/dynamite/elasticsearch/]
2020-08-07 02:14:02 ELASTICSEARCH INFO | Overwriting default configuration.
2020-08-07 02:14:02 ELASTICSEARCH INFO | Setting up JVM default heap settings [5GB]
2020-08-07 02:14:02 ELASTICSEARCH INFO | Setting up Max File Handles [65535] VM Max Map Count [262144]
2020-08-07 02:14:02 ELASTICSEARCH INFO | Creating certificate keystore.
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
2020-08-07 02:14:10 ELASTICSEARCH WARNING | An issue occurred while attempting to start.
2020-08-07 02:14:13 ELASTICSEARCH WARNING | An issue occurred while attempting to start.
2020-08-07 02:14:16 ELASTICSEARCH INFO | [Attempt: 3] Starting ElasticSearch on PID [1995]
2020-08-07 02:14:16 ELASTICSEARCH INFO | Waiting for ElasticSearch API to become accessible.
2020-08-07 02:14:21 ELASTICSEARCH INFO | Waiting for ElasticSearch API to become accessible.
2020-08-07 02:14:26 ELASTICSEARCH INFO | ElasticSearch API is up.
2020-08-07 02:14:31 ELASTICSEARCH INFO | Bootstrapping passwords.
2020-08-07 02:14:34 ELASTICSEARCH ERROR | General exception while resetting Elasticsearch password.
2020-08-07 02:14:34 ELASTICSEARCH ERROR | Failed to bootstrap password.
2020-08-07 02:14:34 ELASTICSEARCH ERROR | General error occurred while attempting to bootstrap ElasticSearch passwords.
2020-08-07 02:14:34 DYNAMITE_CMD CRITICAL | Fatal error. Add --verbose flag for details. Exiting.
I try it again:
2020-08-07 02:30:21 KIBANA INFO | Updating Kibana default configuration path [/etc/dynamite/kibana/]
2020-08-07 02:30:21 KIBANA INFO | Updating Kibana default home path [/opt/dynamite/kibana/]
2020-08-07 02:30:21 KIBANA INFO | Updating Kibana default log path [/var/log/dynamite/kibana/]
2020-08-07 02:30:21 KIBANA INFO | Overwriting default configuration.
2020-08-07 02:30:21 KIBANA INFO | Installing Kibana Dashboards
2020-08-07 02:30:21 KIBANA INFO | Waiting for ElasticSearch to become accessible.
2020-08-07 02:30:21 KIBANA INFO | Starting ElasticSearch.
2020-08-07 02:30:21 ELASTICSEARCH INFO | ElasticSearch is already running on PID [1995]
2020-08-07 02:30:21 KIBANA INFO | ElasticSearch API is up.
2020-08-07 02:30:21 KIBANA INFO | Sleeping for 5 seconds, while ElasticSearch API finishes booting.
2020-08-07 02:30:26 KIBANA INFO | Optimizing Kibana Libraries.
2020-08-07 02:30:49 KIBANA INFO | Starting Kibana.
2020-08-07 02:30:54 KIBANA INFO | [Attempt: 1] Starting Kibana on PID [3342]
2020-08-07 02:30:54 KIBANA INFO | Kibana API is up.
2020-08-07 02:30:54 KIBANA INFO | Sleeping for 10 seconds, while Kibana API finishes booting.
2020-08-07 02:31:05 KIBANA INFO | [Attempt 1] Attempting to install dashboards/visualizations.
[-] Failed to create ElastiFlow objects - [Note: Unnecessary use of -X or --request, POST is already inferred.
- Uses proxy env variable http_proxy == 'http://192.168.11.70:808'
- Trying 192.168.11.70:808...
- TCP_NODELAY set
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Connected to 192.168.11.70 (192.168.11.70) port 808 (#0) - Server auth using Basic with user 'elastic'
POST http://192.168.11.44:5601/api/saved_objects/_import HTTP/1.1
Host: 192.168.11.44:5601
Authorization: Basic ZWxhc3RpYzpkZXZlbG9w
User-Agent: curl/7.68.0
Accept: /
Proxy-Connection: Keep-Alive
kbn-xsrf: true
Content-Length: 3578604
Content-Type: multipart/form-data; boundary=------------------------dc0a62586229f500
Expect: 100-continue
- Done waiting for 100-continue
0 3494k 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0} [65536 bytes data] - We are completely uploaded and fine
- Mark bundle as not supporting multiuse
< HTTP/1.1 100 Continue - Mark bundle as not supporting multiuse
< HTTP/1.1 503 Service Unavailable
< retry-after: 30
< content-type: text/html; charset=utf-8
< cache-control: no-cache
< content-length: 30
< connection: close
< Date: Thu, 06 Aug 2020 18:31:05 GMT
<
{ [30 bytes data]
100 3494k 100 30 100 3494k 22 2627k 0:00:01 0:00:01 --:--:-- 2627k - Closing connection 0
===============================================================
- if i fail to install monitor, the install process will download tar.gz again and again, can you check md5 to avoid repeated downloads?
What is the behavior if you try to start the monitor at this point?
FYI - We're looking for a better way to install Kibana Dashboards. The current method relies on the Kibana API which has been finicky during the best of times.