NetXMS Support Forum

Definitely upgrade to 2.0.2.
There were many fixes between 2.0-RC2 and 2.0.2.

If the problem still persists on 2.0.2, let us know

Connection refused usually means server is not even running.
Check if netxmsd is actually running.

Also, before doing anything with nxdbmgr, stop netxmsd.
After you are done, you need to start netxmsd again.

Definitely upgrade to 2.0.2.

There were many LDAP fixes and improvements between RC2 and released 2.0.2.

I suggest reading up on what Syslog is here http://www.networkmanagementsoftware.com/what-is-syslog

On Windows, system logs will not automatically be delivered to the NetXMS Syslog server.
(not on any OS/device for that matter, it needs configuration)

Probably what you want to look at is the LogWatch SubAgent, documentation is here:
https://wiki.netxms.org/wiki/UM:Log_Monitoring

I really recommend reading the script hints, they are available since 2.0+.
Regarding reading another DCI, see this:
https://wiki.netxms.org/wiki/NXSL:GetDCIValueByDescription
https://wiki.netxms.org/wiki/NXSL:GetDCIValueByName

Here is an example... this is a threshold on disk % usage, depending on the size of the disk.
If disk is smaller then 1GB - 80% threshold.
1GB-1TB - 90% threshold.
1TB+ - 95% threshold.
storageSize = AgentReadParameter($node, "FileSystem.Total(" . $dci->instance . ")");
if (storageSize == null)
  return false;

if (storageSize < 1099511627776) {
  // for storageSize under 1TB
  if (storageSize < 1073741824) {
    // for storageSize under 1GB, 80%
    usageThreshold  = 80;
  } else {
    // for storageSize between 1GB and 1TB, 90%
    usageThreshold  = 90;
  }
} else {
  // for storageSize above 1TB, 95% threshold
  usageThreshold  = 95;
}

if ($1 > usageThreshold)
  return true;

return false;


netxms-client contains CLI client tools (nxevent, nxalarm, etc.).
These are useful and as far as I know fully supported and maintained.

If you are new, I recommend watching the Video Tutorial series, you can find it stickied in General Support.

Hi!


return $1/10;

Is enough actually, you dont need to declare an explicit main() method/function.
See this: https://wiki.netxms.org/wiki/UM:NetXMS_Scripting_Language_(NXSL)#Script_entry_point

As for why you are seeing 0 in last values, you have "Simple delta" as delta calculation enabled.
Set delta calculation to None, and it will work.

I dont understand exactly what you are trying to achieve, but maybe look at the delta functionality for the DCI.
It will automatically calculate the change of the DCI for the time period, and show you the value the DCI changed by.

Look at the DCI Summary Tables functionality, is that what you need?

It should be fixed in 2.0.2 (as Alex mentioned) which will be released very soon.
Please check after release if it works correctly for you as well.

For me (running on 2.0.2 development build), the output of the script is correct:

FindObject - Class of node object: 4535 is Node
Type of node object: 2

*** FINISHED ***


You put the action definitions into the filemgr section, which is invalid.

Put them into the main config section (above the filemgr section declaration).

Is the MIB file present under '/usr/share/netxms/mibs/netxms.mib' (or '/var/lib/netxms/netxms.mib' if installed from .deb packages) on the server?

Working with 2.0.2 here, the output of this script:

// this is a Container
println(classof(FindObject(125)));

// this is a Node
println(classof(FindObject(4528)));

// this is a Container
try {
  println(classof(FindNodeObject(null, 125)));
} catch {
  println("This error should be displayed, since we are calling classoff(null)");
}

// this is a Node
println(classof(FindNodeObject(null, 4528)));



Is

NetObj
Node
This error should be displayed, since we are calling classoff(null)
Node

*** FINISHED ***


Node is just a sub-class of NetObj, so calling any attributes of the NetObj on a node-class object will of course work.
For reference: https://wiki.netxms.org/wiki/NXSL_Class_Reference.

I have also fixed the FindObject function documentation on the wiki to be more clear on what the current behavior is:
https://wiki.netxms.org/wiki/NXSL:FindObject

Please check in Server Manager (http://[ip/fqdn]:8080/manager/status) if the correct memory really is set.

You should see under JVM something like this:
JVM
Free memory: 423.20 MB Total memory: 495.37 MB Max memory: 1007.37 MB

Please also check "F:\Program\NetXMS\etc\nxagentd.conf.d" if there is some config there or not.