AnsweredAssumed Answered

Jarvis Healthcheck KO

Question asked by Nicolas Afonso Employee on Aug 10, 2017
Latest reply on Sep 1, 2017 by Nicolas Afonso

Hi folks,

 

I am currently setting up the most up-to-date APIm platform :

- gateway in 9.2 

- OTK in 4.1

- portal 4.1

 

I am quite familiar with gateway and OTK, all is OK for this part. My issue is with last portal version. It requires an external analytics engine, jarvis.

 

I have been following the docops instruction to install it and set up. Nevertheless the last step, verification of the installation using jarvisHealthCheck.sh.

 

It seems I encounter an SSL issue, here is the output of the health check script :

 

-----------------------------------------------------------------------------------------------------------------------------
Argument onboarding url is https://<hostname>:8443
Argument ingestion url is https://<hostname>:8443
Argument elastic search url is http://<hostname>:9200
Argument isAvro is true
Argument wait time is 60

Avro is set to true
***** Starting End to End Jarvis health check *****
Onboarding product: jarvisheathcheck1502303043 resulted in curl: (58) NSS: client certificate not found (nickname not specified)
error! Expected 2XX return code but got 000. Please check logs.

Onboarding tenant: tenant1502303043 resulted in curl: (58) NSS: client certificate not found (nickname not specified)
error! Expected 2XX return code but got 000. Please check logs.

Create mapping with doctype: doctype1502303043 resulted in curl: (58) NSS: client certificate not found (nickname not specified)
error! Expected 2XX return code but got 000. Please check logs.
Let's wait for ElasticSearch to sync up............................................................
Ingesting data into Jarvis with POST resulted in curl: (58) NSS: client certificate not found (nickname not specified)
error! Expected 2XX return code but got 000. Please check logs.
Let's wait for ElasticSearch to sync up............................................................
Check for index's existent in Elasticsearch resulted in curl: (52) Empty reply from server
error! Expected 2XX return code but got 000. Please check logs.
Documents found in Elastic Search.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (52) Empty reply from server

 

***** JARVIS DEPLOYMENT STATUS: broken *****
------------------------------------------------------------------------------------------------------------------------------

 

Since Jarvis is not functionnal, the portal will not start

 

Could you help me identify the root cause ?

 

Thank you

Outcomes