@victor said in Expected number of connections:
This is firewall design problem in my opinion, as this is perfectly normal traffic pattern.
Sure, understood. Because firewall keeps connection state table entry hanging around for 60s this exacerbates the apparent "issue".
Lightning maint window, stopped Zabbix proxy service for a few minutes.
This is the cause:
17:32:56.994760 IP 192.168.1.1.54475 > 192.168.10.18.161: C="public" GetRequest(28) .1.3.6.1.2.1.1.2.0
17:32:57.029465 IP 192.168.10.18.161 > 192.168.1.1.54475: C="public" GetResponse(39) .1.3.6.1.2.1.1.2.0=.1.3.6.1.4.1.9.6.1.81.28.2
17:32:57.032267 IP 192.168.1.1.49414 > 192.168.10.18.161: C="public" GetRequest(30) .1.3.6.1.2.1.2.2.1.7.49
....
17:33:04.334785 IP 192.168.10.18.161 > 192.168.1.1.36845: C="public" GetResponse(33) .1.3.6.1.2.1.2.2.1.5.100409=0
17:33:04.346389 IP 192.168.1.1.51426 > 192.168.10.18.161: C="public" GetRequest(28) .1.3.6.1.2.1.1.3.0
17:33:04.381043 IP 192.168.10.18.161 > 192.168.1.1.51426: C="public" GetResponse(33) .1.3.6.1.2.1.1.3.0=2487595200
The source port is different every time, so this is a new "connection" [UDP is connectionless] every time from the firewall's POV. In this case, 172 connections in 8 seconds. The real age of the connection is only a few tens of ms but the firewall doesn't know this and only ages it out after 60s of no traffic.
We are simply collecting more data with NetXMS than Zabbix, so the apparent effect is amplified.
This is a bit tricky, the host in question also runs a Zabbix proxy. But it's definitely NetXMS generating this traffic. I will see what I can do.
Added a subnet to NetXMS yesterday, ran a discovery on it and then disabled the discovery. This is monitored via a NetXMS agent as a proxy.
It has picked up 45 devices, a mixture of switches, APs and firewalls. I am not really sure exactly how many metrics are being collected in total across the whole network, but I have not specifically started collecting [for example] interface throughput stats or created any custom templates. NetXMS will just be collecting whatever it does by default, things like ICMP reachability, FDB, interface and instance discovery.
In Server Configuration, every parameter with word "poll" or "interval" is at the default except NetworkDiscovery.ActiveDiscovery.Interval and NetworkDiscovery.PassiveDiscovery.Interval which are set to 43000s.
So the reason I am asking this, is that since this network was added, the firewall is showing an additional 2000-4000 connections in to this network from the NetXMS agent. One switch has 64 SNMP connections to it. 19 were opened in the same second. Each connection has <100 TX/RX bytes. So it seems to me that NetXMS is being a bit profligate with how it opens connections.
If I create a new active discovery target and assign a zone to it, the proxy node chosen is "zone proxy" even it doesn't exist. Active discovery will then fail,
Cannot find zone proxy node for address range **10.**0.0.0/24@6
but nothing in the UI to indicate this.
"Clear selection" button on "Proxy node" just reverts to "Zone proxy".
I can work around this by using the server itself as the "Proxy".
Version 5.0.3.
I uploaded a bunch of MIBs using the "SNMP MIB files" tool.
The only one that actually works had the extension .mib, all the rest with the extension .MIB are ignored [when you compile the MIBs, it only lists the .mib file].
I guess I can understand that if I just dropped these files somewhere then there may be some rules to follow, but I used the UI to upload these and was given no feedback to indicate that they wouldn't be used. So I think that makes this a bug.
5.0.3, using nxmx-light as a webapp served by tomcat 9.0.58 and openjdk-17-jre 17.0.10+7-1~22.04.1
If I pop out a graph view on a host, I get a server error and stack trace:
org.eclipse.swt.SWTException: Invalid thread access
org.eclipse.swt.SWT.error(SWT.java:3753)
org.eclipse.swt.SWT.error(SWT.java:3676)
org.eclipse.swt.SWT.error(SWT.java:3647)
org.eclipse.swt.widgets.Display.error(Display.java:2309)
org.eclipse.swt.widgets.Display.checkDevice(Display.java:2291)
org.eclipse.swt.widgets.Display.timerExec(Display.java:1127)
org.netxms.nxmc.tools.ViewRefreshController.setInterval(ViewRefreshController.java:92)
org.netxms.nxmc.modules.datacollection.views.HistoricalGraphView.configureGraphFromSettings(HistoricalGraphView.java:382)
org.netxms.nxmc.modules.datacollection.views.HistoricalGraphView.createContent(HistoricalGraphView.java:435)
org.netxms.nxmc.base.views.View.create(View.java:221)
org.netxms.nxmc.base.views.ViewStack.pushViewInternal(ViewStack.java:370)
org.netxms.nxmc.base.views.ViewStack.setView(ViewStack.java:323)
org.netxms.nxmc.base.windows.PopOutViewWindow.createContents(PopOutViewWindow.java:202)
org.eclipse.jface.window.Window.create(Window.java:451)
org.eclipse.jface.window.Window.open(Window.java:834)
org.netxms.nxmc.Startup.createUI(Startup.java:298)
org.eclipse.rap.rwt.internal.lifecycle.RWTLifeCycle.createUI(RWTLifeCycle.java:177)
org.eclipse.rap.rwt.internal.lifecycle.RWTLifeCycle$UIThreadController.run(RWTLifeCycle.java:290)
java.base/java.lang.Thread.run(Thread.java:840)
org.eclipse.rap.rwt.internal.lifecycle.UIThread.run(UIThread.java:107)
Incidentally, Google claims that it has never heard of the NetXMS "Pop out view"!
No results found for netxms "pop out view".
Results for netxms pop out view (without quotes):
Upgraded server from 4.5.x to 5.0.3 yesterday.
Using agent 4.4.3 on Windows 10 as a proxy at a remote site. This monitors all nodes in the zone.
This continues to work as an ICMP proxy without issue, that I can see.
@victor said in NetXMS 4.5 patch release 1:
- Fixed server crash when interface list cannot be read from SNMP device and option to ignore interfaces in NOT PRESENT state is on
Confirmed, no longer crashing when this option is enabled.
Also, the option itself works 
It's definitely this, has stayed up >24h since I disabled the option.
This seems to be causing some instability. With the ignore NotPresent interfaces enabled, the server crashes after a few minutes. Even with the log level turned up to 7, the log file just goes silent and the process dies. It does leave this behind in dmesg, however:
[17465427.164364] $POLLERS/WRK[1229844]: segfault at 8 ip 00007fbab4970ea6 sp 00007fba751bc760 error 4 in libnxcore.so.45.0.0[7fbab485c000+24c000]
[17465427.164413] Code: 44 24 38 48 83 e8 04 48 89 44 24 40 48 b8 02 00 00 00 02 00 00 00 48 89 44 24 48 48 b8 01 00 00 00 08 00 00 00 48 89 44 24 50 <41> 8b 4c 24 08 85 c9 0f 8e 85 00 00 00 48 89 6c 24 10
4c 89 e5 eb
[17465810.908547] $POLLERS/WRK[1255212]: segfault at 8 ip 00007fb84b476ea6 sp 00007fb7dbb4d760 error 4 in libnxcore.so.45.0.0[7fb84b362000+24c000]
[17465810.908560] Code: 44 24 38 48 83 e8 04 48 89 44 24 40 48 b8 02 00 00 00 02 00 00 00 48 89 44 24 48 48 b8 01 00 00 00 08 00 00 00 48 89 44 24 50 <41> 8b 4c 24 08 85 c9 0f 8e 85 00 00 00 48 89 6c 24 10
4c 89 e5 eb
[17465996.329600] $POLLERS/WRK[1255986]: segfault at 8 ip 00007fd277169ea6 sp 00007fd223437760 error 4 in libnxcore.so.45.0.0[7fd277055000+24c000]
[17465996.329615] Code: 44 24 38 48 83 e8 04 48 89 44 24 40 48 b8 02 00 00 00 02 00 00 00 48 89 44 24 48 48 b8 01 00 00 00 08 00 00 00 48 89 44 24 50 <41> 8b 4c 24 08 85 c9 0f 8e 85 00 00 00 48 89 6c 24 10
4c 89 e5 eb
[17466198.216260] $POLLERS/WRK[1257237]: segfault at 8 ip 00007f6d662d9ea6 sp 00007f6d2b22b760 error 4 in libnxcore.so.45.0.0[7f6d661c5000+24c000]
[17466198.216276] Code: 44 24 38 48 83 e8 04 48 89 44 24 40 48 b8 02 00 00 00 02 00 00 00 48 89 44 24 48 48 b8 01 00 00 00 08 00 00 00 48 89 44 24 50 <41> 8b 4c 24 08 85 c9 0f 8e 85 00 00 00 48 89 6c 24 10
4c 89 e5 eb
NX-2275 (Option for ignoring interfaces in NOT PRESENT state)
Thankyou for this Christmas present!
How are these intervals chosen? Looks a bit random. 1323, 1421, 1520, etc.
Also would be great if there was a marker at 00:00.
This is the new UI. I am testing from Linux.
Tested this in Chrome for reference....it behaves fine. Logged back in with Firefox, also behaves fine! OK, seems like it takes a few minutes of using it, navigating around, etc, before it starts happening.
It seems like the unscrollable tabs are linked to the divider moving around, as soon as the divider moved itself, then the Node-level tabs became inaccessible.
Tomcat 9.0.58
NetXMS server 4.4.3
WAR file 4.4.3
Firefox 119 on the client side.
I get various UI glitches when navigating around.
A popup with 'Cannot invoke "org.eclipse.swt.graphics.Color.getRGB()" because "color" is null' will appear at random.
The vertical divider that separates the navigation tree from the main pane of the interface will jump around when clicking in to different icons on the left. It also moves around when resizing the browser window.
There is no scrollbar so at Node level the right-most tabs will simply be off the screen with no way to get to them. Lack of scrollbars applies in other areas as well.
Thanks as always, Victor!
I am only using the web client.
The screenshot showing it working is from the Legacy web client on 4.1.
I wasn't able to get the legacy web client 4.4 working. Perhaps this is a difference between legacy and new.
Yes, that worked.
Thanks, I've ticked that, re-added the firewall and will wait to see what happens...