subject:"Re\: \[onap\-discuss\] SDC portal is not accessible with 502 error"

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-23 Thread Lando,Michael

Hi,

>From the error you are getting it looks like the keyspaces needed for the BE 
>functionality were not created in the Cassandra.

On the Cassandra Docker startup we run our scheme creation process and then the 
keyspaces should be created.

Please try to login to Cassandra cqlsh and post here what are the keyspaces 
that exist there.

In addition please post the output of the Cassandra Docker on startup so that 
we will be able to see if there was an error there.






BR,

Michael Lando
Opensource & Frontend Team Lead, SDC
AT&T Network Application Development * NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
***
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: ml6...@intl.att.com<mailto:ml6...@intl.att.com>


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
ajay.priyadar...@ril.com
Sent: Monday, May 22, 2017 10:19 AM
To: EMPOROPULO, VITALIY ; ROSE, DANIEL V 
; aayush.bhatna...@ril.com; EFRAT, ELHAY 
; onap-discuss@lists.onap.org; ning...@ril.com; 
robert.pipp...@ril.com
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

I changed the cassandra-host ip in Cassandra.yaml from public ip to internal ip 
and get rid of below error.
com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried 
for query failed (tried: /172.16.74.83:9042 
(com.datastax.driver.core.TransportException: [/172.16.74.83:9042] Cannot 
connect))

But still getting the multiple beans initialization failure as in trailing mail.

PFA docker inspect logs, where CS have exposed 9042 port.

I have also attached the BE Stderr logs.


Regards,
Ajay

From: Vitaliy Emporopulo [mailto:vitaliy.emporop...@amdocs.com]
Sent: 20 May 2017 12:57
To: Ajay Priyadarshi; dr6...@att.com<mailto:dr6...@att.com>; Aayush Bhatnagar; 
Elhay Efrat; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
Ning So; Robert Pippert
Subject: RE: SDC portal is not accessible with 502 error

Have you updated the BE configuration per my suggestion? KEYSPACE_NOT_CONNECTED 
is most likely because the BE cannot reach Cassandra. Do you see any errors in 
BE stderr.log now?

It's not clear from your last email what steps you have taken to fix the issue.

Also, please run "docker inspect" on the Cassandra container to see if it 
exposes port 9042.

Regards,
Vitaliy

From: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com> 
[mailto:ajay.priyadar...@ril.com]
Sent: Friday, May 19, 2017 16:36
To: dr6...@att.com<mailto:dr6...@att.com>; Vitaliy Emporopulo 
mailto:vitaliy.emporop...@amdocs.com>>; 
aayush.bhatna...@ril.com<mailto:aayush.bhatna...@ril.com>; Elhay Efrat 
mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
ning...@ril.com<mailto:ning...@ril.com>; 
robert.pipp...@ril.com<mailto:robert.pipp...@ril.com>
Subject: RE: SDC portal is not accessible with 502 error

Hi,

On SDC Cassandra is UP. The communication issues among all containers (all 
residing in same vm)

(Backend Health check)
root@vm1-sdc:/data/logs/BE/ASDC/ASDC-BE# curl 
http://localhost:8080/sdc2/rest/healthCheck<https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A8080_sdc2_rest_healthCheck&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY&m=-ovrFyR191ZrCsi3yqQ2EfE3HcXJ46ptFVXKjWpEMZk&s=a-Z24Zma3uc_o8B-C2M2wP0Snkt64ubictacTkb80Ts&e=>
  


Error 503 


HTTP ERROR: 503
Problem accessing /sdc2/rest/healthCheck. Reason:
Service Unavailable
http://eclipse.org/jetty<https://urldefense.proofpoint.com/v2/url?u=http-3A__eclipse.org_jetty&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY&m=-ovrFyR191ZrCsi3yqQ2EfE3HcXJ46ptFVXKjWpEMZk&s=1MozW4SpRVO2Q5h9L94liGHRbDANGlQtU8GYpIDSsOE&e=>">Powered
 by Jetty:// 9.3.15.v20161220



There are highlighted  beans which have not been initialized, so kindly suggest 
the possible reasons for failed initialization of these beans.

2017-05-19T12:41:19.007Z|||main||ASDC-BE||ERROR|o.s.web.context.ContextLoader||ActivityType=,
 Desc=
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.b

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-23 Thread Lefevre, Catherine

Re-sending the information shared by Michael Lando this morning

"Hi,

>From the error you are getting it looks like the keyspaces needed for the BE 
>functionality were not created in the Cassandra.

On the Cassandra Docker startup we run our scheme creation process and then the 
keyspaces should be created.

Please try to login to Cassandra cqlsh and post here what are the keyspaces 
that exist there.

In addition please post the output of the Cassandra Docker on startup so that 
we will be able to see if there was an error there"

Best regards

Catherine

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
ajay.priyadar...@ril.com
Sent: Monday, May 22, 2017 9:19 AM
To: EMPOROPULO, VITALIY ; ROSE, DANIEL V 
; aayush.bhatna...@ril.com; EFRAT, ELHAY 
; onap-discuss@lists.onap.org; ning...@ril.com; 
robert.pipp...@ril.com
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

I changed the cassandra-host ip in Cassandra.yaml from public ip to internal ip 
and get rid of below error.
com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried 
for query failed (tried: /172.16.74.83:9042 
(com.datastax.driver.core.TransportException: [/172.16.74.83:9042] Cannot 
connect))

But still getting the multiple beans initialization failure as in trailing mail.

PFA docker inspect logs, where CS have exposed 9042 port.

I have also attached the BE Stderr logs.


Regards,
Ajay

From: Vitaliy Emporopulo [mailto:vitaliy.emporop...@amdocs.com]
Sent: 20 May 2017 12:57
To: Ajay Priyadarshi; dr6...@att.com<mailto:dr6...@att.com>; Aayush Bhatnagar; 
Elhay Efrat; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
Ning So; Robert Pippert
Subject: RE: SDC portal is not accessible with 502 error

Have you updated the BE configuration per my suggestion? KEYSPACE_NOT_CONNECTED 
is most likely because the BE cannot reach Cassandra. Do you see any errors in 
BE stderr.log now?

It's not clear from your last email what steps you have taken to fix the issue.

Also, please run "docker inspect" on the Cassandra container to see if it 
exposes port 9042.

Regards,
Vitaliy

From: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com> 
[mailto:ajay.priyadar...@ril.com]
Sent: Friday, May 19, 2017 16:36
To: dr6...@att.com<mailto:dr6...@att.com>; Vitaliy Emporopulo 
mailto:vitaliy.emporop...@amdocs.com>>; 
aayush.bhatna...@ril.com<mailto:aayush.bhatna...@ril.com>; Elhay Efrat 
mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
ning...@ril.com<mailto:ning...@ril.com>; 
robert.pipp...@ril.com<mailto:robert.pipp...@ril.com>
Subject: RE: SDC portal is not accessible with 502 error

