Hello,

Thanks for testing this, I really appreciate it.

On Feb 7, 2014, at 6:36 AM, jcat <j...@nysasounds.co.uk> wrote:

It looks like the combination that is causing this error is for snmp
interfaces that match the following:

snmpifdescr='' and snmpifname is null

If I delete those from the test DB I've got running, the error goes away :)

I guess in a ideal world the parser would simply "pass" or "skip on
combination like this.  Is that possible?

Of course!

This is classy - check out what the filename for such a directory actually
is:


nodeid |      foreignsource      |         foreignid         | snmpifdescr
| snmpifname | snmpphysaddr 
--------+-------------------------+---------------------------+-------------+------------+--------------
   329 | dd_infrastructure_power | oobman-peddup06.ocado.com |            
|            | 00029906ced7


share/rrd/snmp/329# ls -la |grep 00029906ced7
drwxrwxr-x    2 root root   4096 Jan 29 15:11 null-00029906ced7

Ahhhh!

Well, guess I need to consider this possible use case ;)

I'm attaching an updated patch!

Alejandro.

Attachment: validate-interface-data.diff
Description: Binary data

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-devel mailing list

To *unsubscribe* or change your subscription options, see the bottom of this 
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel

Reply via email to