NetXMS Support Forum

Hi!

There's an issue - when we call .cmd file that produces some output, the execution fails.  (https://track.radensolutions.com/issue/NX-2242)

Currently you can try this in agent configuration file:
ActionShellExec = kill_qv:c:\NetXMS\batches\kill_qv.bat >nul

Most probably you've ran into some bug that happens very rarely.
In such situation it would be beneficial to capture threads before you restart the server. It could be done by running this script (it requires gdb to be installed on the system): https://github.com/netxms/netxms/blob/master/tools/capture_netxmsd_threads.sh

Script should be executed 3 times with 20-30 interval. This would give us debug information to understand where exactly the threads have hanged.

This could also be access denied due to access control on the server.
In properties of the node under Access Control does your NetXMS user has "Download files" access right?

Could it be so on your system, that there is another folder under Infrastructure Services that contains these nodes?

Hi!

Yes, it's a bug, it will be fixed and included in next patch release.

Сделано в девелоперской ветки, где-то в течении пары недель войдет в релиз.

Hi!

NetXMS supports a limited number of SMS gateways, the list is here: https://www.netxms.org/documentation/adminguide/event-processing.html#drivers
Your software is not supported.

Is there a way to send SMS using this software by executing some command at the command line of that server?

It should be the same logic in 4.0 - state of ports on first configuration poll should become expected state.
It's SNMP device, right? What is the model of the device? In object details -> overview what is written next to "Driver"?

When server starts it reads RAW_DCI_VALUES table from DB, takes last_poll_time and schedules polling based on that time. nxdbmgr should have fixed time value in that table, but you can double-check.

The other place where timestamp is stored is when you have cache mode turned on. In this case agent (which collects data from the system where it's running) or proxy (which collects data from SNMP devices) has a table in it's database where that timestamp is stored.
The simplest is to stop proxy, delete it's database (nxagentd.db file) and start the proxy again. Then run configuration poll for the proxy, it should receive data collection configuration form the server.

In 4.0 auto-apply was reworked so that it happens from template/container side. But the case when a new node is added was kinda forgotten. Will discuss that internally with developers.

For snmp only trap sending is currently implemented - it's a subsort of notification channels.

Yes, you can use nxshell or web api.

And there's also fan-out driver that send all collected data to InfluxDB.

This looks to be the most recent version.

What's the value of Objects.AutobindPollingInterval in Configuration -> Server configuration?

Note that now there's poll on templates themselves, what happens if you right-click a template and select Poll -> Automatic bind?

Try adding
trace(0, "some text");
to your auto-bind script. When you do automatic bind poll, does this "some text" appear in server log?

Hi!

Can you check nxmc log (it resides in your home folder in .nxmc/data/.metadata/.log) may be there are any errors there when dashboard stops refreshing.
Also, can you export your dashboard and attach here?

It should work this way. To double-check, can you show contents of nxapisrv.properties?
Where nxapisrv.properties file is located? It should be in classpath of tomcat.

Currently NXSL does not have options to change zone of a node.

This could be done using nxshell script - this way you can do everyting that could be done from nxmc, but there's some learning curve. Some information is available here: https://wiki.netxms.org/wiki/Using_nxshell_to_automate_bulk_operations