Wow, thanks, that will work: These nodes are up for about 15 minutes. If I set the custom attribute to 10 minutes every node should get one poll per uptime 

If you are using 3.9.280 now, you can safe upgarde to latest 3.9 that is 3.9.420 first Atleast i found 3.9.420 in repo for ubuntu focal https://packages.netxms.org/ubuntu/pool/focal/main/n/netxms/ You can also migrate the DB to a virtual server, just use a Postgresql guide on how to migrate data. Then you have both Bare-Metal db + VM DB you can connect NetXMS server to. You can now edit netxms Bare-Metal installation to point to VM DB (Ie Snapshot as backup), then upgrade bare-metal install to latest 4.4 stable. Rollback plan will be to reinstall  3.9.420 and point to bare-metal db that you didnt touch

Thank you very much Filipp! I did not think/know about the different functions which are available for the threshold.  I should get it to work with the information you gave me   Kind Regards, Mitch

This view was just forgotten to move to the new UI, thanks for reminding.

Central server is typically can handle thousands of nodes on it's own, so there's no much need in offloading it, but yes, proxies can be used that way. More interestingly - with cache mode on proxy can collect data even if there's no connection to central server. You can have several proxies on a zone - in this case they will be in HA mode, exchange hearthbeat messages and data collection will move to one if another one goes down

Resolved Had installed Tomcat 10, roled back to Tomcat 9 and everything works perfectly.

Hi, I noticed that the error appeared again, but observing the repetition of the event I understood that when NetXMS adds a new node through network discovery, this node would later generate the error in the database. I'm not sure what the reason is, but it seems to me that if the node is not compatible with the agent, simply check the option to disable the use of the NetXMS agent in the status poll and the error would disappear. It seems to be some bug.

There is my agent config, ping/ssh subagents and enableProxy/enableSNMPProxy were already on: LogFile={stdout} # or file name, might want to mount a volume for this DebugLevel=0 # 0-9 MasterServers=0.0.0.0/0 #list of NetXMS servers with full access #ControlServers=… # list of NetXMS servers with read+execute actions access #Servers=… # list of NetXMS servers with read-only access SubAgent = linux.nsm SubAgent = ecs.nsm SubAgent = filemgr.nsm SubAgent = ping.nsm SubAgent = logwatch.nsm SubAgent = mqtt.nsm SubAgent = netsvc.nsm SubAgent = portcheck.nsm SubAgent = ssh.nsm SubAgent = mqtt.nsm #SubAgent = winperf.nsm #SubAgent = wmi.nsm #SubAgent = ups.nsm EnableProxy = yes EnableSNMPProxy = yes EnableSNMPTrapProxy = yes EnableSyslogProxy = yes EnableTCPProxy = yes You're right, I didn't need the 161 NAT rule, I've dropped it.  But still, I've tried both things:   - creating an icmp.ping metric to a node that container can actually ping => the metric status is in ERROR state   - adding manually a node, put it in the zone, then defining my mikrotik container agent node as a proxy for ICMP and SNMP => in the status poll logs I can see "Starting ICMP ping via proxy", followed by "Node is still unreachable"

Dear support team is there way to stop collecting and processing rpm packages on RHEL installation of agent? We have currently problem with corruption on rpm db which causes huge amount of packages removed and added and agent reads them. This issue is looks like Redhat bug, but i have all installation updated and same behavior occurs on another RHEL 8 servers. I don't want unmonitor this server, just want skip packages processing. Is there any option's on agent to stop collecting rpm db data ?

Thank you Victor.  Faisal

In the scripting language it's different then in SQL. When the script (you probably use script threshold) is invoked, DCI value is contained in $1 variable. Any operation with this variable will take it as a whole thing.

Thank you for the info!

@filipp-sudanov said in Connection with NetXMS server was lost with NetXMC 4.4.2 version: This error was fixed, fix will be included in patch release that should be out this week. Hello! Exactly the same problem after updating to 4.4.2, when connecting a client, the connection is reset. Waiting patch

I figured out how to do it myself, thanks . the question is closed

We will increase the limit, fix will be in a patch release that should be out in a few days.

Thanks for your quick reply, I'll do that!

Please add DebugLevel = 6 to agent config file and share full agent log since it's start till sessions run out. You can share the log in private message if needed.

Make a script named getPackageVersion in script library: packageName = $ARGS[1]; if (packageName == null) return "package name not provided to script"; for (s : $node->softwarePackages) { if (s->name == packageName) { return s->version; } } Then create a script DCI with metric e.g.: getPackageVersion("curl") The script is using information about packages collected during configuration poll, so it will provide a value even if the agent is not available at the moment.

Hi, We had a discussion with developers and formulated how this could be implemented somewhere in the future: https://track.radensolutions.com/issue/NX-2466 For the time being, you can create dummy nodes (specifying ip address 0.0.0.0), create one script DCI on each of these nodes with "Use this DCI for node status calculation" and use script to determine status (script should be returning 0...4 for Normal...Critical)

4.4.2-30 Work fine, without crashes..