Hi,

On SDC Cassandra is UP. The communication issues among all containers (all 
residing in same vm)

(Backend Health check)
root@vm1-sdc:/data/logs/BE/ASDC/ASDC-BE# curl 
http://localhost:8080/sdc2/rest/healthCheck<https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A8080_sdc2_rest_healthCheck&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M&m=bKpbRE7zeVbNQnwgi53UsMk091xlCBisfKHqkFljruE&s=6uhcHy9xGuKyinUFDUuAx7Vv4qqY6pM211Dfhx2SnhQ&e=>
  


Error 503 


HTTP ERROR: 503
Problem accessing /sdc2/rest/healthCheck. Reason:
Service Unavailable
http://eclipse.org/jetty<https://urldefense.proofpoint.com/v2/url?u=http-3A__eclipse.org_jetty&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M&m=bKpbRE7zeVbNQnwgi53UsMk091xlCBisfKHqkFljruE&s=nDoqi9Z4NiE7N5WYWJ1EquyUcQOEwDBueLmD4SOGg10&e=>">Powered
 by Jetty:// 9.3.15.v20161220



There are highlighted  beans which have not been initialized, so kindly suggest 
the possible reasons for failed initialization of these beans.

2017-05-19T12:41:19.007Z|||main||ASDC-BE||ERROR|o.s.web.context.ContextLoader||ActivityType=,
 Desc=
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection of resource 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name &#x

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-20 Thread Vitaliy Emporopulo

Have you updated the BE configuration per my suggestion? KEYSPACE_NOT_CONNECTED 
is most likely because the BE cannot reach Cassandra. Do you see any errors in 
BE stderr.log now?

It's not clear from your last email what steps you have taken to fix the issue.

Also, please run "docker inspect" on the Cassandra container to see if it 
exposes port 9042.

Regards,
Vitaliy

From: ajay.priyadar...@ril.com [mailto:ajay.priyadar...@ril.com]
Sent: Friday, May 19, 2017 16:36
To: dr6...@att.com; Vitaliy Emporopulo ; 
aayush.bhatna...@ril.com; Elhay Efrat ; 
onap-discuss@lists.onap.org; ning...@ril.com; robert.pipp...@ril.com
Subject: RE: SDC portal is not accessible with 502 error

Hi,

On SDC Cassandra is UP. The communication issues among all containers (all 
residing in same vm)

(Backend Health check)
root@vm1-sdc:/data/logs/BE/ASDC/ASDC-BE# curl 
http://localhost:8080/sdc2/rest/healthCheck  


Error 503 


HTTP ERROR: 503
Problem accessing /sdc2/rest/healthCheck. Reason:
Service Unavailable
http://eclipse.org/jetty";>Powered by Jetty:// 
9.3.15.v20161220



There are highlighted  beans which have not been initialized, so kindly suggest 
the possible reasons for failed initialization of these beans.

2017-05-19T12:41:19.007Z|||main||ASDC-BE||ERROR|o.s.web.context.ContextLoader||ActivityType=,
 Desc=
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection of resource 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'component-cassandra-dao': Invocation of init method failed; nested 
exception is java.lang.RuntimeException: Artifact keyspace [sdccomponent] 
failed to connect with error : KEYSPACE_NOT_CONNECTED


Does any script or doc available for validating all necessary services for each 
kind of vm, which could help debugging.

Regards,
Ajay

From: ROSE, DANIEL V [mailto:dr6...@att.com]
Sent: 18 May 2017 20:50
To: EMPOROPULO, VITALIY; Aayush Bhatnagar; Ajay Priyadarshi; EFRAT, ELHAY; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Ning So; 
Robert Pippert
Subject: RE: SDC portal is not accessible with 502 error

Aayush,

There is kind of a story already for this 
https://jira.onap.org/browse/COMMON-12?filter=-2
if you want to track that or add some details

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of EMPOROPULO, VITALIY
Sent: Thursday, May 18, 2017 11:10 AM
To: aayush.bhatna...@ril.com<mailto:aayush.bhatna...@ril.com>; 
ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com>; EFRAT, ELHAY 
mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
ning...@ril.com<mailto:ning...@ril.com>; 
robert.pipp...@ril.com<mailto:robert.pipp...@ril.com>
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Hi Aayush,

It is obviously not a good way to use containers, and is definitely going to 
change.

To my understanding, running all of the SDC containers in a single VM was a 
quick and easy solution for automating SDC deployment in ONAP. From that point 
it will evolve to proper (Micro)services, with independent scaling-out of 
components, load balancing and service lookup as a means of HA and fault 
tolerance, etc.

Regards,
Vitaliy

From: aayush.bhatna...@ril.com<mailto:aayush.bhatna...@ril.com> 
[mailto:aayush.bhatna...@ril.com]
Sent: Thursday, May 18, 2017 17:38
To: Vitaliy Emporopulo 
mailto:vitaliy.emporop...@amdocs.com>>; 
ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com>; Elhay Efrat 
mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
ning...@ril.com<mailto:ning...@ril.com>; 
robert.pipp...@ril.com<mailto:robert.pipp...@ril.com>
Subject: RE: SDC portal is not accessible with 502 error

Thanks for the update Vitaliy.

The requirement of running on the same host is something which has been done by 
design, or will it change in the future.

Why I ask this question is the fact that once we try

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-19 Thread Ajay.Priyadarshi

Hi,

On SDC Cassandra is UP. The communication issues among all containers (all 
residing in same vm)

(Backend Health check)
root@vm1-sdc:/data/logs/BE/ASDC/ASDC-BE# curl 
http://localhost:8080/sdc2/rest/healthCheck  


Error 503 


HTTP ERROR: 503
Problem accessing /sdc2/rest/healthCheck. Reason:
Service Unavailable
http://eclipse.org/jetty";>Powered by Jetty:// 
9.3.15.v20161220



There are highlighted  beans which have not been initialized, so kindly suggest 
the possible reasons for failed initialization of these beans.

2017-05-19T12:41:19.007Z|||main||ASDC-BE||ERROR|o.s.web.context.ContextLoader||ActivityType=,
 Desc=
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection of resource 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'component-cassandra-dao': Invocation of init method failed; nested 
exception is java.lang.RuntimeException: Artifact keyspace [sdccomponent] 
failed to connect with error : KEYSPACE_NOT_CONNECTED


Does any script or doc available for validating all necessary services for each 
kind of vm, which could help debugging.

Regards,
Ajay

