HI, Dan,
Yes. I do see both error.log and debun.log files are growing in sdnc pod, such
as, the following from the error.log keep coming:
2020-09-04T17:12:48.166Z||070548093-246055|INTERNAL||||WARN|900|UnknownError|Authentication
failed for token submission [org.apache.shiro.authc.UsernamePasswordToken -
admin, rememberMe=false]. Possible unexpected error? (Typical or expected
login exceptions should extend from AuthenticationException).
org.opendaylight.aaa.api.AuthenticationException: UserName / Password not
found\n at
org.opendaylight.aaa.shiro.idm.IdmLightProxy.dbAuthenticate(IdmLightProxy.java:105)\n
at
java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660)\n
at
org.opendaylight.aaa.shiro.idm.IdmLightProxy.authenticate(IdmLightProxy.java:66)\n
at
org.opendaylight.aaa.shiro.idm.IdmLightProxy.authenticate(IdmLightProxy.java:39)\n
at
org.opendaylight.aaa.shiro.tokenauthrealm.auth.HttpBasicAuth.generateAuthentication(HttpBasicAuth.java:102)\n
at
org.opendaylight.aaa.shiro.tokenauthrealm.auth.HttpBasicAuth.validate(HttpBasicAuth.java:122)\n
at
org.opendaylight.aaa.shiro.realm.TokenAuthRealm.doGetAuthenticationInfo(TokenAuthRealm.java:147)\n
at
org.apache.shiro.realm.AuthenticatingRealm.getAuthenticationInfo(AuthenticatingRealm.java:568)\n
at
org.apache.shiro.authc.pam.ModularRealmAuthenticator.doSingleRealmAuthentication(ModularRealmAuthenticator.java:180)\n
at
org.apache.shiro.authc.pam.ModularRealmAuthenticator.doAuthenticate(ModularRealmAuthenticator.java:267)\n
at
org.apache.shiro.authc.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:198)\n
at
org.apache.shiro.mgt.AuthenticatingSecurityManager.authenticate(AuthenticatingSecurityManager.java:106)\n
at
org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:270)\n
at
org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)\n
at
org.opendaylight.aaa.authenticator.ODLAuthenticator.login(ODLAuthenticator.java:80)\n
at
org.opendaylight.aaa.authenticator.ODLAuthenticator.authenticate(ODLAuthenticator.java:50)\n
at Proxy401993dd_293e_4cb5_8038_af85a566ddec.authenticate(Unknown Source)\n
at
org.jolokia.osgi.security.ServiceAuthenticationHttpContext.handleSecurity(ServiceAuthenticationHttpContext.java:72)\n
at
org.ops4j.pax.web.service.internal.WebContainerContextWrapper.handleSecurity(WebContainerContextWrapper.java:46)\n
at
org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:69)\n
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)\n
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)\n
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)\n
at
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)\n
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)\n
at
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)\n
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340)\n
at
org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:293)\n
at
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)\n
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)\n at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)\n
at
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)\n
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1242)\n
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)\n
at
org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80)\n
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)\n
at org.eclipse.jetty.server.Server.handle(Server.java:503)\n at
org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364)\n at
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260)\n
at
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)\n
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)\n at
org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118)\n at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)\n
at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)\n
at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)\n
at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)\n
at
org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)\n
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)\n
at
org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)\n
at java.lang.Thread.run(Thread.java:748)
Thanks,
Xin Miao
Solution Engineering
Fujitsu Network Communication
(W)972-479-2263 (M)469-268-5226
2811 Telecom Drive
Richardson, TX 75081, USA
From: Miao, Xin
Sent: Friday, September 4, 2020 11:28 AM
To: Kaleem, Mehreen <[email protected]>; TIMONEY, DAN <[email protected]>
Cc: Dsilva, Franklin <[email protected]>; [email protected]
Subject: RE: [onap-sdnc] Rpc logs and DG logs not printed out in SDNC in Master
deployment
Hi, Mehreen,
Did you check the logs in all of the 3 sdnc-{0,1,2} pods?
Thanks,
Xin Miao
Solution Engineering
Fujitsu Network Communication
(W)972-479-2263 (M)469-268-5226
2811 Telecom Drive
Richardson, TX 75081, USA
From: Miao, Xin
Sent: Thursday, September 3, 2020 7:30 AM
To: Kaleem, Mehreen
<[email protected]<mailto:[email protected]>>; TIMONEY, DAN
<[email protected]<mailto:[email protected]>>
Cc: Dsilva, Franklin
<[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>
Subject: [onap-sdnc] Rpc logs and DG logs not printed out in SDNC in Master
deployment
Hi, Dan/Team,
Any idea on this? Or, we have missed something very significant?
Thanks a lot for your help!
Xin Miao
From: Kaleem, Mehreen
Sent: Wednesday, September 2, 2020 8:12 AM
To: TIMONEY, DAN <[email protected]<mailto:[email protected]>>; Miao, Xin
<[email protected]<mailto:[email protected]>>
Cc: Dsilva, Franklin
<[email protected]<mailto:[email protected]>>
Subject: Re: [onap-sdnc] DMAAPLISTENERROOT env parm
Hi Dan,
The rpc info logs as well as the DG logs are not getting printed in the Karaf
Logs. Can you help us to know if this setting was delibrately changed and also
why these logs are not visible if settings were not changed.
Thanks,
Mehreen
________________________________
From: TIMONEY, DAN <[email protected]<mailto:[email protected]>>
Sent: Wednesday, September 2, 2020 4:52 PM
To: Miao, Xin <[email protected]<mailto:[email protected]>>
Cc: Dsilva, Franklin
<[email protected]<mailto:[email protected]>>; Kaleem,
Mehreen <[email protected]<mailto:[email protected]>>
Subject: Re: [onap-sdnc] DMAAPLISTENERROOT env parm
Xin,
It should be set to /opt/onap/sdnc/dmaap-listener (with or without a trailing
/). I see that's now the default value set in start-dmaap-listener.sh if it's
not set in the helm chart.
I checked the helm charts in oom and see that DMAAPLISTENERROOT is not
currently set , so it should be using that default value.
Are you seeing any errors from dmaap-listener? Is it coming up?
If dmaap-listener is coming up but you're not getting ESR events, the other
place I'd check would be the properties file.
Am I correct in thinking that the ESR events are handled by
org.onap.ccsdk.sli.northbound.dmaapclient.SdncAaiDmaapConsumer? If so, then
the property file in question would be in
oom/kubernetes/sdnc/components/dmaap-listener/resources/config/aai.properties.
Comparing that to the config for the OOF interface in the same directory, the
setting I'd focus on would be ServiceName. I believe that should be set to:
ServiceName
=message-router.{{.Release.Namespace}}:{{.Values.config.dmaapPort}}/events
In aai.properties, it's set to this, which doesn't seem correct:
ServiceName =dmaap-v1.dev.dmaap.dt.saat.acsi.openecomp.org/events
Hope this helps!
Dan
From: "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Date: Wednesday, September 2, 2020 at 6:50 AM
To: "TIMONEY, DAN" <[email protected]<mailto:[email protected]>>
Cc: "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>,
"[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Subject: [onap-sdnc] DMAAPLISTENERROOT env parm
Hi, Dan,
In the following JIRA ticket, you made a comment as the DMAAPLISTENERROOT has
been set to '/opt/onap/sdnc/dmaap-listener/'.
https://jira.onap.org/browse/CCSDK-2388<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_CCSDK-2D2388&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=Ms-DNhR23dO4sQFfYRm4ow&m=1Son7XAnVhog9N1Mkg9ihj5lLXVrvawudu6uRJzB04w&s=0rZV-eRAApbj40OxSzEmSQLxTZjKAfXVgEAjkDTjRA8&e=>
My question is should it be set to '/opt/onap/sdnc/dmaap-listener/lib/' or
'/opt/onap/sdnc/dmaap-listener/'?
How do I verify if the parm is set correct or not?
In my newly deployed 'master' ONAP instance, sdnc-dmaap-listener still cannot
listen to 'ESR' event so that topology discovery cannot be triggered
automatically at external domain controller registration.
Thanks a lot for your advice.
Xin Miao
Solution Engineering
Fujitsu Network Communication
(W)972-479-2263 (M)469-268-5226
2811 Telecom Drive
Richardson, TX 75081, USA
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22064): https://lists.onap.org/g/onap-discuss/message/22064
Mute This Topic: https://lists.onap.org/mt/76605484/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
