https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-717 controller <p>Remote Netconf Server Connection With new cloned Opendaylight controller(Cloned on Aug 21, 2013) failed with java null pointer exception.</p> <p>Steps followed to replicate the issue:</p> <p>1. Clone new Opnedaylight controller<br/> 2. Created the xml file and added the file in configuration/initial folder of the distribution that we are running<br/> 3. Added the remote device configuration yang files in cache/schema directory<br/> 4. Run the controller</p> <p>Running the controller failed to initialize sal and throws java null pointer exception as below</p> <p>2014-08-22 10:59:21.743 IST <span class="error">&#91;remote-connector-processing-executor-2&#93;</span> WARN o.o.c.s.c.netconf.NetconfDevice - RemoteDevice</p> {m10sachi}: Unexpected error resolving device sources: java.lang.NullPointerException<br/> 2014-08-22 10:59:21.770 IST <span class="error">&#91;remote-connector-processing-executor-2&#93;</span> ERROR o.o.c.s.c.netconf.NetconfDevice - RemoteDevice{m10sachi} <p>: Initialization in sal failed, disconnecting from device<br/> java.lang.NullPointerException: null<br/> at org.opendaylight.controller.sal.connect.netconf.NetconfStateSchemas.create(NetconfStateSchemas.java:128) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.controller.sal.connect.netconf.NetconfStateSchemas.create(NetconfStateSchemas.java:118) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.controller.sal.connect.netconf.NetconfStateSchemas.access$000(NetconfStateSchemas.java:35) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.controller.sal.connect.netconf.NetconfStateSchemas$NetconfStateSchemasResolverImpl.resolve(NetconfStateSchemas.java:53) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.controller.sal.connect.netconf.NetconfDevice$DeviceSourcesResolver.call(NetconfDevice.java:222) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.controller.sal.connect.netconf.NetconfDevice$DeviceSourcesResolver.call(NetconfDevice.java:202) ~<span class="error">&#91;na:na&#93;</span><br/> at java.util.concurrent.FutureTask.run(FutureTask.java:262) ~<span class="error">&#91;na:1.7.0_55&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) <span class="error">&#91;na:1.7.0_55&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) <span class="error">&#91;na:1.7.0_55&#93;</span><br/> at java.lang.Thread.run(Thread.java:744) <span class="error">&#91;na:1.7.0_55&#93;</span><br/> 2014-08-22 10:59:21.771 IST <span class="error">&#91;remote-connector-processing-executor-2&#93;</span> WARN o.o.c.s.c.n.l.NetconfDeviceCommunicator - RemoteDevice</p> {m10sachi} <p>: Session terminated Session closed</p> <p>Operating System: Linux<br/> Platform: PC</p> CONTROLLER-717

Remote Netconf Server Initialization Failed With NullPointerException