From: ROSE, DANIEL V [mailto:dr6...@att.com]
Sent: 18 May 2017 20:50
To: EMPOROPULO, VITALIY; Aayush Bhatnagar; Ajay Priyadarshi; EFRAT, ELHAY; 
onap-discuss@lists.onap.org; Ning So; Robert Pippert
Subject: RE: SDC portal is not accessible with 502 error

Aayush,

There is kind of a story already for this 
https://jira.onap.org/browse/COMMON-12?filter=-2
if you want to track that or add some details

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of EMPOROPULO, VITALIY
Sent: Thursday, May 18, 2017 11:10 AM
To: aayush.bhatna...@ril.com<mailto:aayush.bhatna...@ril.com>; 
ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com>; EFRAT, ELHAY 
mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
ning...@ril.com<mailto:ning...@ril.com>; 
robert.pipp...@ril.com<mailto:robert.pipp...@ril.com>
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Hi Aayush,

It is obviously not a good way to use containers, and is definitely going to 
change.

To my understanding, running all of the SDC containers in a single VM was a 
quick and easy solution for automating SDC deployment in ONAP. From that point 
it will evolve to proper (Micro)services, with independent scaling-out of 
components, load balancing and service lookup as a means of HA and fault 
tolerance, etc.

Regards,
Vitaliy

From: aayush.bhatna...@ril.com<mailto:aayush.bhatna...@ril.com> 
[mailto:aayush.bhatna...@ril.com]
Sent: Thursday, May 18, 2017 17:38
To: Vitaliy Emporopulo 
mailto:vitaliy.emporop...@amdocs.com>>; 
ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com>; Elhay Efrat 
mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
ning...@ril.com<mailto:ning...@ril.com>; 
robert.pipp...@ril.com<mailto:robert.pipp...@ril.com>
Subject: RE: SDC portal is not accessible with 502 error

Thanks for the update Vitaliy.

The requirement of running on the same host is something which has been done by 
design, or will it change in the future.

Why I ask this question is the fact that once we try to execute HA and Fault 
Tolerant scenarios for individual ONAP components (inclusive of the SDC), the 
hosts may change.

Regards

Aayush


From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Vitaliy Emporopulo
Sent: 18 May 2017 18:41
To: Ajay Priyadarshi; Elhay Efrat; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Hi Ajay,

Currently a SDC setup expects all of its containers to run on the same host 
(virtual or physical), and access each other via the host's IP address or 
hostname visible inside the containers. This is possible using

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-18 Thread ROSE, DANIEL V

Aayush,

There is kind of a story already for this 
https://jira.onap.org/browse/COMMON-12?filter=-2
if you want to track that or add some details

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of EMPOROPULO, VITALIY
Sent: Thursday, May 18, 2017 11:10 AM
To: aayush.bhatna...@ril.com; ajay.priyadar...@ril.com; EFRAT, ELHAY 
; onap-discuss@lists.onap.org; ning...@ril.com; 
robert.pipp...@ril.com
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Hi Aayush,

It is obviously not a good way to use containers, and is definitely going to 
change.

To my understanding, running all of the SDC containers in a single VM was a 
quick and easy solution for automating SDC deployment in ONAP. From that point 
it will evolve to proper (Micro)services, with independent scaling-out of 
components, load balancing and service lookup as a means of HA and fault 
tolerance, etc.

Regards,
Vitaliy

From: aayush.bhatna...@ril.com<mailto:aayush.bhatna...@ril.com> 
[mailto:aayush.bhatna...@ril.com]
Sent: Thursday, May 18, 2017 17:38
To: Vitaliy Emporopulo 
mailto:vitaliy.emporop...@amdocs.com>>; 
ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com>; Elhay Efrat 
mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
ning...@ril.com<mailto:ning...@ril.com>; 
robert.pipp...@ril.com<mailto:robert.pipp...@ril.com>
Subject: RE: SDC portal is not accessible with 502 error

Thanks for the update Vitaliy.

The requirement of running on the same host is something which has been done by 
design, or will it change in the future.

Why I ask this question is the fact that once we try to execute HA and Fault 
Tolerant scenarios for individual ONAP components (inclusive of the SDC), the 
hosts may change.

Regards

Aayush


From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Vitaliy Emporopulo
Sent: 18 May 2017 18:41
To: Ajay Priyadarshi; Elhay Efrat; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Hi Ajay,

Currently a SDC setup expects all of its containers to run on the same host 
(virtual or physical), and access each other via the host's IP address or 
hostname visible inside the containers. This is possible using 
container-to-host port binding.

Apparently, a SDC container cannot reach the others via 172.16.74.83. On the 
other hand, it looks like the BE identifies itself as 10.0.3.1 (see the log), 
which is your private_ip. This also makes perfect sense - the containers should 
talk to each other on the private network, while the public one is exposed for 
external access. Normally that would be the front-end server.

I guess you won't see a 172.16.74.x address if you run ifconfig inside a 
container, except on FE.

To sum up, the configuration of your containers should point to the private 
network IPs for container-to-container communication (FE-to-BE, 
BE-to-Cassandra, etc).

Regards,
Vitaliy

From: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com> 
[mailto:ajay.priyadar...@ril.com]
Sent: Thursday, May 18, 2017 15:00
To: Vitaliy Emporopulo 
mailto:vitaliy.emporop...@amdocs.com>>; Elhay 
Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: SDC portal is not accessible with 502 error

Hi Vitaliy,

All SDC Docker containers are on single VM.

docker container list
CONTAINER IDIMAGE   
   COMMAND  CREATED STATUS  PORTS   
  NAMES
58421a971a63
nexus3.onap.org:10001/openecomp/sdc-frontend:1.0-STAGING-latest
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:8181->8181/tcp, 8080/tcp, 0.0.0.0:9443->9443/tcp  sdc-FE
35cdccf1abb5
nexus3.onap.org:10001/openecomp/sdc-backend:1.0-STAGING-latest 
"/root/startup.sh"   3 hours ago Up 42 minutes   
0.0.0.0:8080->8080/tcp, 0.0.0.0:8443->8443/tcpsdc-BE
139f5a712d37
nexus3.onap.org:10001/openecomp/sdc-kibana:1.0-STAGING-latest  
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:5601->5601/tcp
sdc-kbn
9b60d4f6fd20
nexus3.onap.org:10001/openecomp/sdc-cassandra:1.0-STAGING-latest   
"/root/startup.sh"   3 hours ago Up 3 hours  7000-7001/tcp, 
0.0.0.0:9042->9042/tcp, 7199/tcp, 0.0.0.0:9160->9160/tcp   sdc-cs
85b83dec8442
nexus3.onap.org:10001

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-18 Thread Vitaliy Emporopulo

Hi Aayush,

It is obviously not a good way to use containers, and is definitely going to 
change.

