Hi Michael,

from the   es0821.log, we found some errors 

when the sdc-elasticsearch  docker image run, the chef did not find the file  
kibana_dashboard_virtualization.json ,so that the  sdc-elasticsearch  service 
was not correct。

we entry the docker container of sdc-elasticsearch,and do not find the 
kibana_dashboard_virtualization.json in directory of  
/root/chef-solo/cookbooks/sdc-elasticsearch/files/default

 

Chef Client failed. 0 resources updated in 01 seconds

[2017-08-21T02:24:35-04:00] FATAL: Stacktrace dumped to 
/root/chef-solo/cache/chef-stacktrace.out

[2017-08-21T02:24:35-04:00] FATAL: Please provide the contents of the 
stacktrace.out file if you file a bug report

[2017-08-21T02:24:35-04: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









原始邮件



发件人:袁虎10090474
收件人: <ml6...@intl.att.com>
抄送人: <onap-discuss@lists.onap.org> <avi....@amdocs.com> <el4...@intl.att.com> 
<gaut...@amdocs.com>
日 期 :2017年08月21日 14:56
主 题 :Re: [onap-discuss][JIRA] (SDC-239) The '1.1-STAGING-latest' version of SDC 
isunavailable.







Hi Michael,




I do reboot the sdc as you said. But its seems still not woked.

For detail log informations to see the attachments.
























logs.zip for /data/logs

cs0821.log for 'docker logs sdc-cs > cs0821.log'

BE0821.log for 'docker logs sdc-BE > BE0821.log'

es0821.log for 'docker logs sdc-es > es0821.log'

FE0821.log for 'docker logs sdc-FE > FE0821.log'

kbn0821.log for 'docker logs sdc-kbn > kbn0821.log'







Thanks,


Yuan Hu





root@ubuntu:/data/scripts# ./docker_health.sh

{

  "cluster_name" : "SDC-ES-Template",

  "status" : "green",

  "timed_out" : false,

  "number_of_nodes" : 1,

  "number_of_data_nodes" : 1,

  "active_primary_shards" : 0,

  "active_shards" : 0,

  "relocating_shards" : 0,

  "initializing_shards" : 0,

  "unassigned_shards" : 0,

  "delayed_unassigned_shards" : 0,

  "number_of_pending_tasks" : 0,

  "number_of_in_flight_fetch" : 0,

  "task_max_waiting_in_queue_millis" : 0,

  "active_shards_percent_as_number" : 100.0

}

BE health-Check:

<html>

<head>

<meta http-equiv="Content-Type" content="text/htmlcharset=ISO-8859-1"/>

<title>Error 503 </title>

</head>

<body>

<h2>HTTP ERROR: 503</h2>

<p>Problem accessing /sdc2/rest/healthCheck. Reason:

<pre>    Service Unavailable</pre></p>

<hr /><a href="http://eclipse.org/jetty";>Powered by Jetty:// 
9.3.20.v20170531</a><hr/>

</body>

</html>







FE health-Check:

{

  "sdcVersion": "UNKNOWN",

  "siteMode": "UNKNOWN",

  "componentsInfo": [

    {

      "healthCheckComponent": "FE",

      "healthCheckStatus": "UP",

      "version": "1.1.0-SNAPSHOT",

      "description": "OK"

    },

    {

      "healthCheckComponent": "BE",

      "healthCheckStatus": "DOWN"

    },

    {

      "healthCheckComponent": "TITAN",

      "healthCheckStatus": "UNKNOWN"

    },

    {

      "healthCheckComponent": "CASSANDRA",

      "healthCheckStatus": "UNKNOWN"

    },

    {

      "healthCheckComponent": "DE",

      "healthCheckStatus": "UNKNOWN"

    },

    {

      "healthCheckComponent": "ON_BOARDING",

      "healthCheckStatus": "UNKNOWN"

    }

  ]

}




Error [12] while user existance check

root@ubuntu:/data/scripts# 



















发件人: <j...@onap.org>
收件人:袁虎10090474
日 期 :2017年08月21日 03:00
主 题 :[JIRA] (SDC-239) The '1.1-STAGING-latest' version of SDC isunavailable.





Message Title Michael Lando commented on SDC-239   Re: The '1.1-STAGING-latest' 
version of SDC is unavailable. 
from a look at the logs, it looks like the C*  is missing so columns.


I checked the Cassandra docker startup logs and I do not see any error there.


 


we did not encounter this issue in any local environment.


 


I want to re start your deployment.

stop all the dockers.

delete the Cassandra data  rm -rf  /data/CS/*

restart the Dockers.


this should provide you with a clean deployment.


please collect all the logs during this flow.


 


 

 Add Comment  This message was sent by Atlassian JIRA 
(v7.3.0#73011-sha1:3c73d0e)
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to