Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1649510

Summary:	[Logs] ODL info logs being spammed with org.opendaylight.openflowplugin.impl - 0.6.4.redhat-4 \| ConnectionEvent: Connection closed by device, Device:/127.0.0.1:38632, NodeId:null
Product:	Red Hat OpenStack	Reporter:	Sai Sindhur Malleni <smalleni>
Component:	opendaylight	Assignee:	lpeer <lpeer>
Status:	CLOSED WONTFIX	QA Contact:	Noam Manos <nmanos>
Severity:	low	Docs Contact:
Priority:	low
Version:	13.0 (Queens)	CC:	mkolesni, vorburger, vpickard
Target Milestone:	z6	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Logs
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-06 16:16:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sai Sindhur Malleni 2018-11-13 18:36:02 UTC

Description of problem:
On looking at ODL logs from an active TripleO deployment we see 1000s of messages such as 2018-11-13T18:23:12,192 | INFO  | nioEventLoopGroup-9-90 | SystemNotificationsListenerImpl  | 374 - org.opendaylight.openflowplugin.impl - 0.6.4.redhat-4 | ConnectionEvent: Connection closed by device, Device:/127.0.0.1:38632, NodeId:null

at a very high frequency, pretty much spamming logs.

Version-Release number of selected component (if applicable):
OSP13

How reproducible:
100%

Steps to Reproduce:
1. Deploy ODL with OSP
2. Observe karaf logs
3.

Actual results:
Log file gets spammed with these Connection closed by device messages

Expected results:
Even at INFO level, there shouldn't be so much traffic in logs. If the message itself is legit, it should at least be iDEBUG level.

Additional info:

Comment 1 Mike Kolesnik 2018-11-15 13:38:07 UTC

Seems like it should be a quick fix, let's see if we have time to tackle this.

Comment 3 Michael Vorburger 2018-11-22 11:22:53 UTC

If the upstream issue does not get resolved, a completely different approach than silencing that log at source (code) would be to attempt to play with logging configuration - the maxBurst filter on https://logging.apache.org/log4j/2.0/manual/filters.html seems useful for a problem such as this...

Comment 4 Michael Vorburger 2018-11-26 10:26:07 UTC

Upstream change to silence log got accepted, master merged, Oxygen pending...

Comment 6 Franck Baudin 2019-03-06 16:16:00 UTC

As per depreciation notice [1], closing this bug. Please reopen if relevant for RHOSP13, as this is the only version shipping ODL.

[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/14/html-single/release_notes/index#deprecated_functionality

Comment 7 Franck Baudin 2019-03-06 16:17:33 UTC

As per depreciation notice [1], closing this bug. Please reopen if relevant for RHOSP13, as this is the only version shipping ODL.

[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/14/html-single/release_notes/index#deprecated_functionality