To my understanding, running all of the SDC containers in a single VM was a 
quick and easy solution for automating SDC deployment in ONAP. From that point 
it will evolve to proper (Micro)services, with independent scaling-out of 
components, load balancing and service lookup as a means of HA and fault 
tolerance, etc.

Regards,
Vitaliy

From: aayush.bhatna...@ril.com [mailto:aayush.bhatna...@ril.com]
Sent: Thursday, May 18, 2017 17:38
To: Vitaliy Emporopulo ; 
ajay.priyadar...@ril.com; Elhay Efrat ; 
onap-discuss@lists.onap.org; ning...@ril.com; robert.pipp...@ril.com
Subject: RE: SDC portal is not accessible with 502 error

Thanks for the update Vitaliy.

The requirement of running on the same host is something which has been done by 
design, or will it change in the future.

Why I ask this question is the fact that once we try to execute HA and Fault 
Tolerant scenarios for individual ONAP components (inclusive of the SDC), the 
hosts may change.

Regards

Aayush


From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Vitaliy Emporopulo
Sent: 18 May 2017 18:41
To: Ajay Priyadarshi; Elhay Efrat; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Hi Ajay,

Currently a SDC setup expects all of its containers to run on the same host 
(virtual or physical), and access each other via the host's IP address or 
hostname visible inside the containers. This is possible using 
container-to-host port binding.

Apparently, a SDC container cannot reach the others via 172.16.74.83. On the 
other hand, it looks like the BE identifies itself as 10.0.3.1 (see the log), 
which is your private_ip. This also makes perfect sense - the containers should 
talk to each other on the private network, while the public one is exposed for 
external access. Normally that would be the front-end server.

I guess you won't see a 172.16.74.x address if you run ifconfig inside a 
container, except on FE.

To sum up, the configuration of your containers should point to the private 
network IPs for container-to-container communication (FE-to-BE, 
BE-to-Cassandra, etc).

Regards,
Vitaliy

From: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com> 
[mailto:ajay.priyadar...@ril.com]
Sent: Thursday, May 18, 2017 15:00
To: Vitaliy Emporopulo 
mailto:vitaliy.emporop...@amdocs.com>>; Elhay 
Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: SDC portal is not accessible with 502 error

Hi Vitaliy,

All SDC Docker containers are on single VM.

docker container list
CONTAINER IDIMAGE   
   COMMAND  CREATED STATUS  PORTS   
  NAMES
58421a971a63
nexus3.onap.org:10001/openecomp/sdc-frontend:1.0-STAGING-latest
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:8181->8181/tcp, 8080/tcp, 0.0.0.0:9443->9443/tcp  sdc-FE
35cdccf1abb5
nexus3.onap.org:10001/openecomp/sdc-backend:1.0-STAGING-latest 
"/root/startup.sh"   3 hours ago Up 42 minutes   
0.0.0.0:8080->8080/tcp, 0.0.0.0:8443->8443/tcpsdc-BE
139f5a712d37
nexus3.onap.org:10001/openecomp/sdc-kibana:1.0-STAGING-latest  
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:5601->5601/tcp
sdc-kbn
9b60d4f6fd20
nexus3.onap.org:10001/openecomp/sdc-cassandra:1.0-STAGING-latest   
"/root/startup.sh"   3 hours ago Up 3 hours  7000-7001/tcp, 
0.0.0.0:9042->9042/tcp, 7199/tcp, 0.0.0.0:9160->9160/tcp   sdc-cs
85b83dec8442
nexus3.onap.org:10001/openecomp/sdc-elasticsearch:1.0-STAGING-latest   
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:9200->9200/tcp, 0.0.0.0:9300->9300/tcpsdc-es

<> have correct Ip_address.

Vm1_sdc public_ip:172.16.64.83
Vm1_sdc private_ip: 10.0.3.1

Cassandra sever are running and UP.

BE stderr.log

Last shared stderr logs. I am getting following highlighted

May 18, 2017 11:07:19 AM org.springframework.web.context.ContextLoader 
initWebApplicationContext
SEVERE: Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'vendorLicenseManager' defined in ServletContext resource 
[/WEB-INF/beans-services.xml]: Instantiation of bean failed; nested exception 
is java.lang.ExceptionInInitializerError
..

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-18 Thread Aayush.Bhatnagar

Thanks for the update Vitaliy.

The requirement of running on the same host is something which has been done by 
design, or will it change in the future.

Why I ask this question is the fact that once we try to execute HA and Fault 
Tolerant scenarios for individual ONAP components (inclusive of the SDC), the 
hosts may change.

Regards

Aayush


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Vitaliy Emporopulo
Sent: 18 May 2017 18:41
To: Ajay Priyadarshi; Elhay Efrat; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Hi Ajay,

Currently a SDC setup expects all of its containers to run on the same host 
(virtual or physical), and access each other via the host's IP address or 
hostname visible inside the containers. This is possible using 
container-to-host port binding.

Apparently, a SDC container cannot reach the others via 172.16.74.83. On the 
other hand, it looks like the BE identifies itself as 10.0.3.1 (see the log), 
which is your private_ip. This also makes perfect sense - the containers should 
talk to each other on the private network, while the public one is exposed for 
external access. Normally that would be the front-end server.

I guess you won't see a 172.16.74.x address if you run ifconfig inside a 
container, except on FE.

To sum up, the configuration of your containers should point to the private 
network IPs for container-to-container communication (FE-to-BE, 
BE-to-Cassandra, etc).

Regards,
Vitaliy

From: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com> 
[mailto:ajay.priyadar...@ril.com]
Sent: Thursday, May 18, 2017 15:00
To: Vitaliy Emporopulo 
mailto:vitaliy.emporop...@amdocs.com>>; Elhay 
Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: SDC portal is not accessible with 502 error

Hi Vitaliy,

All SDC Docker containers are on single VM.

docker container list
CONTAINER IDIMAGE   
   COMMAND  CREATED STATUS  PORTS   
  NAMES
58421a971a63
nexus3.onap.org:10001/openecomp/sdc-frontend:1.0-STAGING-latest
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:8181->8181/tcp, 8080/tcp, 0.0.0.0:9443->9443/tcp  sdc-FE
35cdccf1abb5
nexus3.onap.org:10001/openecomp/sdc-backend:1.0-STAGING-latest 
"/root/startup.sh"   3 hours ago Up 42 minutes   
0.0.0.0:8080->8080/tcp, 0.0.0.0:8443->8443/tcpsdc-BE
139f5a712d37
nexus3.onap.org:10001/openecomp/sdc-kibana:1.0-STAGING-latest  
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:5601->5601/tcp
sdc-kbn
9b60d4f6fd20
nexus3.onap.org:10001/openecomp/sdc-cassandra:1.0-STAGING-latest   
"/root/startup.sh"   3 hours ago Up 3 hours  7000-7001/tcp, 
0.0.0.0:9042->9042/tcp, 7199/tcp, 0.0.0.0:9160->9160/tcp   sdc-cs
85b83dec8442
nexus3.onap.org:10001/openecomp/sdc-elasticsearch:1.0-STAGING-latest   
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:9200->9200/tcp, 0.0.0.0:9300->9300/tcpsdc-es

