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/OPNFLWPLUG-283 OpenFlowPlugin <p>The following logs are being logged despite the log level is set to ERROR:</p> <p>2014-09-17 20:40:11,930 | INFO | qtp103994434-447 | BrokerFacade | 167 - org.opendaylight.controller.sal-rest-connector - 1.1.0.SNAPSHOT | Delete CONFIGURATION via Restconf: /(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[</p> {(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:7} <p>]/AugmentationIdentifier</p> {childNames=[(urn:opendaylight:flow:inventory?revision=2013-08-19)manufacturer, (urn:opendaylight:flow:inventory?revision=2013-08-19)hardware, (urn:opendaylight:flow:inventory?revision=2013-08-19)software, (urn:opendaylight:flow:inventory?revision=2013-08-19)serial-number, (urn:opendaylight:flow:inventory?revision=2013-08-19)description, (urn:opendaylight:flow:inventory?revision=2013-08-19)meter, (urn:opendaylight:flow:inventory?revision=2013-08-19)table, (urn:opendaylight:flow:inventory?revision=2013-08-19)group, (urn:opendaylight:flow:inventory?revision=2013-08-19)ip-address, (urn:opendaylight:flow:inventory?revision=2013-08-19)supported-match-types, (urn:opendaylight:flow:inventory?revision=2013-08-19)supported-instructions, (urn:opendaylight:flow:inventory?revision=2013-08-19)supported-actions, (urn:opendaylight:flow:inventory?revision=2013-08-19)switch-features]} <p>/(urn:opendaylight:flow:inventory?revision=2013-08-19)table/table[</p> {(urn:opendaylight:flow:inventory?revision=2013-08-19)id=0} <p>]/flow/flow[</p> {(urn:opendaylight:flow:inventory?revision=2013-08-19)id=309999} <p>]</p> <p>According to the log's header (and logic), this log should only appear if the log level is info.</p> <p>To reproduce, set all log levels in logback.xml to ERROR, start teh controller and run the attached performance python script with the following command line:</p> <p>&gt;python flow_config_perf.py --nflows 1000 --nthreads=10</p> <p>mininet was not connected. This bug is affecting performance.</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-283

Logging flow deletions despite log level set to ERROR

Bug Resolved Won't Do Jan Hajnar Jan Medved Thu, 18 Sep 2014 03:50:42 +0000 Mon, 27 Sep 2021 09:01:20 +0000 Thu, 23 Oct 2014 10:10:44 +0000 General 0 6 <p>Attachment flow_config_perf.py has been added with description: Flow config script</p> <p>How did you modified logging configuration? There are several bug reports<br/> pointing out that Karaf logging configuration does not work.</p> <p>To my knowledge, karaf does not load log config from logback.xml. </p> <p>It uses Pax Logging service and config file is located in etc/org.ops4j.pax.logging.cfg</p> <p>To change to error level globaly you should change line with "log4j.rootLogger=INFO, out, osgi:<b>" to "log4j.rootLogger=ERROR, out, osgi:</b>"</p> <p>Also you can change level for individual loggers like: <br/> log4j.logger.&lt;package&gt;=&lt;DEBUG_LEVEL&gt; i.e. log4j.logger.org.opendaylight=INFO</p> <p>maybe we could recreate setup from logback.xml in Pax Logging config file.</p> <p>also logging levels and loggers can be edited through karaf command line wit log:set command:<br/> <a href="http://karaf.apache.org/manual/latest-2.2.x/users-guide/logging-system.html" class="external-link" target="_blank" rel="nofollow noopener">http://karaf.apache.org/manual/latest-2.2.x/users-guide/logging-system.html</a></p> <p><a href="http://karaf.apache.org/manual/latest-2.2.x/users-guide/logging-system.html" class="external-link" target="_blank" rel="nofollow noopener">http://karaf.apache.org/manual/latest-2.2.x/users-guide/logging-system.html</a></p> <p>Note the correct place for any changes to logging defaults would be here:</p> <p>controller/opendaylight/distribution/opendaylight-karaf-resources/src/main/resources</p> Development External issue ID 1945 External issue URL Rank 0|i03073: