NetXMS Support Forum

No, in Users and groups all access rights are related to global things - e.g. ability to edit server actions - this is not related to any specific node. But things related to nodes and other objects - ability to modify configuration, edit comments and edit maintenance journal are set in the object tree - this way you can limit users to access only some nodes which is typically needed.

Right, looks like you are using Windows Event Log synchronization.

But how do details of NetXMS event "Win Event - Failed account log on" look in NetXMS event log?

"Disable usage of Modbus for all polls" sould be in Polling tab in properties of a node. But I thing there was some version of NetXMS where this checkbox was not present, so try upgrading to the latest.

As I remember, this information might be present in parameters of that event. If you open Event Log in NetXMS, find such event there and double-click it, a window should open with event details. Please share it here

Try connecting to agent port from your server with telnet:

telnet AGENT_IP 4700

it should establish connection.

The other thing to check is that your server IP is in agent configuration file in
MasterServers = IP_OF_YOUR_SERVER

Developers of NXSL may say in more details, but as far as I understand, the problem is that NXSL is loosely-typed language. So if you run this:
a = 33;
println(typeof(a));
a = "33";
println(typeof(a));

you'll see that when string contains only numbers, it's type is automatically converted to integer. Given that, using + both for addition and concatenation is problematic.

To add, since some time ago there are f-strings, e.g.:

value = 123;
println( f"The value is: {value}" );

so the need for concatenation might be not so high.

.. is already working for concatenation in v. 4.5. It's planned to have automatic conversion when migrating to 5.0 that would go through all scripts and change them.

In 5.0 there are compilation warning on use of deprecated functions, but these only present in script editor. The were some plans to check scripts everywhere in the system for deprecated functions, I will check later.

At some point in the future, when https://track.radensolutions.com/issue/NX-2322 will be implemented it would be possible to specify muliple OIDs and they will appear as variables in transformation script.

For now - either a script DCI that does all SNMP job and calculation and returns final result, or SNMP DCI that reads one OID and the rest being read in transformation script, e.g.:
totalMem = $1;

transport = $node->createSNMPTransport(); 
if (transport == null) return null;

freeMem = transport->getValue(".1.3.6.1.4.1.14823.2.2.1.1.1.11.1.4.1");
if (freeMem == null) return null;

return format(100UL * freeMem / totalMem, 1, 0);
The only bonus of the first approach is that you can perform recalculation for historical collected values.

Can you install netxms-dbg package and run netxms under gdb. It should be like:

gdb netxmsd
run

when it crashes, issue
bt
and share the output

You can enable debug related to notification channels. This can be done without restarting server from Tools->Server Debug Console or from nxadm command line utility. Issue the following commands:

debug nc.* 6
debug ncd.* 6

You can check current status of debug by issuing

debug


Then check netxms server log file (/var/log/netxmsd on linux).

Hi!

I've checked with a developer yesterday - currently there might be issues with correlation for nodes that are behind proxy. This will be investigated whenever developer resources are available.

Looks like some screenshots are missing.
But a question regarding your text - may be you can just use your threshold script right on "Port Speed auf x/x/x" DCI?

This SNMP OID is a counter (https://oid-rep.orange-labs.fr/get/1.3.6.1.2.1.31.1.1.1.6). When setting up a DCI, on transformation tab select delta calculation - average delta per second.

Да, pinboard пока что не сохраняется. Месяцев через несколько наверное будет уже сделано

Должен быть отдельный пекедж netxms-agent-asterisk

There might be some changes recently on how agent handles actions - it might terminate them after some quite short time unless "action produces output" is enabled.
Can you please enable
DebugLevel=6
in agent config and share the log file for the moment when action is being executed?

P.S.
There's actually another approach that might help - In Configuration->Packages you can have executable or archive. When you select "Deploy package..." (in new nxmc this is done from context menu of nodes or containers), file will be uploaded and in case of executable it's possible to specify a command that will be executed. See docs for more info: https://www.netxms.org/documentation/adminguide/package-manager.html#