<> have correct Ip_address.

Vm1_sdc public_ip:172.16.64.83
Vm1_sdc private_ip: 10.0.3.1

Cassandra sever are running and UP.

BE stderr.log

Last shared stderr logs. I am getting following highlighted

May 18, 2017 11:07:19 AM org.springframework.web.context.ContextLoader 
initWebApplicationContext
SEVERE: Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'vendorLicenseManager' defined in ServletContext resource 
[/WEB-INF/beans-services.xml]: Instantiation of bean failed; nested exception 
is java.lang.ExceptionInInitializerError
.
Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All 
host(s) tried for query failed (tried: /172.16.74.83:9042 
(com.datastax.driver.core.TransportException: [/172.16.74.83:9042] Cannot 
connect))
at 
com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:240)
  ...

BE error.log

2017-05-18T11:40:31.762Z|||ES-Health-Check-Thread||ASDC-BE||ERROR|||10.0.3.1||o.o.sdc.be.dao.impl.ESCatalogDAO||ActivityType=,
 Desc=
2017-05-18T11:40:34.763Z|||ES-Health-Check-Thread||ASDC-BE||ERROR|||10.0.3.1||o.o.sdc.be.dao.impl.ESCatalogDAO||ActivityType=,
 Desc=
2017-05-18T11:40:37.762Z|||ES-Health-Check-Thread||ASDC-BE||ERROR|||10.0.3.1||o.o.sdc.be.dao.impl.ESCatalogDAO||ActivityType=,
 Desc=
2017-05-18T11:40:40.763Z|||ES-Health-Check-Thread||ASDC-BE||ERROR|||10.0.3.1||o.

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-18 Thread Vitaliy Emporopulo

.HttpClient||ActivityType=,
 Desc=<   --> HTTP/1.1 200 OK>
2017-05-18T11:40:41.793Z|||UEBConsumerThread||ASDC-BE||INFO|||10.0.3.1||c.a.n.c.c.impl.CambriaConsumerImpl||ActivityType=,
 Desc=
2017-05-18T11:40:41.793Z|||UEBConsumerThread||ASDC-BE||WARN|||10.0.3.1||c.att.nsa.apiClient.http.HttpClient||ActivityType=,
 Desc=http://10.0.11.1:3904/events/ECOMP-PORTAL-OUTBOX-SDC1/c2e95926-534b-4836-8135-19e14ef91c8a/cdae6e8c-3951-4634-bfa4-cff074ac4834?timeout=15000&limit=1000
 will send credentials over a clear channel.>
2017-05-18T11:40:41.793Z|||UEBConsumerThread||ASDC-BE||INFO|||10.0.3.1||c.att.nsa.apiClient.http.HttpClient||ActivityType=,
 Desc=http://10.0.11.1:3904/events/ECOMP-PORTAL-OUTBOX-SDC1/c2e95926-534b-4836-8135-19e14ef91c8a/cdae6e8c-3951-4634-bfa4-cff074ac4834?timeout=15000&limit=1000
 (as x9UfO7JsDn8BESVX) ...>
2017-05-18T11:40:43.763Z|||ES-Health-Check-Thread||ASDC-BE||ERROR|||10.0.3.1||o.o.sdc.be.dao.impl.ESCatalogDAO||ActivityType=,
 Desc=



Regards,
Ajay Priyadarshi

From: Vitaliy Emporopulo [mailto:vitaliy.emporop...@amdocs.com]
Sent: 17 May 2017 23:59
To: Elhay Efrat; Ajay Priyadarshi; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: SDC portal is not accessible with 502 error

It's configuration.yaml - not configuration.yml.

Sorry my bad

From: Vitaliy Emporopulo
Sent: Wednesday, May 17, 2017 21:20
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: SDC portal is not accessible with 502 error

Hi Ajay,

It looks like SDC fails to connect to the Cassandra cluster. Are all of your 
SDC Docker containers running in a single VM?

To begin with, I would check the connectivity from BE to Cassandra and whether 
the Cassandra cluster IP has been configured correctly. Open a shell session in 
the BE container and look for configuration.yml, cassandraConfig section.

Regards,
Vitaliy

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Elhay Efrat
Sent: Wednesday, May 17, 2017 17:12
To: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Could we share hangout elhayef...@gmail.com<mailto:elhayef...@gmail.com> ?

