Hi Tomasz, Brian,
I am trying to build the dev instance using the latest docker images but it
only starts sdc-init-es. Docker ps shows me only one container running
I have taken the latest AUTO.json and running below command.
/data/scripts/docker_run.sh -r latest
Please advise. Also attached docklog extract for the es container
Console output of above command:
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
WARNING! Your password will be stored unencrypted in
/home/ubuntu/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store
Login Succeeded
Performing old dockers cleanup
c522ba5bac49
43cfdad7f8e1
create dir
/data/onap/cert
docker run sdc-elasticsearch...
pulling code
latest: Pulling from onap/sdc-elasticsearch
Digest: sha256:dbc677e7d4bde99f239a8279c9e3cae0aec132a5652fd980d12925b469770859
Status: Image is up to date for
nexus3.onap.org:10001/onap/sdc-elasticsearch:latest
fc065e3e2f0c84ea39504d6c93d7bf9822a01ccb53f52520b5ac7b36046832a8
please wait while ES is starting...
Monitor sdc-es Docker
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:--
0curl: (7) Failed to connect to 192.168.0.7 port 9200: Connection refused
Sleep: 20 seconds before testing if sdc-es DOCKER is up. Total wait time up now
is: 860 seconds. Timeout is: 900 seconds
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:--
0curl: (7) Failed to connect to 192.168.0.7 port 9200: Connection refused
Sleep: 20 seconds before testing if sdc-es DOCKER is up. Total wait time up now
is: 880 seconds. Timeout is: 900 seconds
TIME OUT: DOCKER was NOT fully started in 900 seconds... Could cause problems
...
docker run sdc-init-elasticsearch...
pulling code
latest: Pulling from onap/sdc-init-elasticsearch
4fe2ade4980c: Already exists
6fc58a8d4ae4: Already exists
ef87ded15917: Already exists
086229c56d40: Already exists
73418a619d53: Pull complete
516c2cab0fb4: Pull complete
4f0992057fa3: Pull complete
7a1ccb2d000f: Pull complete
Digest: sha256:8ca449879eac9067d690adc0d8927540a040d9f5f9cf5291148623d1bca19d95
Status: Downloaded newer image for
nexus3.onap.org:10001/onap/sdc-init-elasticsearch:latest
Running sdc-init-es
Regards,
Atif
From: Syed Atif Husain
Sent: Tuesday, May 28, 2019 11:42 PM
To: [email protected]; [email protected]; [email protected]
Subject: RE: [onap-discuss] [sdc] Error in local sdc setup - image pull fails
Thanks. It went past that with Tomasz's suggestion of upgrading to docker
18.06.3-ce
But it has failed now due to space issue. My Ubuntu VM had 10 GB but apparently
we are gonna need a bigger boat!
Do we know what size VM is enough for SDC local setup?
Regards,
Atif
From: [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>> On Behalf Of
Brian
Sent: Tuesday, May 28, 2019 11:17 PM
To: [email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>; Syed Atif Husain
<[email protected]<mailto:[email protected]>>
Subject: Re: [onap-discuss] [sdc] Error in local sdc setup - image pull fails
[**EXTERNAL EMAIL**]
I add insecure registries to the docker daemon config and restart the docker
daemon.
I'm not familiar with the file you listed but there might be multiple ways to
get docker daemon to ignore the insecure registry.
Brian
From: [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>> On Behalf Of
Golabek, Tomasz (Nokia - PL/Wroclaw)
Sent: Tuesday, May 28, 2019 7:18 AM
To: Syed Atif Husain <[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>
Subject: Re: [onap-discuss] [sdc] Error in local sdc setup - image pull fails
Hi,
can You try to reinstall your docker to version 18.03.1.ce and retry the
process? I think that this problem refers to your environment setup or network
issue associated with proxy settings (if you are using any).
Best regards
Tomasz Golabek
________________________________
From: Syed Atif Husain <[email protected]<mailto:[email protected]>>
Sent: Tuesday, May 28, 2019 1:07:46 PM
To: [email protected]<mailto:[email protected]>; Golabek,
Tomasz (Nokia - PL/Wroclaw)
Cc: [email protected]<mailto:[email protected]>
Subject: RE: [onap-discuss] [sdc] Error in local sdc setup - image pull fails
Hi Tomasz,
I tried with 1.4.0 but it fails with the same error. In fact 1.4.1 is also
present in nexus3, it is unable to access nexus3 itself.
I got below error when I ran the build with -X option
Caused by: io.fabric8.maven.docker.access.hc.http.HttpRequestException: v1 ping
attempt failed with error: Get
https://nexus3.onap.org:10001/v1/_ping<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__nexus3.onap.org-3A10001_v1_-5Fping%26d%3DDwQF-g%26c%3DLFYZ-o9_HUMeMTSQicvjIg%26r%3De3d1ehx3DI5AoMgDmi2Fzw%26m%3D0chVOLyT_sf5P_6q0H1BkKlKCOX4auWx0dNlBNKeenY%26s%3DG0tzOjh-U2PF1mxn5xtLBfiOEseZ6BaQXZCCgZssRcg%26e%3D&data=02%7C01%7CSyed_ah%40infosys.com%7C96c4f4326b794afb406308d6e36f0315%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636946463287481498&sdata=46k10xC4Wz76eglDRXMPwEYzWdjgru3Zb1gvC865Wgc%3D&reserved=0>:
dial tcp: i/o timeout. If this private registry supports only HTTP or HTTPS
with an unknown CA certificate, please add `--insecure-registry
nexus3.onap.org:10001` to the daemon's arguments. In the case of HTTPS, if you
have access to the registry's CA certificate, no need for the flag; simply
place the CA certificate at /etc/docker/certs.d/nexus3.onap.org:10001/ca.crt
(Internal Server Error: 500)
at
io.fabric8.maven.docker.access.hc.ApacheHttpClientDelegate$StatusCodeCheckerResponseHandler.handleResponse(ApacheHttpClientDelegate.java:177)
I tried adding `--insecure-registry nexus3.onap.org:10001 to the file
/opt/config/nexus_docker_repo.txt but that also didn't help.
Regards,
Atif
From: [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>> On Behalf Of
Golabek, Tomasz (Nokia - PL/Wroclaw)
Sent: Tuesday, May 28, 2019 5:54 PM
To: [email protected]<mailto:[email protected]>; Syed Atif
Husain <[email protected]<mailto:[email protected]>>
Cc: [email protected]<mailto:[email protected]>
Subject: Re: [onap-discuss] [sdc] Error in local sdc setup - image pull fails
[**EXTERNAL EMAIL**]
Hi,
go to the
https://nexus3.onap.org<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__apc01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fnexus3.onap.org-26data-3D02-257C01-257CSyed-5Fah-2540infosys.com-257Cfa283c6f69404244a37108d6e341d1de-257C63ce7d592f3e42cda8ccbe764cff5eb6-257C1-257C0-257C636946269195632719-26sdata-3DzTS6Z2HMU1xa1Gs9u2zMdfHFupf0gLodQAPNUj-252BlihU-253D-26reserved-3D0%26d%3DDwMF-g%26c%3DLFYZ-o9_HUMeMTSQicvjIg%26r%3De3d1ehx3DI5AoMgDmi2Fzw%26m%3D0chVOLyT_sf5P_6q0H1BkKlKCOX4auWx0dNlBNKeenY%26s%3DCkpEiVW0Bc222CXHzfHRJiTppxxVqeGJbX7_NOVCyPo%26e%3D&data=02%7C01%7CSyed_ah%40infosys.com%7C96c4f4326b794afb406308d6e36f0315%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636946463287481498&sdata=f%2FAGhjh3WE1%2BRTnfOHTyLsV1zCQ7y6pAzh0bzgjA5rk%3D&reserved=0>
and search for the base_sdc-jetty artifact. BTW version 1.4.0 of this package
is available and You can find it here:
https://nexus3.onap.org/#browse/search=keyword%3Dbase_sdc-jetty:c60bc6b9612f47d3cb32f1b12117e71c<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__apc01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fnexus3.onap.org-252F-2523browse-252Fsearch-253Dkeyword-25253Dbase-5Fsdc-2Djetty-253Ac60bc6b9612f47d3cb32f1b12117e71c-26data-3D02-257C01-257CSyed-5Fah-2540infosys.com-257Cfa283c6f69404244a37108d6e341d1de-257C63ce7d592f3e42cda8ccbe764cff5eb6-257C1-257C0-257C636946269195642713-26sdata-3DGsyXl6nmdTP4MuYO9-252BqNlcso8d0rbPKBXZY4DN-252FKcFE-253D-26reserved-3D0%26d%3DDwMF-g%26c%3DLFYZ-o9_HUMeMTSQicvjIg%26r%3De3d1ehx3DI5AoMgDmi2Fzw%26m%3D0chVOLyT_sf5P_6q0H1BkKlKCOX4auWx0dNlBNKeenY%26s%3DmfYEgfiSn2RDeLtivkMldbYfgPRe4s3Nd7xdjwlX2YE%26e%3D&data=02%7C01%7CSyed_ah%40infosys.com%7C96c4f4326b794afb406308d6e36f0315%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636946463287491493&sdata=5NEU33VAa%2FtQGE0bkcjIU%2BMVGDZKHjmcmECSJL8bdQo%3D&reserved=0>
Best regards
Tomasz Golabek
Software Developer
MN BOAM RD&Pz ONAP UI ML DEVOPS WRO 2 SG
Nokia
Contact number: +48 798 328 205
________________________________
From: [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>> on behalf of
Syed Atif Husain via Lists.Onap.Org
<[email protected]<mailto:[email protected]>>
Sent: Tuesday, May 28, 2019 4:38:52 AM
To: [email protected]<mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>
Subject: [onap-discuss] [sdc] Error in local sdc setup - image pull fails
Hi,
I am getting below error on building SDC in my local VM. I am trying to setup
local SDC on linux machine.
[ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.26.0:build
(generate-images) on project openecomp-sdc-docker-backend: Unable to pull
'onap/base_sdc-jetty:1.4.0' from registry 'nexus3.onap.org:10001' : Error
pulling image (1.4.0) from nexus3.onap.org:10001/onap/base_sdc-jetty, Server
error: 404 trying to fetch remote history for -> [Help 1]
I tried changing the version to other numbers but no luck. How do I check which
image version is available in nexus?
Regards,
Atif
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17364): https://lists.onap.org/g/onap-discuss/message/17364
Mute This Topic: https://lists.onap.org/mt/31816990/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Installing Cookbook Gems:
Compiling Cookbooks...
Converging 2 resources
Recipe: sdc-elasticsearch::ES_4_create_resources_template
* ruby_block[check_ElasticSearch_Cluster_Health] action
run[2019-05-31T01:42:26+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 9 attempt(s) left
[2019-05-31T01:42:28+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 8 attempt(s) left
[2019-05-31T01:42:30+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 7 attempt(s) left
[2019-05-31T01:42:32+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 6 attempt(s) left
[2019-05-31T01:42:34+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 5 attempt(s) left
[2019-05-31T01:42:36+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 4 attempt(s) left
[2019-05-31T01:42:38+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 3 attempt(s) left
[2019-05-31T01:42:40+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 2 attempt(s) left
[2019-05-31T01:42:42+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 1 attempt(s) left
[2019-05-31T01:42:44+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 0 attempt(s) left
================================================================================
Error executing action `run` on resource
'ruby_block[check_ElasticSearch_Cluster_Health]'
================================================================================
Errno::ENETUNREACH
------------------
Failed to open TCP connection to localhost:9200 (Network is unreachable -
connect(2) for "localhost" port 9200)
Cookbook Trace:
---------------
/root/chef-solo/cache/cookbooks/sdc-elasticsearch/recipes/ES_4_create_resources_template.rb:7:in
`block (2 levels) in from_file'
Resource Declaration:
---------------------
# In
/root/chef-solo/cache/cookbooks/sdc-elasticsearch/recipes/ES_4_create_resources_template.rb
1: ruby_block "check_ElasticSearch_Cluster_Health" do
2: block do
3: #tricky way to load this Chef::Mixin::ShellOut utilities
4: Chef::Resource::RubyBlock.send(:include, Chef::Mixin::ShellOut)
5: #curl_command =
"http://#{node['ipaddress']}:9200/_cluster/health?pretty=true"
6: curl_command =
"http://localhost:9200/_cluster/health?pretty=true";
7: resp = Net::HTTP.get_response URI.parse(curl_command)
8: stat = JSON.parse(resp.read_body)['status']
9:
10: case stat
11: when "green"
12: printf("\033[32m%s\n\033[0m", " ElasticSearch Cluster
status is green.")
13: when "yellow"
14: printf("\033[33m%s\n\033[0m", " ElasticSearch Cluster
status is yellow...")
15: when "red"
16: printf("\033[31m%s\n\033[0m", " ElasticSearch Cluster
status is red!")
17: end
18: end
19: retries 10
Compiled Resource:
------------------
# Declared in
/root/chef-solo/cache/cookbooks/sdc-elasticsearch/recipes/ES_4_create_resources_template.rb:1:in
`from_file'
ruby_block("check_ElasticSearch_Cluster_Health") do
action [:run]
default_guard_interpreter :default
block_name "check_ElasticSearch_Cluster_Health"
declared_type :ruby_block
cookbook_name "sdc-elasticsearch"
recipe_name "ES_4_create_resources_template"
block
#<Proc:0x0000000002a807d0@/root/chef-solo/cache/cookbooks/sdc-elasticsearch/recipes/ES_4_create_resources_template.rb:2>
retries 10
retry_delay 2
end
System Info:
------------
chef_version=13.5.3
platform=debian
platform_version=8.6
ruby=ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-linux]
program_name=chef-solo worker: ppid=504;start=01:42:25;
executable=/opt/chef/bin/chef-solo
[2019-05-31T01:42:46+00:00] INFO: Running queued delayed notifications before
re-raising exception
Running handlers:
[2019-05-31T01:42:46+00:00] ERROR: Running exception handlers
Running handlers complete
[2019-05-31T01:42:46+00:00] ERROR: Exception handlers complete
Chef Client failed. 0 resources updated in 20 seconds
[2019-05-31T01:42:46+00:00] FATAL: Stacktrace dumped to
/root/chef-solo/cache/chef-stacktrace.out
[2019-05-31T01:42:46+00:00] FATAL: Please provide the contents of the
stacktrace.out file if you file a bug report
[2019-05-31T01:42:46+00:00] ERROR:
ruby_block[check_ElasticSearch_Cluster_Health]
(sdc-elasticsearch::ES_4_create_resources_template line 1) had an error:
Errno::ENETUNREACH: Failed to open TCP connection to localhost:9200 (Network is
unreachable - connect(2) for "localhost" port 9200)
[2019-05-31T01:42:46+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef
run process exited unsuccessfully (exit code 1)
The environment variable HTTP_PROXY is discouraged. Use http_proxy.
[2019-05-31T01:42:47+00:00] INFO: Started chef-zero at chefzero://localhost:1
with repository at /root/chef-solo
One version per cookbook
[2019-05-31T01:42:47+00:00] INFO: Forking chef instance to converge...
Starting Chef Client, version 13.5.3
[2019-05-31T01:42:47+00:00] INFO: *** Chef 13.5.3 ***
[2019-05-31T01:42:47+00:00] INFO: Platform: x86_64-linux
[2019-05-31T01:42:47+00:00] INFO: Chef-client pid: 742
[2019-05-31T01:42:47+00:00] INFO: The plugin path /etc/chef/ohai/plugins does
not exist. Skipping...
[2019-05-31T01:42:48+00:00] INFO: Setting the run_list to
["role[elasticsearch]"] from CLI options
[2019-05-31T01:42:48+00:00] WARN: Run List override has been provided.
[2019-05-31T01:42:48+00:00] WARN: Original Run List: [role[elasticsearch]]
[2019-05-31T01:42:48+00:00] WARN: Overridden Run List:
[recipe[sdc-elasticsearch::ES_5_create_monitoring_template]]
[2019-05-31T01:42:48+00:00] INFO: Run List is
[recipe[sdc-elasticsearch::ES_5_create_monitoring_template]]
[2019-05-31T01:42:48+00:00] INFO: Run List expands to
[sdc-elasticsearch::ES_5_create_monitoring_template]
[2019-05-31T01:42:48+00:00] INFO: Starting Chef Run for fc065e3e2f0c
[2019-05-31T01:42:48+00:00] INFO: Running start handlers
[2019-05-31T01:42:48+00:00] INFO: Start handlers complete.
resolving cookbooks for run list:
["sdc-elasticsearch::ES_5_create_monitoring_template"]
[2019-05-31T01:42:48+00:00] INFO: Loading cookbooks [[email protected]]
[2019-05-31T01:42:48+00:00] INFO: Skipping removal of obsoleted cookbooks from
the cache
Synchronizing Cookbooks:
- sdc-elasticsearch (0.0.0)
Installing Cookbook Gems:
Compiling Cookbooks...
Converging 3 resources
Recipe: sdc-elasticsearch::ES_5_create_monitoring_template
* ruby_block[check_ElasticSearch_Cluster_Health] action
run[2019-05-31T01:42:48+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 9 attempt(s) left
[2019-05-31T01:42:50+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 8 attempt(s) left
[2019-05-31T01:42:52+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 7 attempt(s) left
[2019-05-31T01:42:54+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 6 attempt(s) left
[2019-05-31T01:42:56+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 5 attempt(s) left
[2019-05-31T01:42:58+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 4 attempt(s) left
[2019-05-31T01:43:00+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 3 attempt(s) left
[2019-05-31T01:43:02+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 2 attempt(s) left
[2019-05-31T01:43:04+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 1 attempt(s) left
[2019-05-31T01:43:06+00:00] INFO: Retrying execution of
ruby_block[check_ElasticSearch_Cluster_Health], 0 attempt(s) left
================================================================================
Error executing action `run` on resource
'ruby_block[check_ElasticSearch_Cluster_Health]'
================================================================================
Errno::ENETUNREACH
------------------
Failed to open TCP connection to localhost:9200 (Network is unreachable -
connect(2) for "localhost" port 9200)
Cookbook Trace:
---------------
/root/chef-solo/cache/cookbooks/sdc-elasticsearch/recipes/ES_5_create_monitoring_template.rb:7:in
`block (2 levels) in from_file'
Resource Declaration:
---------------------
# In
/root/chef-solo/cache/cookbooks/sdc-elasticsearch/recipes/ES_5_create_monitoring_template.rb
1: ruby_block "check_ElasticSearch_Cluster_Health" do
2: block do
3: #tricky way to load this Chef::Mixin::ShellOut utilities
4: Chef::Resource::RubyBlock.send(:include, Chef::Mixin::ShellOut)
5: #curl_command =
"http://#{node['ipaddress']}:9200/_cluster/health?pretty=true"
6: curl_command =
"http://localhost:9200/_cluster/health?pretty=true";
7: resp = Net::HTTP.get_response URI.parse(curl_command)
8: stat = JSON.parse(resp.read_body)['status']
9:
10: case stat
11: when "green"
12: printf("\033[32m%s\n\033[0m", " ElasticSearch Cluster
status is green.")
13: when "yellow"
14: printf("\033[33m%s\n\033[0m", " ElasticSearch Cluster
status is yellow...")
15: when "red"
16: printf("\033[31m%s\n\033[0m", " ElasticSearch Cluster
status is red!")
17: end
18: end
19: retries 10
Compiled Resource:
------------------
# Declared in
/root/chef-solo/cache/cookbooks/sdc-elasticsearch/recipes/ES_5_create_monitoring_template.rb:1:in
`from_file'
ruby_block("check_ElasticSearch_Cluster_Health") do
action [:run]
default_guard_interpreter :default
block_name "check_ElasticSearch_Cluster_Health"
declared_type :ruby_block
cookbook_name "sdc-elasticsearch"
recipe_name "ES_5_create_monitoring_template"
block
#<Proc:0x000000000188ba70@/root/chef-solo/cache/cookbooks/sdc-elasticsearch/recipes/ES_5_create_monitoring_template.rb:2>
retries 10
retry_delay 2
end
System Info:
------------
chef_version=13.5.3
platform=debian
platform_version=8.6
ruby=ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-linux]
program_name=chef-solo worker: ppid=737;start=01:42:47;
executable=/opt/chef/bin/chef-solo
[2019-05-31T01:43:08+00:00] INFO: Running queued delayed notifications before
re-raising exception
Running handlers:
[2019-05-31T01:43:08+00:00] ERROR: Running exception handlers
Running handlers complete
[2019-05-31T01:43:08+00:00] ERROR: Exception handlers complete
Chef Client failed. 0 resources updated in 20 seconds
[2019-05-31T01:43:08+00:00] FATAL: Stacktrace dumped to
/root/chef-solo/cache/chef-stacktrace.out
[2019-05-31T01:43:08+00:00] FATAL: Please provide the contents of the
stacktrace.out file if you file a bug report
[2019-05-31T01:43:08+00:00] ERROR:
ruby_block[check_ElasticSearch_Cluster_Health]
(sdc-elasticsearch::ES_5_create_monitoring_template line 1) had an error:
Errno::ENETUNREACH: Failed to open TCP connection to localhost:9200 (Network is
unreachable - connect(2) for "localhost" port 9200)
[2019-05-31T01:43:08+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef
run process exited unsuccessfully (exit code 1)
The environment variable HTTP_PROXY is discouraged. Use http_proxy.
[2019-05-31T01:43:09+00:00] INFO: Started chef-zero at chefzero://localhost:1
with repository at /root/chef-solo
One version per cookbook
[2019-05-31T01:43:09+00:00] INFO: Forking chef instance to converge...
Starting Chef Client, version 13.5.3
[2019-05-31T01:43:09+00:00] INFO: *** Chef 13.5.3 ***
[2019-05-31T01:43:09+00:00] INFO: Platform: x86_64-linux
[2019-05-31T01:43:09+00:00] INFO: Chef-client pid: 975
[2019-05-31T01:43:09+00:00] INFO: The plugin path /etc/chef/ohai/plugins does
not exist. Skipping...
[2019-05-31T01:43:10+00:00] INFO: Setting the run_list to
["role[elasticsearch]"] from CLI options
[2019-05-31T01:43:10+00:00] WARN: Run List override has been provided.
[2019-05-31T01:43:10+00:00] WARN: Original Run List: [role[elasticsearch]]
[2019-05-31T01:43:10+00:00] WARN: Overridden Run List:
[recipe[sdc-elasticsearch::ES_6_create_kibana_dashboard_virtualization]]
[2019-05-31T01:43:10+00:00] INFO: Run List is
[recipe[sdc-elasticsearch::ES_6_create_kibana_dashboard_virtualization]]
[2019-05-31T01:43:10+00:00] INFO: Run List expands to
[sdc-elasticsearch::ES_6_create_kibana_dashboard_virtualization]
[2019-05-31T01:43:10+00:00] INFO: Starting Chef Run for fc065e3e2f0c
[2019-05-31T01:43:10+00:00] INFO: Running start handlers
[2019-05-31T01:43:10+00:00] INFO: Start handlers complete.
resolving cookbooks for run list:
["sdc-elasticsearch::ES_6_create_kibana_dashboard_virtualization"]
[2019-05-31T01:43:10+00:00] INFO: Loading cookbooks [[email protected]]
[2019-05-31T01:43:10+00:00] INFO: Skipping removal of obsoleted cookbooks from
the cache
Synchronizing Cookbooks:
- sdc-elasticsearch (0.0.0)
Installing Cookbook Gems:
Compiling Cookbooks...
Converging 5 resources
Recipe: sdc-elasticsearch::ES_6_create_kibana_dashboard_virtualization
*
cookbook_file[/usr/share/elasticsearch/config/kibana_dashboard_virtualization.json]
action create
================================================================================
Error executing action `create` on resource
'cookbook_file[/usr/share/elasticsearch/config/kibana_dashboard_virtualization.json]'
================================================================================
Chef::Exceptions::FileNotFound
------------------------------
Cookbook 'sdc-elasticsearch' (0.0.0) does not contain a file at any of
these locations:
files/debian-8.6/kibana_dashboard_virtualization.json
files/debian/kibana_dashboard_virtualization.json
files/default/kibana_dashboard_virtualization.json
files/kibana_dashboard_virtualization.json
This cookbook _does_ contain:
['files/default/dashboard_BI-Dashboard.json','files/default/dashboard_Monitoring-Dashboared.json','files/default/visualization_JVM-used-CPU.json','files/default/visualization_JVM-used-Threads-Num.json','files/default/visualization_Show-all-distributed-services.json','files/default/visualization_host-used-CPU.json','files/default/visualization_host-used-Threads-Num.json','files/default/logging.yml','files/default/visualization_Show-all-certified-services-ampersand-resources-(per-day).json','files/default/visualization_Show-all-created-Resources-slash-Services-slash-Products.json','files/default/visualization_number-of-user-accesses.json','files/default/visualization_JVM-used-Memory.json']
Resource Declaration:
---------------------
# In
/root/chef-solo/cache/cookbooks/sdc-elasticsearch/recipes/ES_6_create_kibana_dashboard_virtualization.rb
1: cookbook_file
"/usr/share/elasticsearch/config/kibana_dashboard_virtualization.json" do
2: source "kibana_dashboard_virtualization.json"
3: owner "elasticsearch"
4: group "elasticsearch"
5: mode "0755"
6: end
7:
Compiled Resource:
------------------
# Declared in
/root/chef-solo/cache/cookbooks/sdc-elasticsearch/recipes/ES_6_create_kibana_dashboard_virtualization.rb:1:in
`from_file'
cookbook_file("/usr/share/elasticsearch/config/kibana_dashboard_virtualization.json")
do
provider Chef::Provider::CookbookFile
action [:create]
default_guard_interpreter :default
source "kibana_dashboard_virtualization.json"
declared_type :cookbook_file
cookbook_name "sdc-elasticsearch"
recipe_name "ES_6_create_kibana_dashboard_virtualization"
owner "elasticsearch"
group "elasticsearch"
mode "0755"
path
"/usr/share/elasticsearch/config/kibana_dashboard_virtualization.json"
verifications []
end
System Info:
------------
chef_version=13.5.3
platform=debian
platform_version=8.6
ruby=ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-linux]
program_name=chef-solo worker: ppid=970;start=01:43:09;
executable=/opt/chef/bin/chef-solo
[2019-05-31T01:43:10+00:00] INFO: Running queued delayed notifications before
re-raising exception
Running handlers:
[2019-05-31T01:43:10+00:00] ERROR: Running exception handlers
Running handlers complete
[2019-05-31T01:43:10+00:00] ERROR: Exception handlers complete
Chef Client failed. 0 resources updated in 00 seconds
[2019-05-31T01:43:10+00:00] FATAL: Stacktrace dumped to
/root/chef-solo/cache/chef-stacktrace.out
[2019-05-31T01:43:10+00:00] FATAL: Please provide the contents of the
stacktrace.out file if you file a bug report
[2019-05-31T01:43:10+00:00] ERROR:
cookbook_file[/usr/share/elasticsearch/config/kibana_dashboard_virtualization.json]
(sdc-elasticsearch::ES_6_create_kibana_dashboard_virtualization line 1) had an
error: Chef::Exceptions::FileNotFound: Cookbook 'sdc-elasticsearch' (0.0.0)
does not contain a file at any of these locations:
files/debian-8.6/kibana_dashboard_virtualization.json
files/debian/kibana_dashboard_virtualization.json
files/default/kibana_dashboard_virtualization.json
files/kibana_dashboard_virtualization.json
This cookbook _does_ contain:
['files/default/dashboard_BI-Dashboard.json','files/default/dashboard_Monitoring-Dashboared.json','files/default/visualization_JVM-used-CPU.json','files/default/visualization_JVM-used-Threads-Num.json','files/default/visualization_Show-all-distributed-services.json','files/default/visualization_host-used-CPU.json','files/default/visualization_host-used-Threads-Num.json','files/default/logging.yml','files/default/visualization_Show-all-certified-services-ampersand-resources-(per-day).json','files/default/visualization_Show-all-created-Resources-slash-Services-slash-Products.json','files/default/visualization_number-of-user-accesses.json','files/default/visualization_JVM-used-Memory.json']
[2019-05-31T01:43:10+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef
run process exited unsuccessfully (exit code 1)
