<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[MIB Parser Error]]></title><description><![CDATA[<p dir="auto">I'm getting the following error when trying to compile new MIB files:</p>
<pre><code>CISCO-UNIFIED-COMPUTING-TC-MIB.txt: ERROR 003: Parser error - memory exhausted in line 15951
</code></pre>
<p dir="auto">I could try to remove the MIB, but other MIBs depend on this one.</p>
<p dir="auto">I got this particular MIB directly from Cisco, so I don't think it's bad but I could be wrong.</p>
]]></description><link>https://forum.netxms.org/topic/5725/mib-parser-error</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 12:31:08 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/5725.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 01 Nov 2018 18:02:40 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to MIB Parser Error on Tue, 20 Nov 2018 23:30:02 GMT]]></title><description><![CDATA[<p dir="auto">If there's one thing I've learned from using NetXMS and it's strict MIB parser is that most vendors MIBs don't follow best practices and also come prebundled with out of date IEEE and other common MIBs.</p>
]]></description><link>https://forum.netxms.org/post/25047</link><guid isPermaLink="true">https://forum.netxms.org/post/25047</guid><dc:creator><![CDATA[Staj]]></dc:creator><pubDate>Tue, 20 Nov 2018 23:30:02 GMT</pubDate></item><item><title><![CDATA[Reply to MIB Parser Error on Wed, 07 Nov 2018 11:11:22 GMT]]></title><description><![CDATA[<p dir="auto">That particular MIB appears to have a history of issues:<br />
2013: <a href="https://community.cisco.com/t5/unified-computing-system/cisco-unified-computing-tc-mib-won-t-compile/td-p/2096749" rel="nofollow ugc">https://community.cisco.com/t5/unified-computing-system/cisco-unified-computing-tc-mib-won-t-compile/td-p/2096749</a><br />
2015: <a href="https://kb.vmware.com/s/article/2034241" rel="nofollow ugc">https://kb.vmware.com/s/article/2034241</a></p>
<p dir="auto">Having said that, I downloaded the MIB from <a href="http://www.circitor.fr/Mibs/Mib/C/CISCO-UNIFIED-COMPUTING-TC-MIB.mib" rel="nofollow ugc">http://www.circitor.fr/Mibs/Mib/C/CISCO-UNIFIED-COMPUTING-TC-MIB.mib</a> and it compiled fine at our end.<br />
But then the memory exhausted part would indicate your system somehow running out of memory while trying to build all your MIBs?<br />
I did a quick check at our end and compiling our pile of MIBs (~ 56MB worth) seems to take up half a gig of RAM while doing so.<br />
I wouldn't think that should be a problem on a server, but then I don't know how many MIBs (and available RAM) you have.</p>
<p dir="auto">Maybe you can download your MIB collection to Google Drive or similar for Victor to download?</p>
]]></description><link>https://forum.netxms.org/post/24976</link><guid isPermaLink="true">https://forum.netxms.org/post/24976</guid><dc:creator><![CDATA[Tursiops]]></dc:creator><pubDate>Wed, 07 Nov 2018 11:11:22 GMT</pubDate></item><item><title><![CDATA[Reply to MIB Parser Error on Fri, 02 Nov 2018 13:33:15 GMT]]></title><description><![CDATA[<p dir="auto">I tried to attach it, but I get an error of "413 Request Entity Too Large" when I hit Post.</p>
]]></description><link>https://forum.netxms.org/post/24966</link><guid isPermaLink="true">https://forum.netxms.org/post/24966</guid><dc:creator><![CDATA[coffey64]]></dc:creator><pubDate>Fri, 02 Nov 2018 13:33:15 GMT</pubDate></item><item><title><![CDATA[Reply to MIB Parser Error on Fri, 02 Nov 2018 09:15:09 GMT]]></title><description><![CDATA[<p dir="auto">Could you provide archive with all your MIB files so we can test them?</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/24965</link><guid isPermaLink="true">https://forum.netxms.org/post/24965</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Fri, 02 Nov 2018 09:15:09 GMT</pubDate></item></channel></rss>