NetXMS Forum

+1

Hi! I've changed the drbd.cpp (protocol version should also work as expected). These changes are included in 1.2.10 release. Thank you for fixing it! Best regards, Victor

Works now, I've also been waiting for this

Hi, We've been having crashes similar to these for quite some time (from v1.2.0 up to v1.2.5) on windows 2003 x86. I'm curious if we're having the same problem. Are there multiple events from the NetXMS Agent in the event log, starting minutes up to hours before the actual crash, with the message: Communication session broken: An existing connection was forcibly closed by the mote host. or does the server act strangely before crashing (slow response, node statuses changing to unknown, failing to show graphs/history, ...)? In our case, I've never been able to pick anything useful out of the server logfile or the crash dumps, possibly because the logs fill up very quickly and memory corruption can take place long before the server actually tries to use the corrupted memory and crashes. How often does your server crash? The rate at which the problem occurs seems tied in with queue lengths and memory usage in general. When we had large database writer queue lengths (> 100,000) the server was crashing 2-3 times a day, but after improving database performance somewhat (more database writers etc) it's now down to every 2-3 weeks. I'm also hoping https://www.netxms.org/forum/general-support/out-of-memory-netxms-v1-2-5/ is related to this problem, as on linux there's the chance that valgrind might catch the culprit. Kind regards, bdefloo

Hi! I incorporate patch into the trunk. Thank you! Best regards, Victor

Thank you, not to urgent. So happy to wait for the next build. Regards Aron

Hello, Thank you that has worked Many Thanks Aron

Hello Many thanks, is now running successfully on the patched version. Best Regards Aron

@athesis said in Dynamic Content Network Map: Hi, I would also support an Display like that, it would be enoumous advantage for traffic monitoring and clarity what where is. At least to say witch port is connected to what device etc. Just one comments regarding which port is connected to what device - it's already possible. You can either do this manually (just link objects on the map and put appropriate labels on link), or automatically (create new map of type "layer 2 topology", put some network device as a seed, and NetXMS will build and update it automatically with known layer 2 connectivity information). There are also minor move toward active network maps: you already can show values of selected DCIs in object's tooltips. Just check "show in object tooltips" checkbox in DCI properties, and value of this DCI will be displayed when you hover mouse over node object on map. I'll try to add options for displaying DCI data over map links in 1.2.8 or 1.2.9, depending on how well it will go. Best regards, Victor

Hi! Yes, this is a bug in the Java console. Just fixed it - version 1.2.3 will work correctly. Best regards, Victor

Hi! I suppose that connection to server was dropped by timeout or due to some other reason, and ODBC subagent does not reconnect. I'll check it. Best regards, Victor

Hello, Thank you for the build. Provisionally looks good, running as expected and memory usage is stable with no obvious signs of the issue. Many thanks Aron

Thank you, that has done the trick.