<?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[Inconsistent database due to deleted objects]]></title><description><![CDATA[<p dir="auto">Hello Team ,</p>
<p dir="auto">I am observing the following issue. Starting the netxmsd in the logs i can see a lot of these massages:</p>
<p dir="auto">[14-Nov-2016 14:14:08.701] [ERROR] Inconsistent database: interface 6321 linked to non-existing node 6302<br />
[14-Nov-2016 14:14:08.702] [ERROR] Failed to load interface object with id 6321 from database<br />
[14-Nov-2016 14:14:08.703] [ERROR] Inconsistent database: interface 6382 linked to non-existing node 6372<br />
[14-Nov-2016 14:14:08.704] [ERROR] Failed to load interface object with id 6382 from database<br />
[14-Nov-2016 14:14:08.706] [ERROR] Inconsistent database: interface 6384 linked to non-existing node 6375<br />
[14-Nov-2016 14:14:08.707] [ERROR] Failed to load interface object with id 6384 from database</p>
<p dir="auto">[13-Nov-2016 09:21:09.508] [ERROR] Inconsistent database: container object 3602 has reference to non-existing child object 6294<br />
[13-Nov-2016 09:21:09.508] [ERROR] Inconsistent database: container object 3602 has reference to non-existing child object 6295<br />
[13-Nov-2016 09:21:09.508] [ERROR] Inconsistent database: container object 3602 has reference to non-existing child object 6302<br />
[13-Nov-2016 09:21:09.508] [ERROR] Inconsistent database: container object 3602 has reference to non-existing child object 6372</p>
<p dir="auto">Checked this and these are already deleted nodes, but obviously netxms is still trying to monitor the interfaces and some other object related to the already deleted nodes.<br />
I ran the following:</p>
<p dir="auto">service netxmsd stop<br />
mysqlcheck --auto-repair netxms -u root –p (just in case)<br />
nxdbmgr check (this fixed some inconsistencies)<br />
service netxmsd start</p>
<p dir="auto">Unfortunately i am still seeing the same errors. I ran nxdbmgr couple more times, but with no success. I checked and these are for real deleted nodes, so i am looking for a way to clear up the database from unneeded objects (related with deleted nodes).</p>
<p dir="auto">I am using NetXMS server version 2.0.6 on debian host.</p>
<p dir="auto">Another question is if there is a good practice to delete nodes/conteiners so they don't leave unparented child objects.</p>
<p dir="auto">Best Regards,<br />
Adrian</p>
]]></description><link>https://forum.netxms.org/topic/4799/inconsistent-database-due-to-deleted-objects</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 13:27:21 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/4799.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 14 Nov 2016 12:44:43 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Inconsistent database due to deleted objects on Mon, 28 Nov 2016 11:09:28 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">server supposed to handle deletion correctly and do not leave unparented objects. This is a known bug and it will be fixed eventually. There is also a registered issue for improving database check (<a href="https://dev.raden.solutions/issues/1335" rel="nofollow ugc">https://dev.raden.solutions/issues/1335</a>) - will be fixed during 2.1 development. You can leave it as is for now - references to non-existent objects are not read from database so the only consequence are errors being reported on server startup.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/21417</link><guid isPermaLink="true">https://forum.netxms.org/post/21417</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Mon, 28 Nov 2016 11:09:28 GMT</pubDate></item></channel></rss>