<?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[Cannot Delete Nodes]]></title><description><![CDATA[<p dir="auto">Good Afternoon,</p>
<p dir="auto">I'm a new user to NetXMS. I'm running version 2.2.4 on Centos 7.4. I'm using a MariaDB Galera cluster for the database because we're setting this up to run in across multiple datacenters. I'm having a problem where I cannot delete a node from NetXMS. Using the desktop management console I've tried right clicking and and left clicking delete on the node, it disappears from the management app and if I close it and reopen it its still not there, however, if I try to re-add the node it says there's an IP conflict. If I stop the netXMS daemon and restart it, the nodes show back up. I tried setting them to unmanaged and trying the same thing with the same result. I tried removing all of the interfaces and then removing the node, same result.</p>
<p dir="auto">I can add nodes just fine, I can move nodes around to different containers, but I cannot seem to delete them. I am able create and delete dci parameters. I ran the nxdbmgr check also.</p>
<pre><code>[root@nms1 etc]# nxdbmgr check
NetXMS Database Manager Version 2.2.4 Build 9506 (2.2.4) (UNICODE)

Checking database (excluding collected data):
Database is locked by server 10.3.1.1 [nms1.allstatehosting.local Linux Release 3.10.0-693.21.1.el7.x86_64]
Do you wish to force database unlock? (Yes/No) y
Database lock removed
* Checking zone object properties                                      [PASSED]
* Checking node object properties                                      [PASSED]
* Checking node to subnet bindings                                     [PASSED]
* Checking interface object properties                                 [PASSED]
* Checking interface bindings                                          [PASSED]
* Checking network service object properties                           [PASSED]
* Checking network service bindings                                    [PASSED]
* Checking cluster object properties                                   [PASSED]
* Checking cluster member nodes                                        [PASSED]
* Checking template to node mapping                                    [PASSED]
* Checking object properties                                           [PASSED]
* Checking container membership                                        [PASSED]
* Checking event processing policy                                     [PASSED]
* Checking network map links                                           [PASSED]
* Checking data tables                                                 [PASSED]
* Checking raw DCI values table                                        [PASSED]
* Checking DCI thresholds                                              [PASSED]
* Checking table DCI thresholds                                        [PASSED]
Database doesn't contain any errors
Database check completed
</code></pre>
<p dir="auto">Anybody have any thoughts?</p>
<p dir="auto">Thanks,<br />
Brian</p>
]]></description><link>https://forum.netxms.org/topic/5495/cannot-delete-nodes</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 12:41:32 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/5495.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 15 Mar 2018 19:17:35 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Cannot Delete Nodes on Fri, 16 Mar 2018 03:27:34 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">I believe that can happen if a device is scheduled for removal, but hasn't actually been removed from the database yet.<br />
In memory, it will be gone (hence you can't see it in the Console), but it is still in the database (causing conflicts when you try to re-add the node).<br />
The syncer thread which runs every minute by default should write updates to the database, but I guess it could be running into problems.</p>
<p dir="auto">Try setting debug for obj.sync and sync to 7 and watch the NetXMS server logs after you delete the object.<br />
To enable debug open the NetXMS Server Console and enter "debug obj.sync 7" and "debug sync 7".<br />
An example of a deletion gone wrong from our logs:</p>
<pre><code>Object 120.150.216.0/24 [205198] marked for deletion
Unable to delete object with id 205198 because it is being referenced 8 time(s)
</code></pre>
<p dir="auto">In our case the above was removed after about an hour (we run the syncer every 5 minutes), presumably because the references were eventually removed.</p>
<p dir="auto">Cheers</p>
]]></description><link>https://forum.netxms.org/post/24016</link><guid isPermaLink="true">https://forum.netxms.org/post/24016</guid><dc:creator><![CDATA[Tursiops]]></dc:creator><pubDate>Fri, 16 Mar 2018 03:27:34 GMT</pubDate></item></channel></rss>