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/OPNFLWJAVA-71 openflowjava <p>When I connect OVS 2.4 to controller, I see too many exceptions filling up several karaf log files. I understand some WARN or ERROR is needed but is it possible to reduce the number? If we cannot easily fix this, we can always release note this issue so users are not alarmed.</p> <p>2016-01-29 18:36:05,600 | WARN | entLoopGroup-5-2 | ListDeserializer | 172 - org.opendaylight.openflowjava.openflow-protocol-impl - 0.7.0.SNAPSHOT | Problem during reading table feature property. Skipping unknown feature property: msgVersion: 4 objectClass: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.oxm.rev150225.match.entries.grouping.MatchEntry msgType: 1 oxm_field: 31 experimenterID: null<br/> java.lang.IllegalStateException: Deserializer for key: msgVersion: 4 objectClass: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.oxm.rev150225.match.entries.grouping.MatchEntry msgType: 1 oxm_field: 31 experimenterID: null was not found - please verify that all needed deserializers ale loaded correctly<br/> at org.opendaylight.openflowjava.protocol.impl.deserialization.DeserializerRegistryImpl.getDeserializer(DeserializerRegistryImpl.java:69)<span class="error">&#91;172:org.opendaylight.openflowjava.openflow-protocol-impl:0.7.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.openflowjava.protocol.impl.util.ListDeserializer.deserializeHeaders(ListDeserializer.java:80)<span class="error">&#91;172:org.opendaylight.openflowjava.openflow-protocol-impl:0.7.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.createTableFeaturesProperties(MultipartReplyMessageFactory.java:444)<span class="error">&#91;172:org.opendaylight.openflowjava.openflow-protocol-impl:0.7.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.setTableFeatures(MultipartReplyMessageFactory.java:379)<span class="error">&#91;172:org.opendaylight.openflowjava.openflow-protocol-impl:0.7.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.deserialize(MultipartReplyMessageFactory.java:232)<span class="error">&#91;172:org.opendaylight.openflowjava.openflow-protocol-impl:0.7.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.deserialize(MultipartReplyMessageFactory.java:149)<span class="error">&#91;172:org.opendaylight.openflowjava.openflow-protocol-impl:0.7.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.openflowjava.protocol.impl.deserialization.DeserializationFactory.deserialize(DeserializationFactory.java:59)<span class="error">&#91;172:org.opendaylight.openflowjava.openflow-protocol-impl:0.7.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.openflowjava.protocol.impl.core.OFDecoder.decode(OFDecoder.java:55)<span class="error">&#91;172:org.opendaylight.openflowjava.openflow-protocol-impl:0.7.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.openflowjava.protocol.impl.core.OFDecoder.decode(OFDecoder.java:28)<span class="error">&#91;172:org.opendaylight.openflowjava.openflow-protocol-impl:0.7.0.SNAPSHOT&#93;</span><br/> at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:89)<span class="error">&#91;125:io.netty.codec:4.0.33.Final&#93;</span><br/> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:276)<span class="error">&#91;125:io.netty.codec:4.0.33.Final&#93;</span><br/> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:263)<span class="error">&#91;125:io.netty.codec:4.0.33.Final&#93;</span><br/> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:276)<span class="error">&#91;125:io.netty.codec:4.0.33.Final&#93;</span><br/> at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:354)<span class="error">&#91;125:io.netty.codec:4.0.33.Final&#93;</span><br/> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:244)<span class="error">&#91;125:io.netty.codec:4.0.33.Final&#93;</span><br/> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.handler.timeout.ReadTimeoutHandler.channelRead(ReadTimeoutHandler.java:152)<span class="error">&#91;127:io.netty.handler:4.0.33.Final&#93;</span><br/> at org.opendaylight.openflowjava.protocol.impl.core.IdleHandler.channelRead(IdleHandler.java:39)<span class="error">&#91;172:org.opendaylight.openflowjava.openflow-protocol-impl:0.7.0.SNAPSHOT&#93;</span><br/> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:349)<span class="error">&#91;124:io.netty.transport:4.0.33.Final&#93;</span><br/> at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)<span class="error">&#91;123:io.netty.common:4.0.33.Final&#93;</span><br/> at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)<span class="error">&#91;123:io.netty.common:4.0.33.Final&#93;</span><br/> at java.lang.Thread.run(Thread.java:745)<span class="error">&#91;:1.7.0_79&#93;</span></p> <p>Operating System: All<br/> Platform: All</p> OPNFLWJAVA-71

