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!! D: )
Any ideas of what I could do about this? :'(
Thanks everyone for the great support,
Jhúlia Graziella
Hi,
what do you mean by "excluded"? Did you delete the node or unbind it?
Best regards,
Victor
I'm sorry about my english. By "excluded" I mean deleted.
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?
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
Thank you very much! ;D