Bug Resolved Done Maros Marsalek Sachi Gupta Fri, 22 Aug 2014 06:23:12 +0000 Tue, 25 Jul 2023 08:24:06 +0000 Wed, 3 Sep 2014 10:02:49 +0000 netconf 0 5 <p>Hi, I have fixed the NullPointer exception. But it looks like your device does not respond correctly to get request with filter netconf-state/schemas. So it looks like your device supports netconf monitoring, but does not expose any schemas.</p> <p>Here is the commit to fix null pointer:<br/> <a href="https://git.opendaylight.org/gerrit/#/c/10158/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/10158/</a></p> <p>But since your device does not support netconf monitoring, you would have to place your schemas into cache folder before ODL start.</p> <p>Hi,</p> <p>The null pointer exception is resolved with your patch</p> <p>Have added the schema files in cache/schema folder but still getting one more exception as below:</p> <p>2014-08-22 15:01:49.289 IST <span class="error">&#91;remote-connector-processing-executor-2&#93;</span> WARN o.o.c.s.c.n.NetconfStateSchemas - RemoteDevice</p> {m10sachi}: Unable to detect available schemas, get to (urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring?revision=2010-10-04)netconf-state/(urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring?revision=2010-10-04)schemas was empty<br/> 2014-08-22 15:01:49.313 IST <span class="error">&#91;remote-connector-processing-executor-3&#93;</span> ERROR o.o.c.s.c.netconf.NetconfDevice - RemoteDevice{m10sachi} <p>: Initialization in sal failed, disconnecting from device<br/> java.lang.IllegalStateException: RemoteDevice</p> {m10sachi}: No more sources for schema context<br/> at org.opendaylight.controller.sal.connect.netconf.NetconfDevice$RecursiveSchemaSetup.setUpSchema(NetconfDevice.java:305) <span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.sal.connect.netconf.NetconfDevice$RecursiveSchemaSetup.run(NetconfDevice.java:294) <span class="error">&#91;bundlefile:na&#93;</span><br/> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) <span class="error">&#91;na:1.7.0_55&#93;</span><br/> at java.util.concurrent.FutureTask.run(FutureTask.java:262) <span class="error">&#91;na:1.7.0_55&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) <span class="error">&#91;na:1.7.0_55&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) <span class="error">&#91;na:1.7.0_55&#93;</span><br/> at java.lang.Thread.run(Thread.java:744) <span class="error">&#91;na:1.7.0_55&#93;</span><br/> 2014-08-22 15:01:49.316 IST <span class="error">&#91;remote-connector-processing-executor-3&#93;</span> WARN o.o.c.s.c.n.l.NetconfDeviceCommunicator - RemoteDevice{m10sachi} <p>: Session terminated Session closed</p> <p>I see, can you show me the hello message produced by your device ?</p> <p>Hi Maros,</p> <p>The hello message produced by the device is as follows:</p> <p>&lt;hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"&gt;<br/> &lt;capabilities&gt;<br/> &lt;capability&gt;urn:ietf:params:netconf:base:1.0&lt;/capability&gt;<br/> &lt;capability&gt;urn:ietf:params:netconf:capability:candidate:1.0&lt;/capability&gt;<br/> &lt;capability&gt;urn:ietf:params:netconf:capability:confirmed-commit:1.0&lt;/capability&gt;<br/> &lt;capability&gt;urn:ietf:params:netconf:capability:validate:1.0&lt;/capability&gt;<br/> &lt;capability&gt;urn:ietf:params:netconf:capability:url:1.0?scheme=http,ftp,file&lt;/capability&gt;<br/> &lt;capability&gt;urn:ietf:params:xml:ns:netconf:base:1.0&lt;/capability&gt;<br/> &lt;capability&gt;urn:ietf:params:xml:ns:netconf:capability:candidate:1.0&lt;/capability&gt;<br/> &lt;capability&gt;urn:ietf:params:xml:ns:netconf:capability:confirmed-commit:1.0&lt;/capability&gt;<br/> &lt;capability&gt;urn:ietf:params:xml:ns:netconf:capability:validate:1.0&lt;/capability&gt;<br/> &lt;capability&gt;urn:ietf:params:xml:ns:netconf:capability:url:1.0?protocol=http,ftp,file&lt;/capability&gt;<br/> &lt;capability&gt;<a href="http://xml.juniper.net/netconf/junos/1.0" class="external-link" target="_blank" rel="nofollow noopener">http://xml.juniper.net/netconf/junos/1.0</a>&lt;/capability&gt;<br/> &lt;capability&gt;<a href="http://yang.juniper.net/yang/1.1/jc?module=configuration" class="external-link" target="_blank" rel="nofollow noopener">http://yang.juniper.net/yang/1.1/jc?module=configuration</a>&lt;/capability&gt;<br/> &lt;capability&gt;urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring&lt;/capability&gt;<br/> &lt;capability&gt;<a href="http://xml.juniper.net/dmi/system/1.0" class="external-link" target="_blank" rel="nofollow noopener">http://xml.juniper.net/dmi/system/1.0</a>&lt;/capability&gt;<br/> &lt;/capabilities&gt;<br/> &lt;session-id&gt;27216&lt;/session-id&gt;<br/> &lt;/hello&gt;</p> <p>Looking at the hello message, not many yang based capabilities there. Except maybe: &lt;capability&gt;<a href="http://yang.juniper.net/yang/1.1/jc?module=configuration" class="external-link" target="_blank" rel="nofollow noopener">http://yang.juniper.net/yang/1.1/jc?module=configuration</a>&lt;/capability&gt;. What yang modules did you put under cache/schema folder ? </p> <p>Or what yang modules do you expect to be downloaded from the device and used ?</p> <p>Because your device provides no schemas, and in hello message there is maybe one yang schema reported. In case you need to override the capabilities from hello message, there is a way via netconf-connector configuretion.</p> <p>Hi Maros,</p> <p>I have already added configuration.yang file in cache/schema folder, but faced the above mentioned issue.</p> <p>Note: The same setup was working fine with the older odl code(Cloned on June 19,2014) but showing the issues with new odl code(Cloned on Aug 21, 2014)</p> <p>Can you show me the whole log ? or can I connect to your device from my PC to debug ?</p> <p>Hi Maros,</p> <p>Device does not have internet connectivity, so you will not be able to connect to my netconf device.</p> <p>Sharing with you the log file.</p> <p>Attachment Opendaylight.log:26-08-2014 has been added with description: Log File Attached</p> <p>Ok,</p> <p>So your device has this capability in hello message<br/> <a href="http://yang.juniper.net/yang/1.1/jc?module=configuration" class="external-link" target="_blank" rel="nofollow noopener">http://yang.juniper.net/yang/1.1/jc?module=configuration</a><br/> without revision.</p> <p>Netconf-connector currently ignores capabilities without revision parameter.</p> <p>What you can do as a workaround:</p> <p>1. add revision to the schema in cache/schema folder.<br/> 2. change configuration of netconf-connector, by adding this list property:<br/> &lt;yang-module-capabilities&gt;<br/> &lt;capability&gt;<br/> <a href="http://yang.juniper.net/yang/1.1/jc?module=configuration?revision=YYYY-MM-DD" class="external-link" target="_blank" rel="nofollow noopener">http://yang.juniper.net/yang/1.1/jc?module=configuration?revision=YYYY-MM-DD</a><br/> &lt;/capability&gt;<br/> &lt;/yang-module-capabilities&gt;</p> <p>Hi Maros,<br/> Are you suggesting to put the capability as added in the last line of attached file(snapshot.txt) of 99-netconf-connector.xml?<br/> i have added configuration@1970-01-01.yang file in cache/schema folder but getting the exception </p> <p>Exception:<br/> 2014-08-27 19:07:14.139 IST <span class="error">&#91;config-pusher&#93;</span> ERROR o.o.c.l.b.i.UncaughtExceptionPolicy - Thread Thread<span class="error">&#91;config-pusher,5,main&#93;</span> died because of an uncaught exception<br/> java.lang.IllegalStateException: Max wait for capabilities reached.Not enough capabilities for ConfigSnapshot</p> {configSnapshot='&lt;data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"&gt;&lt;modules xmlns="urn:opendaylight:params:xml:ns:yang:controller:config"&gt;&lt;module&gt;&lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;prefix:sal-netconf-connector&lt;/type&gt;&lt;name&gt;sachi&lt;/name&gt;&lt;address xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;1.1.1.7&lt;/address&gt;&lt;port xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;830&lt;/port&gt;&lt;username xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;tcs&lt;/username&gt;&lt;password xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;tcs@1234&lt;/password&gt;&lt;tcp-only xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;false&lt;/tcp-only&gt;&lt;event-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;&lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:netty"&gt;prefix:netty-event-executor&lt;/type&gt;&lt;name&gt;global-event-executor&lt;/name&gt; &lt;/event-executor&gt;&lt;binding-registry xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;&lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding"&gt;prefix:binding-broker-osgi-registry&lt;/type&gt;&lt;name&gt;binding-osgi-broker&lt;/name&gt; &lt;/binding-registry&gt;&lt;dom-registry xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;&lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:dom"&gt;prefix:dom-broker-osgi-registry&lt;/type&gt;&lt;name&gt;dom-broker&lt;/name&gt; &lt;/dom-registry&gt;&lt;client-dispatcher xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;&lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:config:netconf"&gt;prefix:netconf-client-dispatcher&lt;/type&gt;&lt;name&gt;global-netconf-dispatcher&lt;/name&gt; &lt;/client-dispatcher&gt;&lt;processing-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;&lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:threadpool"&gt;prefix:threadpool&lt;/type&gt;&lt;name&gt;global-netconf-processing-executor&lt;/name&gt; &lt;/processing-executor&gt; &lt;/module&gt; &lt;/modules&gt; &lt;/data&gt; ', capabilities=[http://yang.juniper.net/yang/1.1/jc?module=configuration&amp;revision=1970-01-01, urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf?module=odl-sal-netconf-connector- cfg&amp;revision=2013-10-28]} <p>. Expected but not found: <span class="error">&#91;urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf?module=odl-sal-netconf-connector- cfg&amp;revision=2013-10-28, http://yang.juniper.net/yang/1.1/jc?module=configuration&amp;revision=1970-01-01&#93;</span><br/> at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.getOperationServiceWithRetries(ConfigPusherImpl.java:158) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.pushConfigWithConflictingVersionRetries(ConfigPusherImpl.java:134) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.internalPushConfigs(ConfigPusherImpl.java:111) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.process(ConfigPusherImpl.java:78) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.controller.netconf.persist.impl.osgi.ConfigPersisterActivator$InnerCustomizer$1.run(ConfigPersisterActivator.java:177) ~<span class="error">&#91;na:na&#93;</span><br/> at java.lang.Thread.run(Thread.java:744) ~<span class="error">&#91;na:1.7.0_55&#93;</span><br/> Caused by: org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl$NotEnoughCapabilitiesException: Not enough capabilities for ConfigSnapshot</p> {configSnapshot='&lt;data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"&gt;&lt;modules xmlns="urn:opendaylight:params:xml:ns:yang:controller:config"&gt;&lt;module&gt;&lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;prefix:sal-netconf-connector&lt;/type&gt;&lt;name&gt;sachi&lt;/name&gt;&lt;address xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;1.1.1.7&lt;/address&gt;&lt;port xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;830&lt;/port&gt;&lt;username xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;tcs&lt;/username&gt;&lt;password xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;tcs@1234&lt;/password&gt;&lt;tcp-only xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;false&lt;/tcp-only&gt;&lt;event-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;&lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:netty"&gt;prefix:netty-event-executor&lt;/type&gt;&lt;name&gt;global-event-executor&lt;/name&gt; &lt;/event-executor&gt;&lt;binding-registry xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;&lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding"&gt;prefix:binding-broker-osgi-registry&lt;/type&gt;&lt;name&gt;binding-osgi-broker&lt;/name&gt; &lt;/binding-registry&gt;&lt;dom-registry xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;&lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:dom"&gt;prefix:dom-broker-osgi-registry&lt;/type&gt;&lt;name&gt;dom-broker&lt;/name&gt; &lt;/dom-registry&gt;&lt;client-dispatcher xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;&lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:config:netconf"&gt;prefix:netconf-client-dispatcher&lt;/type&gt;&lt;name&gt;global-netconf-dispatcher&lt;/name&gt; &lt;/client-dispatcher&gt;&lt;processing-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;&lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:threadpool"&gt;prefix:threadpool&lt;/type&gt;&lt;name&gt;global-netconf-processing-executor&lt;/name&gt; &lt;/processing-executor&gt; &lt;/module&gt; &lt;/modules&gt; &lt;/data&gt; ', capabilities=[http://yang.juniper.net/yang/1.1/jc?module=configuration&amp;revision=1970-01-01, urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf?module=odl-sal-netconf-connector- cfg&amp;revision=2013-10-28]} <p>. Expected but not found: <span class="error">&#91;urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf?module=odl-sal-netconf-connector- cfg&amp;revision=2013-10-28, http://yang.juniper.net/yang/1.1/jc?module=configuration&amp;revision=1970-01-01&#93;</span><br/> at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.getOperationService(ConfigPusherImpl.java:196) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.getOperationServiceWithRetries(ConfigPusherImpl.java:151) ~<span class="error">&#91;na:na&#93;</span><br/> ... 5 common frames omitted</p> <p>and if i add the &lt;yang-module-capabilities&gt;<br/> &lt;capability&gt;<br/> <a href="http://yang.juniper.net/yang/1.1/jc?module=configuration?revision=YYYY-MM-DD" class="external-link" target="_blank" rel="nofollow noopener">http://yang.juniper.net/yang/1.1/jc?module=configuration?revision=YYYY-MM-DD</a><br/> &lt;/capability&gt;<br/> &lt;/yang-module-capabilities&gt; in required capabilities or after the required one's i am getting xml exception.<br/> Kindly guide me how can i move ahead with correct configuration.</p> <p>Thanks in advance.</p> <p>Attachment snapshot.txt has been added with description: netconf-connector snapshot</p> <p>Hi Maros,</p> <p>I have hard coded the capabilities in NetconfClientSession.java file(as mentioned in <a href="https://jira.opendaylight.org/browse/CONTROLLER-256" title="Loading YANG files from local directory when netconf server does not support netconf monitoring" class="issue-link" data-issue-key="CONTROLLER-256"><del>CONTROLLER-256</del></a>) after which we don't need to add yang capabilities in xml explicitly and it skips the above mentioned exception.</p> <p>After doing this also, I am facing the same error of "Sal Initialization Failure"</p> <p>2014-09-02 11:16:36.317 IST <span class="error">&#91;remote-connector-processing-executor-2&#93;</span> WARN o.o.c.s.c.n.NetconfStateSchemas - RemoteDevice</p> {sachi}: Unable to detect available schemas, get to (urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring?revision=2010-10-04)netconf-state/(urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring?revision=2010-10-04)schemas was empty<br/> 2014-09-02 11:16:36.319 IST <span class="error">&#91;remote-connector-processing-executor-3&#93;</span> INFO o.o.c.s.c.netconf.NetconfDevice - schema required resources<br/> 2014-09-02 11:16:36.324 IST <span class="error">&#91;remote-connector-processing-executor-3&#93;</span> ERROR o.o.c.s.c.netconf.NetconfDevice - RemoteDevice{sachi} <p>: Initialization in sal failed, disconnecting from device<br/> java.lang.IllegalStateException: RemoteDevice</p> {sachi}: No more sources for schema context<br/> at org.opendaylight.controller.sal.connect.netconf.NetconfDevice$RecursiveSchemaSetup.setUpSchema(NetconfDevice.java:306) <span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.sal.connect.netconf.NetconfDevice$RecursiveSchemaSetup.run(NetconfDevice.java:295) <span class="error">&#91;bundlefile:na&#93;</span><br/> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) <span class="error">&#91;na:1.7.0_55&#93;</span><br/> at java.util.concurrent.FutureTask.run(FutureTask.java:262) <span class="error">&#91;na:1.7.0_55&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) <span class="error">&#91;na:1.7.0_55&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) <span class="error">&#91;na:1.7.0_55&#93;</span><br/> at java.lang.Thread.run(Thread.java:744) <span class="error">&#91;na:1.7.0_55&#93;</span><br/> 2014-09-02 11:16:36.325 IST <span class="error">&#91;remote-connector-processing-executor-3&#93;</span> WARN o.o.c.s.c.n.l.NetconfDeviceCommunicator - RemoteDevice{sachi} <p>: Session terminated Session closed</p> <p>Ok, so you have file configuration@1970-01-01.yang in cache/schema. Does the file contain revision statement with 1970-01-01 revision ?</p> <p>If so, adding this configuration under your netconf-connector:</p> <p>&lt;yang-module-capabilities&gt;<br/> &lt;capability&gt;<br/> <a href="http://yang.juniper.net/yang/1.1/jc?module=configuration?revision=1970-01-01" class="external-link" target="_blank" rel="nofollow noopener">http://yang.juniper.net/yang/1.1/jc?module=configuration?revision=1970-01-01</a><br/> &lt;/capability&gt;<br/> &lt;/yang-module-capabilities&gt;</p> <p>should do the trick.</p> <p>Also are you running latest controller ?</p> <p>Hi Maros,</p> <p>1. Yes, configuration@1970-01-01.yang in cache/schema contains 1970-01-01 revision statement as below:</p> <p> module configuration {<br/> namespace "http://yang.juniper.net/yang/1.1/jc";<br/> prefix jc;</p> <p> revision 1970-01-01 </p> { description "Initial revision."; } <p>2. Added configuration under your netconf-connector as below:</p> <p>&lt;required-capabilities&gt; &lt;capability&gt;urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf?module=odl-sal-netconf-connector-cfg&amp;revision=2013-10-28&lt;/capability&gt;<br/> &lt;/required-capabilities&gt;<br/> &lt;yang-module-capabilities&gt;<br/> &lt;capability&gt;<br/> <a href="http://yang.juniper.net/yang/1.1/jc?module=configuration&amp;revision=1970-01-01" class="external-link" target="_blank" rel="nofollow noopener">http://yang.juniper.net/yang/1.1/jc?module=configuration&amp;amp;revision=1970-01-01</a><br/> &lt;/capability&gt;<br/> &lt;/yang-module-capabilities&gt;</p> <p>3. Yes, I am running the new controller code cloned on Sept-02.</p> <p>After doing all the changes, its not working.<br/> Please suggest.</p> <p>Thanks in advance<br/> Sachi</p> <p>This xml:</p> <p>&lt;yang-module-capabilities&gt;<br/> &lt;capability&gt;<br/> <a href="http://yang.juniper.net/yang/1.1/jc?module=configuration&amp;revision=1970-01-01" class="external-link" target="_blank" rel="nofollow noopener">http://yang.juniper.net/yang/1.1/jc?module=configuration&amp;amp;revision=1970-01-01</a><br/> &lt;/capability&gt;<br/> &lt;/yang-module-capabilities&gt;</p> <p>Needs to be under module element. It is part of netconf-connector configuration.</p> <p>Hi Maros,</p> <p>Have added the above as part of netconf-connector configuration.</p> <p>Now, I am not getting any error and device is not getting initialized also.</p> <p>Anything else I need to add.</p> <p>Thanks</p> <p>Could you please rerun with detailed logs ?</p> <p>Add these lines to configuration/logback.xml before you start ODL. Delete logs/ folder and rerun:</p> <p> &lt;logger name="org.opendaylight.protocol.framework" level="TRACE"/&gt;<br/> &lt;logger name="org.opendaylight.controller.netconf" level="TRACE"/&gt;<br/> &lt;logger name="org.opendaylight.controller.sal.connect.netconf" level="TRACE"/&gt;<br/> &lt;logger name="org.opendaylight.yangtools.yang.model.repo.util" level="TRACE"/&gt;<br/> &lt;logger name="org.opendaylight.yangtools.yang.parser.repo" level="TRACE"/&gt;</p> <p>And please attach produced opendaylight.log file afterwards. </p> <p>And what do you mean by not getting initialized ? There is nothing under nodes/node from restconf ? or just no data are transfered ?</p> <p>Send the logs on mmarsale@cisco.com.</p> <p>The size of the file was larger so was not able to attach it on bugzilla.</p> <p>The log says "RemoteDevice</p> {controller-config} <p>: Netconf connector initialized successfully" but it does not show any log for my "sachi-m10" netconf connector.</p> Development External issue ID 1601 External issue URL ODL SR Target Milestone Priority Rank 0|i02m4f: