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/SNMP4SDN-14 snmp4sdn <p>Following ERROR is seeing when bringing snmp4sdn feature:</p> <p>2016-02-02 04:21:52,476 | ERROR | Event Dispatcher | CmethUtil | 466 - org.opendaylight.snmp4sdn - 0.3.0.SNAPSHOT | CmethUtil.readDB() err: {}<br/> java.io.FileNotFoundException: /etc/snmp4sdn_swdb.csv (No such file or directory)<br/> at java.io.FileInputStream.open0(Native Method)<span class="error">&#91;:1.8.0_65&#93;</span><br/> at java.io.FileInputStream.open(FileInputStream.java:195)<span class="error">&#91;:1.8.0_65&#93;</span><br/> at java.io.FileInputStream.&lt;init&gt;(FileInputStream.java:138)<span class="error">&#91;:1.8.0_65&#93;</span><br/> at java.io.FileInputStream.&lt;init&gt;(FileInputStream.java:93)<span class="error">&#91;:1.8.0_65&#93;</span><br/> at java.io.FileReader.&lt;init&gt;(FileReader.java:58)<span class="error">&#91;:1.8.0_65&#93;</span><br/> at org.opendaylight.snmp4sdn.internal.util.CmethUtil.readDB(CmethUtil.java:66)<br/> at org.opendaylight.snmp4sdn.internal.util.CmethUtil.&lt;init&gt;(CmethUtil.java:43)<br/> at org.opendaylight.snmp4sdn.core.internal.Controller.init(Controller.java:156)<br/> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<span class="error">&#91;:1.8.0_65&#93;</span><br/> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)<span class="error">&#91;:1.8.0_65&#93;</span><br/> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)<span class="error">&#91;:1.8.0_65&#93;</span><br/> at java.lang.reflect.Method.invoke(Method.java:497)<span class="error">&#91;:1.8.0_65&#93;</span><br/> at org.apache.felix.dm.InvocationUtil.invokeMethod(InvocationUtil.java:111)<span class="error">&#91;220:org.apache.felix.dependencymanager:3.1.0&#93;</span><br/> at org.apache.felix.dm.InvocationUtil.invokeCallbackMethod(InvocationUtil.java:66)<span class="error">&#91;220:org.apache.felix.dependencymanager:3.1.0&#93;</span><br/> at org.apache.felix.dm.impl.ComponentImpl.invokeCallbackMethod(ComponentImpl.java:688)<span class="error">&#91;220:org.apache.felix.dependencymanager:3.1.0&#93;</span><br/> at org.apache.felix.dm.impl.ComponentImpl.invoke(ComponentImpl.java:679)<span class="error">&#91;220:org.apache.felix.dependencymanager:3.1.0&#93;</span><br/> at org.apache.felix.dm.impl.ComponentImpl.activateService(ComponentImpl.java:608)<span class="error">&#91;220:org.apache.felix.dependencymanager:3.1.0&#93;</span><br/> at org.apache.felix.dm.impl.ComponentImpl.access$000(ComponentImpl.java:52)<span class="error">&#91;220:org.apache.felix.dependencymanager:3.1.0&#93;</span><br/> at org.apache.felix.dm.impl.ComponentImpl$1.run(ComponentImpl.java:144)<span class="error">&#91;220:org.apache.felix.dependencymanager:3.1.0&#93;</span><br/> at org.apache.felix.dm.impl.SerialExecutor$1.run(SerialExecutor.java:47)<span class="error">&#91;220:org.apache.felix.dependencymanager:3.1.0&#93;</span><br/> at org.apache.felix.dm.impl.SerialExecutor.scheduleNext(SerialExecutor.java:84)<span class="error">&#91;220:org.apache.felix.dependencymanager:3.1.0&#93;</span><br/> at org.apache.felix.dm.impl.SerialExecutor.execute(SerialExecutor.java:68)<span class="error">&#91;220:org.apache.felix.dependencymanager:3.1.0&#93;</span><br/> at org.apache.felix.dm.impl.ComponentImpl.calculateStateChanges(ComponentImpl.java:231)<span class="error">&#91;220:org.apache.felix.dependencymanager:3.1.0&#93;</span><br/> at org.apache.felix.dm.impl.ComponentImpl.start(ComponentImpl.java:399)<span class="error">&#91;220:org.apache.felix.dependencymanager:3.1.0&#93;</span><br/> at org.apache.felix.dm.DependencyManager.add(DependencyManager.java:169)<br/> at org.opendaylight.controller.sal.core.ComponentActivatorAbstractBase.start(ComponentActivatorAbstractBase.java:346)<br/> at org.opendaylight.snmp4sdn.internal.Activator.start(Activator.java:138)<br/> at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)<br/> at java.security.AccessController.doPrivileged(Native Method)<span class="error">&#91;:1.8.0_65&#93;</span><br/> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)<span class="error">&#91;org.eclipse.osgi-3.8.2.v20130124-134944.jar:&#93;</span><br/> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)<span class="error">&#91;org.eclipse.osgi-3.8.2.v20130124-134944.jar:&#93;</span><br/> at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)<span class="error">&#91;org.eclipse.osgi-3.8.2.v20130124-134944.jar:&#93;</span><br/> at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)<span class="error">&#91;org.eclipse.osgi-3.8.2.v20130124-134944.jar:&#93;</span><br/> at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)<span class="error">&#91;org.eclipse.osgi-3.8.2.v20130124-134944.jar:&#93;</span><br/> at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)<span class="error">&#91;org.eclipse.osgi-3.8.2.v20130124-134944.jar:&#93;</span><br/> at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)<span class="error">&#91;org.eclipse.osgi-3.8.2.v20130124-134944.jar:&#93;</span><br/> at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)<span class="error">&#91;org.eclipse.osgi-3.8.2.v20130124-134944.jar:&#93;</span><br/> at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)<span class="error">&#91;org.eclipse.osgi-3.8.2.v20130124-134944.jar:&#93;</span><br/> at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)<span class="error">&#91;org.eclipse.osgi-3.8.2.v20130124-134944.jar:&#93;</span><br/> at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)<span class="error">&#91;org.eclipse.osgi-3.8.2.v20130124-134944.jar:&#93;</span><br/> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)<span class="error">&#91;org.eclipse.osgi-3.8.2.v20130124-134944.jar:&#93;</span><br/> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)<span class="error">&#91;org.eclipse.osgi-3.8.2.v20130124-134944.jar:&#93;</span></p> <p>Operating System: All<br/> Platform: All</p> SNMP4SDN-14

