<![CDATA[Issue on update status link on maps]]>Hello everyone.
First of all, my compliments for the beatifull work done by Victor and his team for this powerful product.
We have been using netxms for a few years and I must say that it is a truly flexible and "simple" product to configure compared to its competitors
I would like to ask for support for a problem.
After update to the last server versione there is a problem with the status check of the map links. Now they remain in indefinite state color: blue. Checking the link settings, instead of name of the port used to calculate the status, appears the interface ID between the minor and major signs.
Leaving the map open, some links, after a few minutes, return ok, while others don't.
I checked the db (postgresql) and there are no errors and no performance issues.
It may be that we have too many nodes (Object ID is over 800.000)
Any idea?
I attach some screenshot
Thank you very much.

Massimo

Netxms2.PNG

Netxms1.PNG

]]>https://forum.netxms.org/topic/6499/issue-on-update-status-link-on-mapsRSS for NodeFri, 13 Nov 2026 10:31:42 GMTThu, 16 Apr 2020 13:40:28 GMT60<![CDATA[Reply to Issue on update status link on maps on Mon, 25 May 2020 07:46:57 GMT]]>Hi Viktor,
thank you for the solution. It's works
I'm sorry I didn't read change log properly. Surely this information was there.
I renew my congratulations for this fantastic product.

Best regards

Massimo Gentili

]]>https://forum.netxms.org/post/27946https://forum.netxms.org/post/27946Mon, 25 May 2020 07:46:57 GMT<![CDATA[Reply to Issue on update status link on maps on Mon, 25 May 2020 07:09:57 GMT]]>Hi,

this is caused by lazy object sync introduced in 3.2 - interface objects are no longer synced on login, but only when you expand node or select interfaces tab. We will add appropriate on-demand synchronization for maps as well. In the meantime as a workaround you can try to turn on option "full object synchronization on startup" in console properties (File -> Properties -> Object Browser). This is client-side setting so should be done on each client.

Best regards,
Victor

]]>https://forum.netxms.org/post/27939https://forum.netxms.org/post/27939Mon, 25 May 2020 07:09:57 GMT<![CDATA[Reply to Issue on update status link on maps on Sat, 09 May 2020 14:48:11 GMT]]>hello Filipp,
thank you for you answer.
Actually we do not use agents and there are no proxies mode enabled. We use only snmp because all nodes are netwok object or linux embedded with snmp server.
I'll try to explain the situation:
if I Search #842468 there is no result, but object is present. I can find it directly as parent's interface
I attach an example with another link and object id.
Link is blue.

  1. open link and there is no interface name but object id
  2. I find object id with #objid and there is no result
  3. I open switch parent's interface with objid and is there.

Some link after a few minutes go green or red and I can find objid like you suggest, other link like this remain in unknown state.

Why?

Thx
Massimo

Cattura.PNG

]]>https://forum.netxms.org/post/27861https://forum.netxms.org/post/27861Sat, 09 May 2020 14:48:11 GMT<![CDATA[Reply to Issue on update status link on maps on Fri, 08 May 2020 10:47:56 GMT]]>Regarding the timestamps in the future - there are basically a few scenarios how that could happened:

  • time has jumped on netxms server into the future and then back (so some values have recorded with future times during that time)
  • more probably - time problem on some agent with cache mode = on
  • not sure, but probably - time problem on netxms agent running in proxy mode
    Monitoring time on all agents is advised.

For the links on the map - does the object with ID=842468 exist? (you can search for ID in object tree with # prefix, e.g. #842468)

]]>https://forum.netxms.org/post/27854https://forum.netxms.org/post/27854Fri, 08 May 2020 10:47:56 GMT<![CDATA[Reply to Issue on update status link on maps on Sun, 03 May 2020 19:28:35 GMT]]>Hello,
I don't know if the problem in in DB, but with the command:

  nxdbmgr -d -f check

there are many errors like this:

  Found collected data for node [36849] with timestamp in the future. Delete invalid records? (Yes/No/All/Skip) Y

I checked the server system time and it's correct.
If I repeat obove command, there are always errors, sometimes with different DCI id but there are errors. If I stop netxmsd service, after first DB check and error correction, there are no more errors. It's seems that the problem is how are written data in the dci tables.

Can you help me please?
Thank you.
Massimo

]]>https://forum.netxms.org/post/27815https://forum.netxms.org/post/27815Sun, 03 May 2020 19:28:35 GMT<![CDATA[Reply to Issue on update status link on maps on Sun, 03 May 2020 14:19:54 GMT]]>Is there someone that have any idea for the reason why?
Thank you.

]]>https://forum.netxms.org/post/27813https://forum.netxms.org/post/27813Sun, 03 May 2020 14:19:54 GMT