<![CDATA["Garbage" nodes not being excluded]]>I'm currently playing with NetXMS and populated my network with about 1000 nodes and then I created a new Zone and put an agent to be responsible for polling some nodes that are under a proxy server.
Now I'm dealing with the followint issue: whenever I exclude a node from the Infrastructure Services container it DOESN'T get excluded from its corresponding Zone on Entire Network! And if I try to re-create a node with same IP it returns an error because tecnically it already exists. So every time I exclude a node from Infrastructure Services I have to manually exclude it from Entire Network and it's kinda bugging me.
Another matter: if I move a node from a zone to another and then try to re-move it back to its initial zone it returns an error telling that the node already exists in that zone (but...wait, what? It does'nt, I have moved it!! 😧  )

Any ideas of what I could do about this?  😢

Thanks everyone for the great support,

Jhúlia Graziella

]]>https://forum.netxms.org/topic/3762/garbage-nodes-not-being-excludedRSS for NodeFri, 13 Nov 2026 16:44:25 GMTThu, 07 May 2015 17:56:46 GMT60<![CDATA[Reply to "Garbage" nodes not being excluded on Mon, 11 May 2015 13:29:45 GMT]]>Thank you very much!  ;D

]]>https://forum.netxms.org/post/16827https://forum.netxms.org/post/16827Mon, 11 May 2015 13:29:45 GMT<![CDATA[Reply to "Garbage" nodes not being excluded on Mon, 11 May 2015 07:02:30 GMT]]>It is not related to database housekeeping, but to in-memory object cache inside NetXMS. It seems that after move/delete object still stuck in internal index, and so adding new object/moving it back is not working. I'll try to reproduce this issue on my test system.

Best regards,
Victor

]]>https://forum.netxms.org/post/16823https://forum.netxms.org/post/16823Mon, 11 May 2015 07:02:30 GMT<![CDATA[Reply to "Garbage" nodes not being excluded on Fri, 08 May 2015 18:34:25 GMT]]>And about moving nodes from a zone to another, this is the message I get:

Cannot change zone for node a-rg-fcc-ula-301-image-01 [6644]: Address already in use
Address already in use

If I move node a-rg-fcc-ula-301-image-01 from zone A to zone B, it works fine. But if I try to move it back to zone A I get this error. (And the same error if I try to move some node from zone B to A and then back to zone B.
I started to think this may be because the time the housekeeper runs: i'm using postgre, so maybe the DB isn't properly refreshed without the housekeeper executing vaccum?

]]>https://forum.netxms.org/post/16812https://forum.netxms.org/post/16812Fri, 08 May 2015 18:34:25 GMT<![CDATA[Reply to "Garbage" nodes not being excluded on Fri, 08 May 2015 18:04:03 GMT]]>I'm sorry about my english. By "excluded" I mean deleted.

]]>https://forum.netxms.org/post/16810https://forum.netxms.org/post/16810Fri, 08 May 2015 18:04:03 GMT<![CDATA[Reply to "Garbage" nodes not being excluded on Fri, 08 May 2015 10:21:41 GMT]]>Hi,

what do you mean by "excluded"? Did you delete the node or unbind it?

Best regards,
Victor

]]>https://forum.netxms.org/post/16799https://forum.netxms.org/post/16799Fri, 08 May 2015 10:21:41 GMT