<?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[Server Initialization Errors - Mib and Configuration]]></title><description><![CDATA[<p dir="auto">Server Initialization Errors</p>
<p dir="auto">I'm encountering some errors during initialization. In principle, they don't prevent the system from functioning.</p>
<pre><code>[snmp.mib] Failed to load MIB tree from /var/lib/netxms/netxms.cmib: Invalid or corrupted file data
</code></pre>
<p dir="auto">The MIB compiles successfully on the frontend, but the MIB Explorer doesn't work. This message appears in the server logs during the MIB file compilation.</p>
<p dir="auto">The second error is this:</p>
<pre><code>[config] Configuration loading error: XML parser error in file ":memory:" at line 1 (no element found)
</code></pre>
<p dir="auto">I can't identify the cause of this message, but it appears constantly.</p>
<p dir="auto">Could someone offer some guidance on how to fix this?</p>
]]></description><link>https://forum.netxms.org/topic/8400/server-initialization-errors-mib-and-configuration</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 09:38:37 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/8400.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 05 Jun 2026 00:04:47 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Server Initialization Errors - Mib and Configuration on Thu, 25 Jun 2026 10:47:31 GMT]]></title><description><![CDATA[<p dir="auto">For XML error - I don't see it in current development version log, so changes are that it's already fixed, pls double-check when v.6.2 is out.</p>
<p dir="auto">For MIB error - I guess MIB compiler is failing on some specific MIB file. You can try removing some of your MIB files until you find which one is causing the issue (you can remove half of them, recomplie, then another half, etc...). Or you can just share your whole MIB file collection.</p>
]]></description><link>https://forum.netxms.org/post/35561</link><guid isPermaLink="true">https://forum.netxms.org/post/35561</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Thu, 25 Jun 2026 10:47:31 GMT</pubDate></item><item><title><![CDATA[Reply to Server Initialization Errors - Mib and Configuration on Fri, 12 Jun 2026 16:51:39 GMT]]></title><description><![CDATA[<p dir="auto">Regarding the XML error, is there a way to find out which section the error originates from? This makes it difficult to view the server logs over time.</p>
<p dir="auto">Regarding the MIB error, yes, the date changes and when I compile via the GUI a new file is created, but it remains invalid, although no error is reported.</p>
<p dir="auto">I've had to manually edit some MIB files before uploading them to the interface due to inconsistencies in their definitions, but I don't remember exactly which ones.</p>
]]></description><link>https://forum.netxms.org/post/35545</link><guid isPermaLink="true">https://forum.netxms.org/post/35545</guid><dc:creator><![CDATA[lhpaladin]]></dc:creator><pubDate>Fri, 12 Jun 2026 16:51:39 GMT</pubDate></item><item><title><![CDATA[Reply to Server Initialization Errors - Mib and Configuration on Tue, 09 Jun 2026 09:50:19 GMT]]></title><description><![CDATA[<p dir="auto">XML parser error is not really an error - this happens in some places, e.g. if configuration of a notification channel is empty (or contains only comments).</p>
<p dir="auto">/var/lib/netxms/netxms.cmib is more interesting. Is your server running under root user or some other user? Does this file change it's modification time when you compile MIBs from the GUI? You can just move this file to some other folder and then check if it's recreated by mib compilation.</p>
]]></description><link>https://forum.netxms.org/post/35524</link><guid isPermaLink="true">https://forum.netxms.org/post/35524</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Tue, 09 Jun 2026 09:50:19 GMT</pubDate></item></channel></rss>