From: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com> 
[mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 5:08 PM
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: SDC portal is not accessible with 502 error

Yes, all docker containers are up.

Regards,
Ajay Priyadarshi

 Original Message 
Subject: RE: SDC portal is not accessible with 502 error
From: Elhay Efrat mailto:elhay.efr...@amdocs.com>>
Date: 17 May 2017, 19:33
To: Ajay Priyadarshi 
mailto:ajay.priyadar...@ril.com>>,onap-discuss@lists.onap.org
Could you please check you Cassandra Docker if it's up or down

From: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com> 
[mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 4:58 PM
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: SDC portal is not accessible with 502 error

These are stderr logs. If needed more logs I can attach error logs as well.

BE log:

2017-05-17 10:23:05.852:INFO:oejs.SetUIDListener:main: Setting 
umask=02
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}<mailto:ServerConnector@643b1d11%7bHTTP/1.1,%5bhttp/1.1%5d%7d%7b0.0.0.0:8080%7d>
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:8443}
2017-05-17 10:23:05.889:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:05.890:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:05.892:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:05.908:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:14.027:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=5987ms
2017-05-17 10:23:15.089:INFO:c0.0:main: No Spring WebApplicationInitializer 
types detected on classpath
2017-05-17 10:23:16.275:INFO:c0.0:main: Initializing Spring root 
WebApplicationContext
10:23:17,387  INFO plugins:149 - [371d43040623] loaded [shield], sites []
10:23:17,622  INFO transport:80 - [371d43040623] Using 
[org.elasticsearch.shield.transport.ShieldClientTransportService] as transport 
service, overridden by [shield]
10:23:17,623  INFO transport:96 - [371d

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-18 Thread Ajay.Priyadarshi

p.org
Subject: RE: SDC portal is not accessible with 502 error

It's configuration.yaml - not configuration.yml.

Sorry my bad

From: Vitaliy Emporopulo
Sent: Wednesday, May 17, 2017 21:20
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: SDC portal is not accessible with 502 error

Hi Ajay,

It looks like SDC fails to connect to the Cassandra cluster. Are all of your 
SDC Docker containers running in a single VM?

To begin with, I would check the connectivity from BE to Cassandra and whether 
the Cassandra cluster IP has been configured correctly. Open a shell session in 
the BE container and look for configuration.yml, cassandraConfig section.

Regards,
Vitaliy

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Elhay Efrat
Sent: Wednesday, May 17, 2017 17:12
To: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Could we share hangout elhayef...@gmail.com<mailto:elhayef...@gmail.com> ?

From: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com> 
[mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 5:08 PM
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: SDC portal is not accessible with 502 error

Yes, all docker containers are up.

Regards,
Ajay Priyadarshi

 Original Message 
Subject: RE: SDC portal is not accessible with 502 error
From: Elhay Efrat mailto:elhay.efr...@amdocs.com>>
Date: 17 May 2017, 19:33
To: Ajay Priyadarshi 
mailto:ajay.priyadar...@ril.com>>,onap-discuss@lists.onap.org
Could you please check you Cassandra Docker if it's up or down

From: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com> 
[mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 4:58 PM
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: SDC portal is not accessible with 502 error

These are stderr logs. If needed more logs I can attach error logs as well.

BE log:

2017-05-17 10:23:05.852:INFO:oejs.SetUIDListener:main: Setting 
umask=02
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}<mailto:ServerConnector@643b1d11%7bHTTP/1.1,%5bhttp/1.1%5d%7d%7b0.0.0.0:8080%7d>
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:8443}
2017-05-17 10:23:05.889:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:05.890:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:05.892:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:05.908:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:14.027:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=5987ms
2017-05-17 10:23:15.089:INFO:c0.0:main: No Spring WebApplicationInitializer 
types detected on classpath
2017-05-17 10:23:16.275:INFO:c0.0:main: Initializing Spring root 
WebApplicationContext
10:23:17,387  INFO plugins:149 - [371d43040623] loaded [shield], sites []
10:23:17,622  INFO transport:80 - [371d43040623] Using 
[org.elasticsearch.shield.transport.ShieldClientTransportService] as transport 
service, overridden by [shield]
10:23:17,623  INFO transport:96 - [371d43040623] Using 
[org.elasticsearch.shield.transport.netty.ShieldNettyTransport] as transport, 
overridden by [shield]
2017-05-17 10:24:18.085:WARN:oejw.WebAppContext:main: Failed startup of context 
o.e.j.w.WebAppContext@52a86356{/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE}{/catalog-be-1.0.0.war}<mailto:o.e.j.w.WebAppContext@52a86356%7b/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE%7d%7b/catalog-be-1.0.0.war%7d>
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injecti

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-17 Thread Vitaliy Emporopulo

It's configuration.yaml - not configuration.yml.

Sorry my bad

From: Vitaliy Emporopulo
Sent: Wednesday, May 17, 2017 21:20
To: Elhay Efrat ; ajay.priyadar...@ril.com; 
onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

Hi Ajay,

It looks like SDC fails to connect to the Cassandra cluster. Are all of your 
SDC Docker containers running in a single VM?

To begin with, I would check the connectivity from BE to Cassandra and whether 
the Cassandra cluster IP has been configured correctly. Open a shell session in 
the BE container and look for configuration.yml, cassandraConfig section.

Regards,
Vitaliy

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Elhay Efrat
Sent: Wednesday, May 17, 2017 17:12
To: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Could we share hangout elhayef...@gmail.com<mailto:elhayef...@gmail.com> ?

From: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com> 
[mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 5:08 PM
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: SDC portal is not accessible with 502 error

Yes, all docker containers are up.

Regards,
Ajay Priyadarshi

 Original Message 
Subject: RE: SDC portal is not accessible with 502 error
From: Elhay Efrat mailto:elhay.efr...@amdocs.com>>
Date: 17 May 2017, 19:33
To: Ajay Priyadarshi 
mailto:ajay.priyadar...@ril.com>>,onap-discuss@lists.onap.org
Could you please check you Cassandra Docker if it's up or down

From: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com> 
[mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 4:58 PM
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: SDC portal is not accessible with 502 error

These are stderr logs. If needed more logs I can attach error logs as well.

BE log:

2017-05-17 10:23:05.852:INFO:oejs.SetUIDListener:main: Setting 
umask=02
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}<mailto:ServerConnector@643b1d11%7bHTTP/1.1,%5bhttp/1.1%5d%7d%7b0.0.0.0:8080%7d>
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:8443}
2017-05-17 10:23:05.889:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:05.890:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:05.892:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:05.908:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:14.027:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=5987ms
2017-05-17 10:23:15.089:INFO:c0.0:main: No Spring WebApplicationInitializer 
types detected on classpath
2017-05-17 10:23:16.275:INFO:c0.0:main: Initializing Spring root 
WebApplicationContext
10:23:17,387  INFO plugins:149 - [371d43040623] loaded [shield], sites []
10:23:17,622  INFO transport:80 - [371d43040623] Using 
[org.elasticsearch.shield.transport.ShieldClientTransportService] as transport 
service, overridden by [shield]
10:23:17,623  INFO transport:96 - [371d43040623] Using 
[org.elasticsearch.shield.transport.netty.ShieldNettyTransport] as transport, 
overridden by [shield]
2017-05-17 10:24:18.085:WARN:oejw.WebAppContext:main: Failed startup of context 
o.e.j.w.WebAppContext@52a86356{/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE}{/catalog-be-1.0.0.war}<mailto:o.e.j.w.WebAppContext@52a86356%7b/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE%7d%7b/catalog-be-1.0.0.war%7d>
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-17 Thread Vitaliy Emporopulo

Hi Ajay,

It looks like SDC fails to connect to the Cassandra cluster. Are all of your 
SDC Docker containers running in a single VM?

To begin with, I would check the connectivity from BE to Cassandra and whether 
the Cassandra cluster IP has been configured correctly. Open a shell session in 
the BE container and look for configuration.yml, cassandraConfig section.

Regards,
Vitaliy

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Elhay Efrat
Sent: Wednesday, May 17, 2017 17:12
To: ajay.priyadar...@ril.com; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Could we share hangout elhayef...@gmail.com<mailto:elhayef...@gmail.com> ?

From: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com> 
[mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 5:08 PM
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: SDC portal is not accessible with 502 error

Yes, all docker containers are up.

Regards,
Ajay Priyadarshi

 Original Message 
Subject: RE: SDC portal is not accessible with 502 error
From: Elhay Efrat mailto:elhay.efr...@amdocs.com>>
Date: 17 May 2017, 19:33
To: Ajay Priyadarshi 
mailto:ajay.priyadar...@ril.com>>,onap-discuss@lists.onap.org
Could you please check you Cassandra Docker if it's up or down

From: ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com> 
[mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 4:58 PM
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: SDC portal is not accessible with 502 error

These are stderr logs. If needed more logs I can attach error logs as well.

BE log:

2017-05-17 10:23:05.852:INFO:oejs.SetUIDListener:main: Setting 
umask=02
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}<mailto:ServerConnector@643b1d11%7bHTTP/1.1,%5bhttp/1.1%5d%7d%7b0.0.0.0:8080%7d>
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:8443}
2017-05-17 10:23:05.889:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:05.890:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:05.892:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:05.908:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:14.027:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=5987ms
2017-05-17 10:23:15.089:INFO:c0.0:main: No Spring WebApplicationInitializer 
types detected on classpath
2017-05-17 10:23:16.275:INFO:c0.0:main: Initializing Spring root 
WebApplicationContext
10:23:17,387  INFO plugins:149 - [371d43040623] loaded [shield], sites []
10:23:17,622  INFO transport:80 - [371d43040623] Using 
[org.elasticsearch.shield.transport.ShieldClientTransportService] as transport 
service, overridden by [shield]
10:23:17,623  INFO transport:96 - [371d43040623] Using 
[org.elasticsearch.shield.transport.netty.ShieldNettyTransport] as transport, 
overridden by [shield]
2017-05-17 10:24:18.085:WARN:oejw.WebAppContext:main: Failed startup of context 
o.e.j.w.WebAppContext@52a86356{/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE}{/catalog-be-1.0.0.war}<mailto:o.e.j.w.WebAppContext@52a86356%7b/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE%7d%7b/catalog-be-1.0.0.war%7d>
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection of resource 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'component-cassandra-dao': Invocation of init method failed; nested 
exception is java.lang.RuntimeException: Artifact keyspace [sdccomponent] 
failed to connect with error : KEYSPACE_NOT_CONNECTED
at 
org.springframework.beans

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-17 Thread Elhay Efrat

Could we share hangout elhayef...@gmail.com ?

From: ajay.priyadar...@ril.com [mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 5:08 PM
To: Elhay Efrat ; onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

Yes, all docker containers are up.

Regards,
Ajay Priyadarshi

 Original Message 
Subject: RE: SDC portal is not accessible with 502 error
From: Elhay Efrat mailto:elhay.efr...@amdocs.com>>
Date: 17 May 2017, 19:33
To: Ajay Priyadarshi 
mailto:ajay.priyadar...@ril.com>>,onap-discuss@lists.onap.org
Could you please check you Cassandra Docker if it's up or down

From: ajay.priyadar...@ril.com 
[mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 4:58 PM
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

These are stderr logs. If needed more logs I can attach error logs as well.

BE log:

2017-05-17 10:23:05.852:INFO:oejs.SetUIDListener:main: Setting 
umask=02
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:8443}
2017-05-17 10:23:05.889:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:05.890:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:05.892:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:05.908:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:14.027:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=5987ms
2017-05-17 10:23:15.089:INFO:c0.0:main: No Spring WebApplicationInitializer 
types detected on classpath
2017-05-17 10:23:16.275:INFO:c0.0:main: Initializing Spring root 
WebApplicationContext
10:23:17,387  INFO plugins:149 - [371d43040623] loaded [shield], sites []
10:23:17,622  INFO transport:80 - [371d43040623] Using 
[org.elasticsearch.shield.transport.ShieldClientTransportService] as transport 
service, overridden by [shield]
10:23:17,623  INFO transport:96 - [371d43040623] Using 
[org.elasticsearch.shield.transport.netty.ShieldNettyTransport] as transport, 
overridden by [shield]
2017-05-17 10:24:18.085:WARN:oejw.WebAppContext:main: Failed startup of context 
o.e.j.w.WebAppContext@52a86356{/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE}{/catalog-be-1.0.0.war}
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection of resource 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'component-cassandra-dao': Invocation of init method failed; nested 
exception is java.lang.RuntimeException: Artifact keyspace [sdccomponent] 
failed to connect with error : KEYSPACE_NOT_CONNECTED
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:592)


FE log:

2017-05-17 10:23:54.033:INFO:oejs.SetUIDListener:main: Setting umask=02
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8181}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:9443}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:54.053:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:54.055:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:54.070:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:54.383:INFO:oeja.Ann

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-17 Thread Ajay.Priyadarshi

