It's configuration.yaml - not configuration.yml. Sorry my bad
From: Vitaliy Emporopulo Sent: Wednesday, May 17, 2017 21:20 To: Elhay Efrat <elhay.efr...@amdocs.com>; 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 <elhay.efr...@amdocs.com<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 <elhay.efr...@amdocs.com<mailto:elhay.efr...@amdocs.com>> Date: 17 May 2017, 19:33 To: Ajay Priyadarshi <ajay.priyadar...@ril.com<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 <elhay.efr...@amdocs.com<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.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}<mailto:ServerConnector@643b1d11%7bHTTP/1.1,%5bhttp/1.1%5d%7d%7b0.0.0.0:8181%7d> 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}<mailto:o.e.j.w.WebAppContext@52a86356%7b/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%7d%7b/onboarding-fe-1.0.0.war%7d> 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}<mailto:o.e.j.w.WebAppContext@35ef1869%7b/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%7d%7b/catalog-fe-1.0.0.war%7d> 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}<mailto:ServerConnector@643b1d11%7bHTTP/1.1,%5bhttp/1.1%5d%7d%7b0.0.0.0:8181%7d> 2017-05-17 10:23:59.544:INFO:oejus.SslContextFactory:main: x509=X509@6ecab872(jetty,h=[jetty.eclipse.org],w=[])<mailto: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.0.0:9443} 2017-05-17 10:23:59.563:INFO:oejs.Server:main: Started @6128ms Regards, Ajay From: Elhay Efrat [mailto:elhay.efr...@amdocs.com] Sent: 17 May 2017 19:11 To: Ajay Priyadarshi; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: SDC portal is not accessible with 502 error Could you please share BE and FE log ? From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of ajay.priyadar...@ril.com<mailto:ajay.priyadar...@ril.com> Sent: Wednesday, May 17, 2017 4:20 PM To: onap-discuss@lists.onap.org<mailto: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@01D2CF54.993F2320] 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 "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 "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 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 onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss