Below is the log when SDC-ES container restarts and is unable to fully come up.

Since SDC-ES is used a cache and the cache is build upon container startup. This error can be avoided by not persisting SDC-ES data.

Running handlers:

[2017-12-14T10:14:25-05:00] ERROR: Running exception handlers

Running handlers complete

[2017-12-14T10:14:25-05:00] ERROR: Exception handlers complete

Chef Client failed. 0 resources updated in 29 seconds

[2017-12-14T10:14:25-05:00] FATAL: Stacktrace dumped to /root/chef-solo/cache/chef-stacktrace.out

[2017-12-14T10:14:25-05:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report

[2017-12-14T10:14:25-05:00] ERROR: ruby_block[check_ElasticSearch_Cluster_Health] (sdc-elasticsearch::ES_6_create_kibana_dashboard_virtualization line 2) had an error: Errno::ECONNREFUSED: Failed to open TCP connection to localhost:9200 (Connection refused - connect(2) for "localhost" port 9200)

[2017-12-14T10:14:25-05:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)