Hi Vivek, This is a known problem with SDC initialization in amsterdam. In order to overcome it, you should recreate SDC pods in the following order: cs -> be -> fe. Example, if my namespace is onap, I would: # kubectl delete pod -n onap-sdc sdc-cs-fd787c9b6-nt6f2 Wait for another instance of sdc-cs pod to be created and running (1/1) # kubectl delete pod -n onap-sdc sdc-be-6644d5cd67-vg4xw Wait for another instance of sdc-be pod to be created and running (2/2) #kubectl delete pod -n onap-sdc sdc-fe-7c4d59c5dc-5d5qw Wait for another instance of sdc-fe pod to be created and running (2/2)
Hope this helps. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: [email protected] [mailto:[email protected]] On Behalf Of Vivekanandan Muthukrishnan Sent: Friday, March 2, 2018 6:41 AM To: [email protected] Subject: [onap-discuss] Amsterdam Kubernetes OOM SDC UI is not accessible Hi All, We are setting up Amsterdam kuberneter oom. The deployment went fine, even the ONAP portal login works fine. However when we try to access the SDC portal it is keep throwing 503 error message. And we looked at the SDC-BE and SDC-ES logs and it seems like the elastic serach container failed to initialise "Error : Chef::Exceptions::FileNotFound: Cookbook 'sdc-elasticsearch' (0.0.0)" Did anyone face this issue? Is there any workaround to over come this issue? Thanks & Regards Vivek SDC-ES log sinppets [2018-02-28T12:24:38+00:00] INFO: Running queued delayed notifications before re-raising exception Running handlers: [2018-02-28T12:24:38+00:00] ERROR: Running exception handlers Running handlers complete [2018-02-28T12:24:38+00:00] ERROR: Exception handlers complete Chef Client failed. 0 resources updated in 01 seconds [2018-02-28T12:24:38+00:00] FATAL: Stacktrace dumped to /root/chef-solo/cache/chef-stacktrace.out [2018-02-28T12:24:38+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report [2018-02-28T12:24:38+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/logging.yml','files/default/visualization_JVM-used-CPU.json','files/default/visualization_JVM-used-Memory.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_host-used-CPU.json','files/default/visualization_host-used-Threads-Num.json','files/default/visualization_number-of-user-accesses.json','files/default/visualization_Show-all-distributed-services.json','files/default/visualization_JVM-used-Threads-Num.json'] [2018-02-28T12:24:38+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1) [2018-02-28 12:39:06,607][INFO ][cluster.metadata ] [sdc-es-3319302712-dn5h1] [.kibana] creating index, cause [api], templates [], shards [1]/[1], mappings [config] SDC-BE log snippets 2018-02-28T17:40:21.169Z [ES-Health-Check-Thread] ERROR o.o.sdc.be.dao.impl.ESCatalogDAO Error while trying to c onnect to elasticsearch. host: [sdc-es.onap-sdc:9300] | port: 9200 | error: None of the configured nodes are available: [{#transport#-1}{10.42. 82.207}{sdc-es.onap-sdc/10.42.82.207:9300<http://10.42.82.207:9300/>}] ONAP Portl UI This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