Yes, all docker containers are up.

Regards,
Ajay Priyadarshi


 Original Message 
Subject: RE: SDC portal is not accessible with 502 error
From: Elhay Efrat 
Date: 17 May 2017, 19:33
To: Ajay Priyadarshi ,onap-discuss@lists.onap.org
Could you please check you Cassandra Docker if it’s up or down

From: ajay.priyadar...@ril.com [mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 4:58 PM
To: Elhay Efrat ; onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

These are stderr logs. If needed more logs I can attach error logs as well.

BE log:

2017-05-17 10:23:05.852:INFO:oejs.SetUIDListener:main: Setting 
umask=02
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:8443}
2017-05-17 10:23:05.889:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:05.890:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:05.892:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:05.908:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:14.027:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=5987ms
2017-05-17 10:23:15.089:INFO:c0.0:main: No Spring WebApplicationInitializer 
types detected on classpath
2017-05-17 10:23:16.275:INFO:c0.0:main: Initializing Spring root 
WebApplicationContext
10:23:17,387  INFO plugins:149 - [371d43040623] loaded [shield], sites []
10:23:17,622  INFO transport:80 - [371d43040623] Using 
[org.elasticsearch.shield.transport.ShieldClientTransportService] as transport 
service, overridden by [shield]
10:23:17,623  INFO transport:96 - [371d43040623] Using 
[org.elasticsearch.shield.transport.netty.ShieldNettyTransport] as transport, 
overridden by [shield]
2017-05-17 10:24:18.085:WARN:oejw.WebAppContext:main: Failed startup of context 
o.e.j.w.WebAppContext@52a86356{/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE}{/catalog-be-1.0.0.war}
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection of resource 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'component-cassandra-dao': Invocation of init method failed; nested 
exception is java.lang.RuntimeException: Artifact keyspace [sdccomponent] 
failed to connect with error : KEYSPACE_NOT_CONNECTED
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:592)


FE log:

