This looks Beryllium SR 3. Are these warnings/errors also when connecting to OVS 2.4? I would think so given the second message. The first one I believe Anil may have a better idea (Helium design stats mgr). The second one is because in Beryllium - we were not processing the table features property & hence issuing a warning that we were skipping - so can be considered as a legitimate warning. Earlier before adding the skipping warning the connection to OVS 2.4 itself used to fail.
On Fri, Aug 19, 2016 at 9:36 AM, Jamo Luhrsen <jluhr...@gmail.com> wrote: > > > On 08/19/2016 09:30 AM, Robert Varga wrote: > >> On 08/19/2016 06:16 PM, Ryan Dietrich wrote: >> >>> >>> 2016-08-19 09:58:52,959 | WARN | entLoopGroup-7-1 | >>> StatisticsManagerImpl | 183 - >>> org.opendaylight.openflowplugin.impl - 0.2.2.Beryllium-SR2 | Statistics >>> gathering for single node was not successful: Previous transaction >>> member-1-chn-3-txn-789-1471296067057 is not ready yet >>> 2016-08-19 09:58:55,969 | WARN | entLoopGroup-7-1 | >>> StatisticsGatheringUtils | 183 - >>> org.opendaylight.openflowplugin.impl - 0.2.2.Beryllium-SR2 | stats >>> processing of type OFPMPTABLE for node Uri >>> [_value=openflow:10195228916973568] failed during write-to-tx step >>> java.lang.IllegalStateException: Previous transaction >>> member-1-chn-3-txn-789-1471296067057 is not ready yet >>> at >>> org.opendaylight.controller.cluster.datastore.TransactionCha >>> inProxy$Allocated.checkReady(TransactionChainProxy.java:85)[ >>> 165:org.opendaylight.controller.sal-distributed-datastore:1. >>> 3.2.Beryllium-SR2] >>> >>> >> Looks like a synchronization problem in OFP, +openflowplugin-dev >> >> Bye, >> Robert >> >> This error is showing up all over the place in my logs (SR2) >>> >>> Also, this warning is repeated thousands of times. >>> >>> 2016-08-19 09:57:12,690 | WARN | entLoopGroup-7-1 | ListDeserializer >>> | 179 - >>> org.opendaylight.openflowjava.openflow-protocol-impl - >>> 0.7.2.Beryllium-SR2 | Problem during reading table feature property. >>> Skipping unknown feature property: msgVersion: 4 objectClass: >>> org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.oxm.r >>> ev150225.match.entries.grouping.MatchEntry >>> msgType: 1 oxm_field: 31 experimenterID: null.If more information is >>> needed, set org.opendaylight.openflowjava do DEBUG log level. >>> >>> Are these fixed in SR3? Are they issues I need to deal with? >>> >> > no, not fixed anywhere yet, but I think it's coming to Boron soon. see > this thread > > https://lists.opendaylight.org/pipermail/openflowplugin-dev/ > 2016-August/005831.html > > > JamO > > > > >>> _______________________________________________ >>> controller-dev mailing list >>> controller-dev@lists.opendaylight.org >>> https://lists.opendaylight.org/mailman/listinfo/controller-dev >>> >>> >> >> >> _______________________________________________ >> controller-dev mailing list >> controller-dev@lists.opendaylight.org >> https://lists.opendaylight.org/mailman/listinfo/controller-dev >> >> _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/controller-dev >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
