NetXMS Support Forum

Yes, you have to get node object first. Global variables $node and $object refer to current node. You can use function FindObject to get other objects. This function accepts either object ID or name. For example, if you want to print alarms for node named "netxms-server":

node = FindObject("netxms-server");
for(a : node->alarms)
{
println(a->message);
}


Best regards,
Victor

3.5.136 is now available in repository.

Best regards,
Victor

Packages on download page were updated to version 3.5.152 due to packaging issues. Functionality wise this version is identical with 3.5.136.

You can mark option "tool generates output" in object tool configuration and use println in script for sending output back to client.

Best regards,
Victor

Hi all!

NetXMS agent was updated to version 3.5.136 - it fixes possible agent crash when accessing agent thread pool metrics.

Best regards,
Victor

Hi,

do you monitor thread pools on agent? If yes, try to temporarily disable those DCIs. Recently we've discovered bug that can lead to agent crash after querying data for thread pool WEBSVC.

Best regards,
Victor

P.S. We started build 3.5.136 - it should be published in few hours and probably will fix that.

Hi,

you have to pass them as script arguments and then access them via $ARGS array. For example, you can create library script named "TestScript" as this:

trace(0, "field1 = " . $ARGS[1]);
trace(0, "field2 = " . $ARGS[2]);


and configure it in object tool as this:

TestScript("$(Field1)", "$(Field2)")


Best regards,
Victor

No, at least at the moment. All that user support application provides is configurable actions menu for the user and screenshot functionality. We do not have any specific plans for it yet. Current functionality for user agent was developed at request from one of our customers.

Best regards,
Victor

Hi,

please try updating to 3.5.133. If it won't help try to run netxmsd under gdb and provide stack trace.

Best regards,
Victor

Hi all!

We just published patch release for version 3.5 (binary version 3.5.133) that fixes few critical issues in server and database manager. Full change log:

- Fixed server deadlock when unreachable node is deleted
- Fixed SNMPv3 performance issue
- Fixed issues:
        NX-1966 (MySQL / MariaDB database access performance issues)

Only server component is affected, there is no need to update agents or UI.

Best regards,
Victor

In agent config you should specify path to SSH config - you cannot just put SSH configuration options to NetXMS agent config. So in nxagentd.conf you should have something like


[SSH]
ConfigFile = /etc/nxagentd-ssh-config


and in file /etc/nxagentd-ssh-config


HostKeyAlgorithms +ssh-rsa


Best regards,
Victor

Looks like router supports only ssh-dss and ssh-rsa as host key algorithms and they are not offered by client. You may try to add

HostKeyAlgorithms +ssh-rsa

to your .ssh/config file, or create separate config file for SSH subagent with that line and specify it in nxagentd.conf by adding

ConfigFile = path_to_config

in section [SSH].

Best regards,
Victor

Hi,

in 3.4 we have added reading SSH config by SSH subagent - could it be that you have something configured there? Also, what KEX algorithms this Mikrotik supports? You can run ssh with -v option and check it. This is sample output from my router:

debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: diffie-hellman-group-exchange-sha256

Best regards,
Victor

Hi,

seems that currently it is not possible. There is feature request for that for some time already: https://track.radensolutions.com/issue/NX-1483, which we will definitely implement at some point. Also NXSL function GetDCIValues could be fairly easily modified to return list of table DCI values for given period.

Best regards,
Victor

Hi,

NetXMS server does not support alternate database servers directly. It is only possible if database client provides such functionality (for example, Oracle client when connecting to Oracle RAC), or if you can provide virtual IP for server to connect to, that migrates from one DB cluster node to another.

Best regards,
Victor