2017-05-17 10:23:54.033:INFO:oejs.SetUIDListener:main: Setting umask=02
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8181}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:9443}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:54.053:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:54.055:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:54.070:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:54.383:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=67ms
2017-05-17 10:23:54.699:INFO:oejsh.ContextHandler:main: Started 
o.e.j.w.WebAppContext@52a86356{/onboarding,file:///var/lib/jetty/temp/jetty-0.0.0.0-8181-onboarding-fe-1.0.0.war-_onboarding-fe-1.0.0-any-3940833158422955661.dir/webapp/,AVAILABLE}{/onboarding-fe-1.0.0.war}

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-17 Thread Elhay Efrat

Could you please check you Cassandra Docker if it's up or down

From: ajay.priyadar...@ril.com [mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 4:58 PM
To: Elhay Efrat ; onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

These are stderr logs. If needed more logs I can attach error logs as well.

BE log:

2017-05-17 10:23:05.852:INFO:oejs.SetUIDListener:main: Setting 
umask=02
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:8443}
2017-05-17 10:23:05.889:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:05.890:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:05.892:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:05.908:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:14.027:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=5987ms
2017-05-17 10:23:15.089:INFO:c0.0:main: No Spring WebApplicationInitializer 
types detected on classpath
2017-05-17 10:23:16.275:INFO:c0.0:main: Initializing Spring root 
WebApplicationContext
10:23:17,387  INFO plugins:149 - [371d43040623] loaded [shield], sites []
10:23:17,622  INFO transport:80 - [371d43040623] Using 
[org.elasticsearch.shield.transport.ShieldClientTransportService] as transport 
service, overridden by [shield]
10:23:17,623  INFO transport:96 - [371d43040623] Using 
[org.elasticsearch.shield.transport.netty.ShieldNettyTransport] as transport, 
overridden by [shield]
2017-05-17 10:24:18.085:WARN:oejw.WebAppContext:main: Failed startup of context 
o.e.j.w.WebAppContext@52a86356{/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE}{/catalog-be-1.0.0.war}
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection of resource 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'component-cassandra-dao': Invocation of init method failed; nested 
exception is java.lang.RuntimeException: Artifact keyspace [sdccomponent] 
failed to connect with error : KEYSPACE_NOT_CONNECTED
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:592)


FE log:

2017-05-17 10:23:54.033:INFO:oejs.SetUIDListener:main: Setting umask=02
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8181}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:9443}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:54.053:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:54.055:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:54.070:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:54.383:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=67ms
2017-05-17 10:23:54.699:INFO:oejsh.ContextHandler:main: Started 
o.e.j.w.WebAppContext@52a86356{/onboarding,file:///var/lib/jetty/temp/jetty-0.0.0.0-8181-onboarding-fe-1.0.0.war-_onboarding-fe-1.0.0-any-3940833158422955661.dir/webapp/,AVAILABLE}{/onboarding-fe-1.0.0.war}
2017-05-17 10:23:57.821:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=2254ms
2017-05-17 10:23:59.533:INFO:oejsh.ContextHandler:main: S

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-17 Thread Ajay.Priyadarshi

These are stderr logs. If needed more logs I can attach error logs as well.

BE log:

2017-05-17 10:23:05.852:INFO:oejs.SetUIDListener:main: Setting 
umask=02
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:8443}
2017-05-17 10:23:05.889:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:05.890:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:05.892:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:05.908:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:14.027:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=5987ms
2017-05-17 10:23:15.089:INFO:c0.0:main: No Spring WebApplicationInitializer 
types detected on classpath
2017-05-17 10:23:16.275:INFO:c0.0:main: Initializing Spring root 
WebApplicationContext
10:23:17,387  INFO plugins:149 - [371d43040623] loaded [shield], sites []
10:23:17,622  INFO transport:80 - [371d43040623] Using 
[org.elasticsearch.shield.transport.ShieldClientTransportService] as transport 
service, overridden by [shield]
10:23:17,623  INFO transport:96 - [371d43040623] Using 
[org.elasticsearch.shield.transport.netty.ShieldNettyTransport] as transport, 
overridden by [shield]
2017-05-17 10:24:18.085:WARN:oejw.WebAppContext:main: Failed startup of context 
o.e.j.w.WebAppContext@52a86356{/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE}{/catalog-be-1.0.0.war}
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection of resource 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'component-cassandra-dao': Invocation of init method failed; nested 
exception is java.lang.RuntimeException: Artifact keyspace [sdccomponent] 
failed to connect with error : KEYSPACE_NOT_CONNECTED
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:592)


FE log:

2017-05-17 10:23:54.033:INFO:oejs.SetUIDListener:main: Setting umask=02
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8181}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:9443}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:54.053:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:54.055:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:54.070:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:54.383:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=67ms
2017-05-17 10:23:54.699:INFO:oejsh.ContextHandler:main: Started 
o.e.j.w.WebAppContext@52a86356{/onboarding,file:///var/lib/jetty/temp/jetty-0.0.0.0-8181-onboarding-fe-1.0.0.war-_onboarding-fe-1.0.0-any-3940833158422955661.dir/webapp/,AVAILABLE}{/onboarding-fe-1.0.0.war}
2017-05-17 10:23:57.821:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=2254ms
2017-05-17 10:23:59.533:INFO:oejsh.ContextHandler:main: Started 
o.e.j.w.WebAppContext@35ef1869{/sdc1,file:///var/lib/jetty/temp/jetty-0.0.0.0-8181-catalog-fe-1.0.0.war-_catalog-fe-1.0.0-any-4644672237465305283.dir/webapp/,AVAILABLE}{/catalog-fe-1.0.0.war}
2017-05-17 10:23:59.540:INFO:oejs.AbstractConnector:main: Started 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8181}
2017-05-17 10:23:59.544:INFO:oejus.SslContextFactory:main: 
x509=X509@6ecab872(jetty,h=[jetty.eclipse.org],w=[]) for 
SslContextFactory@48eb9836(file:///var/lib/jetty/etc/keystore,file:///var/lib/jetty/etc/keystore)
2017-05-17 10:23:59.552:INFO:oejus.SslContextFactory:main: 
x509=X509@6c518474(mykey,h=[],w=[]) for 
SslContextFactory@48eb9836(file:///var/lib/jetty/etc/keystore,file:///var/lib/jetty/etc/keystore)
2017-05-17 10:23:59.563:INFO:oejs.AbstractConnector:main: Started 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-17 Thread Elhay Efrat

Could you please share BE and FE log ?

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
ajay.priyadar...@ril.com
Sent: Wednesday, May 17, 2017 4:20 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] SDC portal is not accessible with 502 error

Hello team,

We are installing ONAP on Red Hat OSP-10 .

My portal is accessible while trying to access the SDC, I am getting 502 bad 
gateway (attached image). What are the possible reasons of this error.
I tried to access the page directly and getting same response.

[cid:image001.jpg@01D2CF2C.592C93D0]

Regards,
Ajay Kr. Priyadarshi
SDM QA Team
Reliance Jio Infocomm Limited
Mobile: +91-9958880174
Direct : 1246625832
VOIP : 11832

"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."
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

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] SDC portal is not accessible with 502 error

16 matches

Site Navigation

Mail list logo

Footer information