Karaf log many WARNs when OVS 2.4 connects to controller

Bug Highest Resolved Done Luis Gomez Luis Gomez Mon, 1 Feb 2016 18:03:53 +0000 Thu, 3 May 2018 16:50:03 +0000 Thu, 3 May 2018 16:50:03 +0000 unspecified General 0 6 <p>This bug is directly related to the one I have reported: Bug ID: 5181. In fact, if the library "Nicira Extension" is installated, then the bug is the one I have reported. However, if you decide to remote such library to fix the "ClassCastExpection then the problem is exactly the one reported herein.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/33881/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/33881/</a></p> <p>The change was merged - WARN message will be logged for EACH multipart reply (table features) - This should only provide hint with exception message. If details are desired, one has to set openflowjava logging to DEBUG and he will see complete exception.</p> <p>Log frequency can't be adjusted beyond this point.</p> <p>Now I "only" get 1524 log entries like this:</p> <p>2016-02-03 18:34:29,604 | WARN | entLoopGroup-5-2 | ListDeserializer | 172 - org.opendaylight.openflowjava.openflow-protocol-impl - 0.7.0.SNAPSHOT | Problem during reading table feature property. Skipping unknown feature property: msgVersion: 4 objectClass: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.oxm.rev150225.match.entries.grouping.MatchEntry msgType: 1 oxm_field: 31 experimenterID: null.If more information is needed, set org.opendaylight.openflowjava do DEBUG log level.</p> <p>And they all fit in a single kara.log file.</p> <p>If this is all we can do for now we can close this bug.</p> <p>BR/Luis</p> <p>According to Jamo, OPNFV is testing with latest Be and they also find annoying and difficult to debug the controller with so many logs. Really is it not possible to move all these messages to DEBUG level until we do proper implementation in openflowplugin?</p> <p>Setting openflowjava log level to WARN should be enough, shouldn't it ?</p> <p>*specially org.opendaylight.openflowjava.protocol.impl.util</p> <ul> <li> <ul> <li>to ERROR</li> </ul> </li> </ul> <p>see thread here:</p> <p><a href="https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-August/005831.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-August/005831.html</a></p> <p>also making it critical as I think it makes the user experience pretty poor<br/> when trying to debug other issues in the log.</p> <p>(In reply to Jamo Luhrsen from comment #8)<br/> &gt; see thread here:<br/> &gt; <br/> &gt; <a href="https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-August/" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-August/</a><br/> &gt; 005831.html<br/> &gt; <br/> &gt; also making it critical as I think it makes the user experience pretty poor<br/> &gt; when trying to debug other issues in the log.</p> <p>I'm planning to now move our CSIT jobs to set logging levels to ERROR<br/> in order to not see this, but it's still there and really makes a<br/> lot of useless noise when trying to debug other failures.</p> <p>I have not seen this issue in Boron/Carbon but it is probably in Beryllium.</p> <p>(In reply to Luis Gomez from comment #11)<br/> &gt; I have not seen this issue in Boron/Carbon but it is probably in Beryllium.</p> <p><a href="https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-learn-carbon/138/archives/odl1_karaf.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-learn-carbon/138/archives/odl1_karaf.log.gz</a></p> <p>I do not see this issue in the log you post, it is similar but not the same, just search for "Problem during reading table feature property" that was the issue we had before and now I believe it is fixed. I would probably open a bug for the new issue as it could be just some flow not properly interpreted by ofplugin/ofjava.</p> <p>Since the bug is unassigned I'm currently assigning it to you.</p> <p>Please assign to the relevant person. </p> <p>This is old stuff, closing.</p> Duplicate OPNFLWPLUG-564 Development External issue ID 5173 External issue URL Rank 0|i02g4v: