Kanagarai,
I have run the *docker_health.sh* script as you said and output as follows:
*root@vm1-sdc:/opt# /data/scripts/docker_health.sh*
*{*
* "cluster_name" : "SDC-ES-AUTO",*
* "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/html;charset=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
<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*
Now, I am trying to pull the master in */opt/sdc* directory and tried to
run */opt/asdc_vm_init.sh* script and trying to run *docker_health.sh*
afterwards,
it is getting blocked while "*BE health-Check:*"*. *
Is my approach correct??
Thanks,
Ganesh
On Wed, Sep 13, 2017 at 6:18 PM, Kanagaraj Manickam <
kanagaraj.manic...@huawei.com> wrote:
> Hi Ganesh,
>
> In sdc vm, you can find the scrip /data/docker_health.sh script. Can you
> please run it once and see all components are OK state.
>
> Also I felt that your portal is not up to date. Can you please git pull
> the master and re-initialize the portal.
>
>
>
> Regards,
>
> Kanagaraj M
>
>
>
> ************************************************************
> ***************************
> 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、
> 复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！*********
> ************************************************************
> *****************
>
> ************************************************************
> ***************************
> This e-mail and its attachments contain confidential information from
> HUAWEI, which is intended only for the person or entity whose address is
> listed above. Any use of the information contained herein in any way
> (including, but not limited to, total or partial disclosure,
> reproduction, or dissemination) by persons other than the intended
> recipient(s) is prohibited. If you receive this e-mail in error, please
> notify the sender by phone or email immediately and delete it!
> ************************************************************
> ***************************
>
>
>
> *From:* Ganesh Kaila [mailto:gane...@biarca.com]
> *Sent:* Wednesday, September 13, 2017 5:54 PM
> *To:* Elhay Efrat
> *Cc:* Kanagaraj Manickam; onap-discuss@lists.onap.org
>
> *Subject:* Re: [onap-discuss] ONAP v1.1 Portal isn't coming up on
> Openstack
>
>
>
> Hi,
>
>
>
> Please find the attached log files for the containers in vm1-sdc.
>
>
> Thanks,
>
> Ganesh
>
>
>
> On Wed, Sep 13, 2017 at 3:49 PM, Elhay Efrat <elhay.efr...@amdocs.com>
> wrote:
>
> Could you please share docker logs ?
>
>
>
> *From:* onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-bounces@
> lists.onap.org] *On Behalf Of *Ganesh Kaila
> *Sent:* Wednesday, September 13, 2017 1:16 PM
> *To:* Kanagaraj Manickam <kanagaraj.manic...@huawei.com>
> *Cc:* onap-discuss@lists.onap.org
> *Subject:* Re: [onap-discuss] ONAP v1.1 Portal isn't coming up on
> Openstack
>
>
>
> In addition to the previous mail -
>
>
>
> In */opt/portal/deliveries/* directory, I have commented out the cli
> container section in *docker-compose.yaml* file and run
> *portal_vm_init.sh* script then I am able to see three containers running
> as shown:
>
>
>
> ubuntu@vm1-portal:/opt/portal/deliveries$ sudo docker ps
>
> CONTAINER ID IMAGE COMMAND CREATED
> STATUS PORTS
> NAMES
>
> a2ca21b3cb29 portal-apps:1.1.0 "/wait-for.sh -t 1..." 40
> minutes ago Up 39 minutes 8989/tcp, 0.0.0.0:8006->8005/tcp,
> 0.0.0.0:8010->8009/tcp, 0.0.0.0:8989->8080/tcp deliveries_portal-apps_1
>
> d598838d887b portal-wms:1.1.0 "/wait-for.sh -t 1..." 40
> minutes ago Up 40 minutes 8082/tcp
> deliveries_portal-wms_1
>
> 06c8e8bd3168 portal-db:1.1.0 "docker-entrypoint..." 40
> minutes ago Up 40 minutes 3306/tcp
> deliveries_portal-db_1
>
> ubuntu@vm1-portal:/opt/portal/deliveries$
>
>
>
> And, I am able to login to portal webpage with designer credentials of
> ONAP:
>
>
>
> [image: Inline image 1]
>
>
>
>
>
> When I click on SDC widget, I am seeing as shown here:
>
>
>
> [image: Inline image 2]
>
>
>
> I have seen the similar problem with ONAP v1.0 on Openstack deployment.
>
>
>
> Please give me your suggestions to get over from this issue.
>
>
>
>
> Thanks,
>
> Ganesh
>
>
>
> On Wed, Sep 13, 2017 at 2:58 PM, Ganesh Kaila <gane...@biarca.com> wrote:
>
> Hi,
>
>
>
> I have re-deployed the ONAP v1.1 on Vanilla Openstack. I waited around 1
> hour 30 minutes to let the ONAP to be ready, then I logged into vm1-portal
> instance and checked the containers status.
>
>
>
> ubuntu@vm1-portal:~$ sudo docker ps -a
>
> CONTAINER ID IMAGE COMMAND CREATED
> STATUS PORTS NAMES
>
> 2765075dab0c mariadb "docker-entrypoint..." 33
> minutes ago Created data_vol_portal
>
>
>
> Then, I went on to debug the functionality. From the heat template, in
> portal section, it is trying to run *./opt/portal_install.sh* script. In
> the *portal_install.sh* script, it is again trying to run
> */opt/portal_vm_init.sh
> *script.
>
>
>
> From the /opt/portal_vm_init.sh script, I have found that the script files
> *dbstart.sh,
> new_start.sh and widget_ms_start.sh* are missing in
> */opt/portal/deliveries/* directory.
>
>
>
> I have figured out that either in */opt/portal_install.sh
> or /opt/portal_vm_init.sh*, we are not starting the docker containers.
>
>
>
> Further, I have checked */opt/portal/deliveries* directory. There, I can
> see another script file named *portal_vm_init.sh* which is trying to
> start the containers with *docker-compose* command. But, this script file
> is not running either from heat templates or any of the other scripts. May
> be, because of this reason I am not able to see the portal directly.
>
>
>
> Michael or Kanagarai, Do you have any suggestions on this or else am I
> missing something important??
>
>
> Thanks,
>
> Ganesh
>
>
>
> On Tue, Sep 12, 2017 at 7:58 PM, Kanagaraj Manickam <
> kanagaraj.manic...@huawei.com> wrote:
>
> Dear Ganesh,
>
>
>
> We were able to bring up the portal in 1.1 using heat based deployment on
> vanilla OpenStack.
>
> May be you want to introduce the time delay between the containers run
> step. Sometime, it helped us to bring all dockers up and running.
>
>
>
> Regards
>
> Kanagaraj M
>
>
>
> ************************************************************
> ***************************
> 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、
> 复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！*********
> ************************************************************
> *****************
>
> ************************************************************
> ***************************
> This e-mail and its attachments contain confidential information from
> HUAWEI, which is intended only for the person or entity whose address is
> listed above. Any use of the information contained herein in any way
> (including, but not limited to, total or partial disclosure,
> reproduction, or dissemination) by persons other than the intended
> recipient(s) is prohibited. If you receive this e-mail in error, please
> notify the sender by phone or email immediately and delete it!
> ************************************************************
> ***************************
>
>
>
> *From:* onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-bounces@
> lists.onap.org] *On Behalf Of *Ganesh Kaila
> *Sent:* 12 September 2017 15:15
> *To:* onap-discuss@lists.onap.org
> *Subject:* [onap-discuss] ONAP v1.1 Portal isn't coming up on Openstack
>
>
>
> Hi,
>
>
>
> I am trying to deploy ONAP v1.1 on Vanilla Openstack using the heat
> templates:
>
> - onap_openstack.yaml (https://nexus.onap.org/content/sites/raw/org.
> openecomp.demo/heat/OpenECOMP/1.1.0-SNAPSHOT/onap_openstack.yaml)
>
> - onap_openstack.env (https://nexus.onap.org/content/sites/raw/org.
> openecomp.demo/heat/OpenECOMP/1.1.0-SNAPSHOT/onap_openstack.env)
>
>
>
> I have allowed ports 8989, 8181, 3306, 8080, 8443 in the security groups.
>
>
>
> If I ssh into "vm1-portal" instance and check for containers, I could see
> only "maria-db" container created.
>
>
>
> Can someone help me to understand why does it happen??
>
>
>
> Thanks in advance.!
>
>
>
> Regards
>
> ,
>
> Ganesh
>
>
>
>
>
> 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
>
>
>
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
