Hi Supantho, It seems the dmaap-plugin is experiencing a failure to communicate with the DMaaP Bus Controller application.
Can you first verify that the application is accessible? To do so you can make sure that the BC service exposes a port for HTTP communication: kubectl get svc -n onap | grep dmaap-bc Then using that node port(I think its 30241) mapped to 8080, you can make a request to bus controller asking for its health status curl http://<node-ip>:<nodeport>/webapi/info -I Please let me know if that responds with a two hundred series response code. Best Regards Joe ________________________________ From: [email protected] <[email protected]> on behalf of Banerjee, Supantho via Lists.Onap.Org <[email protected]> Sent: 24 March 2020 13:02 To: [email protected] <[email protected]>; Joseph O'Leary <[email protected]>; Amol Kulkarni <[email protected]> Cc: Henrik Andersson B <[email protected]>; Vijay VK <[email protected]> Subject: Re: [onap-discuss] FW: [onap-discuss] # data file Collector Hi Joseph, Vijay We tried installing the El-Alto version of DFC by following the steps shared by you. We uninstalled the older blueprint file and deleted it before doing the installation. But the installation failed with the attached logs. Please suggest how can we successfully complete the installation for DFC. Also, the output of POD healthcheck as requested are given below: kubectl get pods -n onap | grep dmaap-dr dev-dmaap-dmaap-dr-db-0 1/1 Running 0 45h dev-dmaap-dmaap-dr-db-1 1/1 Running 0 45h dev-dmaap-dmaap-dr-node-0 2/2 Running 0 45h dev-dmaap-dmaap-dr-prov-f7f5bc97f-7v4bd 2/2 Running 0 45h Regards Supantho Banerjee Senior Solution Architect Harman Connected Services. From: [email protected] <[email protected]> On Behalf Of Joseph O'Leary Sent: Monday, March 23, 2020 7:33 PM To: Amol Kulkarni <[email protected]> Cc: Henrik Andersson B <[email protected]>; [email protected]; Vijay VK <[email protected]> Subject: [EXTERNAL] Re: [onap-discuss] FW: [onap-discuss] # data file Collector I think between Dublin and El Alto there were some non-backwards compatible changes to the config of DFC, which means you may need to use a different blueprint, That can be found here<https://clicktime.symantec.com/3C4ob6bzexAWg9HXKqpHumS7Vc?u=https%3A%2F%2Fgit.onap.org%2Fdcaegen2%2Fcollectors%2Fdatafile%2Ftree%2Fdatafile-app-server%2Fdpo%2Fblueprints%2Fk8s-datafile.yaml%3Fh%3Delalto>, and since you have already got to the point where you have the service running I'll assume you know what to do with the blueprint. If not then around the 5 minute mark of this video <https://clicktime.symantec.com/36WtQwEJ6JrzQh6NFuB9wMo7Vc?u=https%3A%2F%2Fwiki.onap.org%2Fpages%2Fviewpage.action%3FpageId%3D71835025%26preview%3D%2F71835025%2F71837151%2FDMaaPPluginDemo.mp4> might be helpful. Best Regards Joe ________________________________ From: Amol Kulkarni <[email protected]<mailto:[email protected]>> Sent: 23 March 2020 13:55 To: Joseph O'Leary <[email protected]<mailto:[email protected]>> Cc: Henrik Andersson B <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>; Vijay VK <[email protected]<mailto:[email protected]>> Subject: Re: [onap-discuss] FW: [onap-discuss] # data file Collector Thanks Joseph. I will share it shortly. By the way - as you know we have deployed EL-Alto release however DFC is using Dublin release. Is there any way to upgrade DFC it to El-Alto? Request to share steps or reference link. Regards, Amol On Mon, 23 Mar, 2020, 7:19 PM Joseph O'Leary, <[email protected]<mailto:[email protected]>> wrote: Hi Amol, Nice to meet you, I'm not quiet sure whats happening in that environment, >From the looks of it the service cannot communicate with the data router >provisioning server. Can you check if that pod is online, online, by running something like kubectl get pods -n <onap-namespace> | grep dmaap-dr then send a rest query to see if the server is healthy, would be something like curl -k https://node-ip:30269/internal/prov Could you let me know the output to those ? /Joe ________________________________ From: Amol Kulkarni <[email protected]<mailto:[email protected]>> Sent: 23 March 2020 13:36 To: Henrik Andersson B <[email protected]<mailto:[email protected]>> Cc: Joseph O'Leary <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>; Vijay VK <[email protected]<mailto:[email protected]>> Subject: Re: [onap-discuss] FW: [onap-discuss] # data file Collector Hi Joseph, Could you please help here to fix the setup issues? Regards, Amol On Mon, 23 Mar, 2020, 6:34 PM Henrik Andersson B, <[email protected]<mailto:[email protected]>> wrote: Hi again, I am afraid I am not very good at the installation procedures. Maybe @Joseph O'Leary<mailto:[email protected]> can help more with this? /Henrik Från: Amol Kulkarni <[email protected]<mailto:[email protected]>> Skickat: den 23 mars 2020 13:43 Till: Henrik Andersson B <[email protected]<mailto:[email protected]>> Kopia: [email protected]<mailto:[email protected]>; Vijay VK <[email protected]<mailto:[email protected]>> Ämne: Re: [onap-discuss] FW: [onap-discuss] # data file Collector Hi Henrik, Thanks for reply. Request to provide further inputs on below topics - 1. Any reference link which will help us update it to El-alto release. 2. Right now we are getting following timeout issues when DFC try to connect to DR however the mentioned IP is not there in the deployment EKS cluster. Your inputs will certainly help. PFB Logs details: ============= org.onap.dcaegen2.collectors.datafile.tasks.DataRouterPublisher |2020-03-22T18:08:37.997Z |WARN |Unable to send file to DataRouter. Data: /tmp/onap_datafile/A1584899539.2258172.xml.gz |RequestID=A1584899539.2258172.xml.gz |java.net.ConnectException: Timeout connecting to [dmaap-dr-prov.onap.svc.cluster.local/10.43.141.199:8443<http://10.43.141.199:8443/>]\n\tat org.apache.http.nio.pool.RouteSpecificPool.timeout(RouteSpecificPool.java:174)\n\tat org.apache.http.nio.pool.AbstractNIOConnPool.requestTimeout(AbstractNIOConnPool.java:629)\n\tat org.apache.http.nio.pool.AbstractNIOConnPool$InternalSessionRequestCallback.timeout(AbstractNIOConnPool.java:899)\n\tat org.apache.http.impl.nio.reactor.SessionRequestImpl.timeout(SessionRequestImpl.java:183)\n\tat org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processTimeouts(DefaultConnectingIOReactor.java:210)\n\tat org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:155)\n\tat org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:348)\n\tat org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:221)\n\tat org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)\n\t... 1 common frames omitted\nWrapped by: java.util.concurrent.ExecutionException: java.net.ConnectException: Timeout connecting to [dmaap-dr-prov.onap.svc.cluster.local/10.43.141.199:8443<http://10.43.141.199:8443/>]\n\tat org.apache.http.concurrent.BasicFuture.getResult(BasicFuture.java:71)\n\tat org.apache.http.concurrent.BasicFuture.get(BasicFuture.java:84)\n\tat org.apache.http.impl.nio.client.FutureWrapper.get(FutureWrapper.java:70)\n\tat org.onap.dcaegen2.collectors.datafile.service.producer.DmaapProducerHttpClient.getDmaapProducerResponseWithRedirect(DmaapProducerHttpClient.java:93)\n\t... 20 common frames omitted\nWrapped by: org.onap.dcaegen2.collectors.datafile.exceptions.DatafileTaskException: Unable to create web client.\n\tat org.onap.dcaegen2.collectors.datafile.service.producer.DmaapProducerHttpClient.getDmaapProducerResponseWithRedirect(DmaapProducerHttpClient.java:97)\n\tat org.onap.dcaegen2.collectors.datafile.tasks.DataRouterPublisher.publishFile(DataRouterPublisher.java:106)\n\tat reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:118)\n\tat reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1505)\n\tat reactor.core.publisher.MonoProcessor.subscribe(MonoProcessor.java:457)\n\tat reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:60)\n\tat reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:60)\n\tat reactor.core.publisher.Mono.subscribe(Mono.java:3695)\n\tat reactor.core.publisher.FluxRetryWhen$RetryWhenMainSubscriber.resubscribe(FluxRetryWhen.java:183)\n\tat reactor.core.publisher.FluxRetryWhen$RetryWhenOtherSubscriber.onNext(FluxRetryWhen.java:229)\n\tat reactor.core.publisher.FluxFlatMap$FlatMapMain.tryEmit(FluxFlatMap.java:501)\n\tat reactor.core.publisher.FluxFlatMap$FlatMapInner.onNext(FluxFlatMap.java:943)\n\tat reactor.core.publisher.MonoDelay$MonoDelayRunnable.run(MonoDelay.java:117)\n\tat reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:50)\n\tat reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:27)\n\tat java.util.concurrent.FutureTask.run(FutureTask.java:266)\n\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)\n\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\n\tat java.lang.Thread.run(Thread.java:748)\n | |parallel-1 | ========================================================================= Regards, Amol On Mon, 23 Mar, 2020, 6:01 PM Henrik Andersson B, <[email protected]<mailto:[email protected]>> wrote: Hi Amol, It seems like you are actually running code from the Dublin release. The class CloudConfiguration, seen in the log, has been removed in the El-Alto release. So I think it might be a software version problem. Please check that the Datafile Collector actually is from the El-Alto release. Hope this helps! Henrik Från: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> För Amol via Lists.Onap.Org<https://clicktime.symantec.com/3MSYPWA4eNeeveAzv6FwUhb7Vc?u=http%3A%2F%2FLists.Onap.Org> Skickat: den 21 mars 2020 09:19 Till: Vijay VK <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Ämne: Re: [onap-discuss] FW: [onap-discuss] # data file Collector Hi Henrik,Joe & Vijay, PFA all logs belong to DFC. Request to provide a way ahead. Hi Vijay, We have followed DFC deployment as mentioned in the below link. https://wiki.onap.org/pages/viewpage.action?pageId=60891239<https://clicktime.symantec.com/34hJ8tVsBNTse7PcHEsNvds7Vc?u=https%3A%2F%2Fwiki.onap.org%2Fpages%2Fviewpage.action%3FpageId%3D60891239> I can see the mentioned link does DFC deployment belong to Dublin release, however is there any way to do DFC deployment belong to El-Alto release. Please let us know reference link. Regards, Amol -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20358): https://lists.onap.org/g/onap-discuss/message/20358 Mute This Topic: https://lists.onap.org/mt/72310785/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
