Hi Ajay,
Thanks for your feedback!
I think that is not the root cause in my side, I just need wait more time so
that backend can connect with Cassandra, but SDC still cannot work, health
checkup scripts always show me Titan graph is down, I have reinstalled ONAP and
change the environment as below (as mentioned in another thread):
* artifacts_version: from 1.0.0
to 1.1.0-SNAPSHOT
* docker_version: from 1.0-STAGING-latest to latest
Still doesn't work.
Ajay, how you ever enabled SDC? What's the artefact version and the docker
version are you using?
sdc-es seems to fail as well,
$ sudo docker logs sdc-es
...
d: 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_Monitoring-Dashboared.json','files/default/logging.yml','files/default/visualization_JVM-used-CPU.json','files/default/visualization_JVM-used-Memory.json','files/default/visualization_JVM-used-Threads-Num.json','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_Show-all-distributed-services.json','files/default/visualization_host-used-CPU.json','files/default/visualization_host-used-Threads-Num.json','files/default/visualization_number-of-user-accesses.json','files/default/dashboard_BI-Dashboard.json']
[2017-07-04T21:38:40+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef
run process exited unsuccessfully (exit code 1)
From: ajay.priyadar...@ril.com [mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, July 5, 2017 1:52 PM
To: Chen, Wei D <wei.d.c...@intel.com>; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [SDC] Need your help to deploy SDC
Hi Dave chen,
I observed this issue as using openstack_float, and found that CS and ES were
not able to connect. Although this time all routing is working fine.
Errors:
1. stderrout.log
com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried
for query failed (tried: /10.64.105.82:9042
(com.datastax.driver.core.TransportException: [/10.64.105.82:9042] Cannot
connect))
2. /data/logs/BE/ASDC/ASDC-BE/error.log
2017-06-23T06:12:11.828Z|||ES-Health-Check-Thread||ASDC-BE||ERROR|||192.168.3.1||o.o.sdc.be.dao.impl.ESCatalogDAO||ActivityType=<?>,
Desc=<Error while trying to connect to elasticsearch. host:
[10.64.105.82:9300] port: 9200>
Resolution:
File /opt/config/public_ip.txt uses sdc_floating_ip (public ip). Even (CS is up
on -host-ip 0.0.0.0 -host-port 9042, ES is on -host-ip 0.0.0.0 -host-port
9200). I changed the /opt/config/public_ip.txt value to private_ip .
You also have same error
Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All
host(s) tried for query failed (tried: /192.168.4.116:9042
(com.datastax.driver.core.TransportException: [/192.168.4.116:9042] Cannot
connect))
My cassandra was also showing all required namespaces, but unable to serve. So
I observed and resolved as above. Hopefully it help you.
Regards,
Ajay Priyadarshi
Date: Sat, 1 Jul 2017 07:59:45 +0000
From: "Chen, Wei D" <wei.d.c...@intel.com<mailto:wei.d.c...@intel.com>>
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>"
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] [SDC] Need your help to deploy SDC
Message-ID:
<c5a0092c63e939488005f15f736a81125b2c2...@shsmsx104.ccr.corp.intel.com<mailto:c5a0092c63e939488005f15f736a81125b2c2...@shsmsx104.ccr.corp.intel.com>>
Content-Type: text/plain; charset="us-ascii"
Hi All,
I am trying to enable SDC in the demo project, the ONAP is on top of vanilla
OpenStack, just want to have a try on how it works from portal, but I got
bunches of issues and the latest one is from Cassandra, seen from the log it
seems like 9042 port is not available (log is attached), so I go to the
container and run /root/startup.sh manually, firstly, I can access the DB, but
some mins later I cannot access the DB anymore,
This is what I get from the DB couple of mins after run startup.sh.
# cqlsh -u cassandra -p Aa1234%^! 10.0.3.1
Namespaces:
cassandra@cqlsh> DESCRIBE keyspaces;
system_auth titan sdcaudit sdcartifact
sdccomponent system dox system_traces
I check both 9160 and 9042 inside container, seems like they are opened,
root@5aad37f3ec48:/var/log/cassandra# netstat -anp | grep 9042
tcp6 0 0 0.0.0.0:9042 :::* LISTEN
-
root@5aad37f3ec48:/var/log/cassandra# netstat -anp | grep 9160
tcp 0 0 0.0.0.0:9160 0.0.0.0:* LISTEN
-
But when I try to connect to the DB again, I see,
root@5aad37f3ec48:/var/log/cassandra# cqlsh -u cassandra -p Aa1234%^! 10.0.3.1
Connection error: ('Unable to connect to any servers', {'10.0.3.1':
OperationTimedOut('errors=None, last_host=None',)})
Also, I saw those message from console,
Fri Jun 30 01:39:52 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5
Looks like those info comes from /tmp/create_cassandra_user.sh.
Any ideas on how to fix it?
Best Regards,
Dave Chen
"Confidentiality Warning: This message and any attachments are intended only
for the use of the intended recipient(s), are confidential and may be
privileged. If you are not the intended recipient, you are hereby notified that
any review, re-transmission, conversion to hard copy, copying, circulation or
other use of this message and any attachments is strictly prohibited. If you
are not the intended recipient, please notify the sender immediately by return
email and delete this message and any attachments from your system.
Virus Warning: Although the company has taken reasonable precautions to ensure
no viruses are present in this email. The company cannot accept responsibility
for any loss or damage arising from the use of this email or attachment."
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
