[OPNFLWJAVA-71] Karaf log many WARNs when OVS 2.4 connects to controller Created: 01/Feb/16 Updated: 03/May/18 Resolved: 03/May/18 |
|
| Status: | Resolved |
| Project: | openflowjava |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Highest |
| Reporter: | Luis Gomez | Assignee: | Luis Gomez |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 5173 | ||||||||
| Description |
|
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. 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 |
| Comments |
| Comment by Jose M. Alcaraz Calero [ 02/Feb/16 ] |
|
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. |
| Comment by Michal Polkorab [ 02/Feb/16 ] |
| Comment by Michal Polkorab [ 03/Feb/16 ] |
|
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. Log frequency can't be adjusted beyond this point. |
| Comment by Luis Gomez [ 04/Feb/16 ] |
|
Now I "only" get 1524 log entries like this: 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. And they all fit in a single kara.log file. If this is all we can do for now we can close this bug. BR/Luis |
| Comment by Luis Gomez [ 09/Feb/16 ] |
|
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? |
| Comment by Michal Polkorab [ 09/Feb/16 ] |
|
Setting openflowjava log level to WARN should be enough, shouldn't it ? |
| Comment by Michal Polkorab [ 09/Feb/16 ] |
|
*specially org.opendaylight.openflowjava.protocol.impl.util
|
| Comment by Jamo Luhrsen [ 19/Aug/16 ] |
|
see thread here: https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-August/005831.html also making it critical as I think it makes the user experience pretty poor |
| Comment by Jamo Luhrsen [ 01/Mar/17 ] |
|
(In reply to Jamo Luhrsen from comment #8) I'm planning to now move our CSIT jobs to set logging levels to ERROR |
| Comment by Luis Gomez [ 01/Mar/17 ] |
|
I have not seen this issue in Boron/Carbon but it is probably in Beryllium. |
| Comment by Jamo Luhrsen [ 01/Mar/17 ] |
|
(In reply to Luis Gomez from comment #11) |
| Comment by Luis Gomez [ 01/Mar/17 ] |
|
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. |
| Comment by OpenDaylight Release [ 03/May/18 ] |
|
Since the bug is unassigned I'm currently assigning it to you. Please assign to the relevant person. |
| Comment by Luis Gomez [ 03/May/18 ] |
|
This is old stuff, closing. |