ERROR message in distribution sanity check

Bug Resolved Done Unassigned Luis Gomez Tue, 2 Feb 2016 23:08:32 +0000 Thu, 19 Oct 2017 22:33:52 +0000 Mon, 15 Feb 2016 18:24:55 +0000 unspecified General 0 4 <p>This bug is fine. snmp4sdn plugin tries to read a file during start, for user's convenience. The read file failure won't harm snmp4sdn plugin nor whole system. Actually it is the switch list file, which is necessary for topology discovery for snmp4sdn plugin. snmp4sdn plugin provides command for user to manually assign the file path and trigger topology discovery.</p> <p>&gt; The read file failure won't harm snmp4sdn plugin nor whole system.</p> <p>Then it should not be logged as ERROR.<br/> INFO about default config file not found (if it is really optional), or WARN if users should create such file.</p> <p>Right, I reopened this to see if snmp4sdn can change the log severity to WARN or INFO as future sanity checks will block everything in case of karaf ERROR.</p> <p>Luis, do you think the bug should be marked as "major" since Yi-Ling Hsieh mentions this bug is fine.</p> <p>Sure, I just did.</p> <p>Thanks Luis, I modified the error as INFO level, merged as <a href="https://git.opendaylight.org/gerrit/#/c/34052/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/34052/</a></p> <p>In my opinion, having full traces in the logs is very alarming and we should<br/> avoid those if possible. I usually assume the software has encountered<br/> something unexpected or is broken. In this case, we know that there are<br/> times when the file might not be there. If that's reasonable, then can<br/> we do something like this instead:</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/34364" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/34364</a></p> <p>I'm not a java person, but it allows for the generic exception to still<br/> be caught, but also the specific FileNotFound exception to be there in<br/> a more tame fasion. Looks like this now:</p> <p>016-02-09 21:56:06,489 | INFO | l for user karaf | CmethUtil | 242 - org.opendaylight.snmp4sdn - 0.3.0.SNAPSHOT | enter CmethUtil.readDB()<br/> 2016-02-09 21:56:06,489 | INFO | l for user karaf | CmethUtil | 242 - org.opendaylight.snmp4sdn - 0.3.0.SNAPSHOT | open file /etc/snmp4sdn_swdb.csv<br/> 2016-02-09 21:56:06,489 | INFO | l for user karaf | CmethUtil | 242 - org.opendaylight.snmp4sdn - 0.3.0.SNAPSHOT | CmethUtil.readDB() fail: /etc/snmp4<br/> sdn_swdb.csv (No such file or directory)<br/> 2016-02-09 21:56:06,490 | INFO | l for user karaf | Controller | 242 - org.opendaylight.snmp4sdn - 0.3.0.SNAPSHOT | snmp4sdn's Controller: Starting!</p> <p>I moved this back to an open state, just to continue the conversation, if<br/> that's ok.</p> <p>There is another exception coming from snmp4sdn:</p> <p>2016-02-09 22:04:41,723 | WARN | l for user karaf | SNMPListener | 242 - org.opendaylight.snmp4sdn - 0.3.0.SNAPSHOT | Problem starting SNMP Trap Interfac<br/> e: {}<br/> java.net.BindException: Permission denied<br/> at java.net.PlainDatagramSocketImpl.bind0(Native Method)<span class="error">&#91;:1.7.0_95&#93;</span><br/> at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:96)<span class="error">&#91;:1.7.0_95&#93;</span><br/> at java.net.DatagramSocket.bind(DatagramSocket.java:397)<span class="error">&#91;:1.7.0_95&#93;</span><br/> at java.net.DatagramSocket.&lt;init&gt;(DatagramSocket.java:251)<span class="error">&#91;:1.7.0_95&#93;</span><br/> &lt;snip&gt;</p> <p>this is also alarming, but I'm not sure the right thing to do. The reason for<br/> the exception is that we are trying to bind on the well known SNMP trap port of <br/> 162. But, that's a privileged port ( &lt; 1024) so only root user can do so.</p> <p>our jenkins jobs are using a non-root user, I guess, so we see this is CSIT<br/> every time. But, if we run karaf as root user (I tried) the port is successfully<br/> bound to and no exceptions.</p> <p>Not sure the right thing, or if anything, to do on this one.</p> <p>For the warn alarm above, pointed by Jamo Luhrsen</p> <p>2016-02-09 22:04:41,723 | WARN | l for user karaf | SNMPListener | 242 - org.opendaylight.snmp4sdn - 0.3.0.SNAPSHOT | Problem starting SNMP Trap Interfac<br/> e: {}<br/> java.net.BindException: Permission denied<br/> ...</p> <p>It's due to snmp4sdn plugin needs to listen to the SNMP port for SNMP traps (in order to detect link-down/up events if receiving SNMP trap sent from an Ethernet switch).</p> <p>So user needs to launch Karaf with sufficient OS privilege, such as an administrator.</p> <p>So, I have two patches for you:</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/34364/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/34364/</a><br/> <a href="https://git.opendaylight.org/gerrit/#/c/34588/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/34588/</a></p> <p>Since I think you would agree that these Exceptions are coming from<br/> reasonable situations that we can know about, I think we should <br/> not spit out the Entire trace. I do think those come across as<br/> extra alarming and these are not cases for that. The above two<br/> patches would instead give log messages like this:</p> <p>2016-02-12 20:10:20,732 | INFO | l for user karaf | CmethUtil | 242 - org.opendaylight.snmp4sdn - 0.3.0.SNAPSHOT | CmethUtil.readDB() fail: /etc/snmp4sdn_swdb.csv (No such file or director<br/> y)<br/> 2016-02-12 20:10:20,733 | INFO | l for user karaf | Controller | 242 - org.opendaylight.snmp4sdn - 0.3.0.SNAPSHOT | snmp4sdn's Controller: Starting!<br/> 2016-02-12 20:10:20,740 | WARN | l for user karaf | SNMPListener | 242 - org.opendaylight.snmp4sdn - 0.3.0.SNAPSHOT | Unable to Bind to SNMP Trap Port: Permission denied </p> <p>I can modify the patches somehow if you feel neccessary.</p> <p>Thanks.</p> <p>Thanks for the patches, introduced into snmp4sdn repo.</p> <p>Fixed, close this bug.</p> <p>Severity: Not a blocker. We can release Beryllium without it.<br/> Testing: Improved log messages instead of spitting out the entire trace. Extensive testing not necessary as the fix has very small footprint. This is not covered by any unit tests or system tests.<br/> Impact: No impact to dependent projects.</p> Development External issue ID 5194 External issue URL Rank 0|i02v9r: