NetXMS Support Forum

Hi,

it seems that you still have older server version then your nxdbmgr. Try to download source package again and compile everything again.

Best regards,
Victor

I mean a bit different thing. Try to do the following:

1. Create script in script library that will calculate status as you need it.
2. Create script source DCI, select your script as source, check "use for status calculation" option.
3. Don't forget to remove "use for status calculation" option from internal status DCI.

Best regards,
Victor

P.S. also, you should use address 0.0.0.0 to create node without IP address.

Hi,

both are implemented and will be included in 2.0-RC1 release.

Best regards,
Victor

Hi,

condition object is limited to have only two possible statuses. However, you can create node object without IP address, then create script DCI on it that will return status as a number from 0 (normal) to 4 (critical) and mark this DCI as "status DCI". You'll have node with status based only on value provided by your script.

Best regards,
Victor

Hi,

if you delete /opt/netxms completely then it should not be an issue. Still it looks like older library somewhere. Can you please check if there are libnetxms.so.1 left somewhere?

Best regards,
Victor

Hi,

it seems to be some strange mix of different library versions (*.so.1 and *.so.2). Try to delete all libraries from /opt/netxms/lib, run make clean and then make and make install again.

Best regards,
Victor

Hi,

it's a bug in console. I'll fix in till next release.

Best regards,
Victor

Hi,

currently it's not possible to change column order. You can "hide" column by resizing it to zero - console should remember column width settings.

Best regards,
Victor

When you run configure it will create config.log in same directory. Yes, I need it from M5.

Best regards,
Victor

There is issue after upgrade with incorrectly configured agent cache mode. Check that server's configuration parameter DefaultAgentCacheMode set to 2, and restart server (you may need to restart server even if it is set to 2).

Best regards,
Victor

Hi,

templates may be configured not override "disabled" flag on node DCIs. This is done to allow to disable unsupported/unwanted items on some nodes and not re-disable them after each template change. You can turn this off by setting ApplyDCIFromTemplateToDisabledDCI to 1.

Best regards,
Victor

Hi,

it could be like this:


if ($object->type == 1)
   return true;  // allow all subnets

parents = GetObjectParents($object);
//if (parents == null) return false;
foreach(p : parents)
{
   if ((p->type == 5) && (p->name == "containerA" || p->name == "ContainerB")) return true;
}
return false;


You can also add additional contraints on subnet names as usual using $object->name.

Best regards,
Victor

Line like this:


table = AgentReadTable($node, "System.Processes");


will read agent table (System.Processes in this example) into variable. It will be object variable of class Table. Then you can walk through table using it's methods. For example, to read value of column "NAME" in first row you can use the following code:


colIndex = table->getColumnIndex("NAME");
value = table->get(0, colIndex);


You can iterate through table using rowCount attribute as stop indicator:


for(row = 0; row < table->rowCount; row++)
{
   value = table->get(row, colIndex);
}


Best regards,
Victor

P.S. If you meant transformation script of a table DCI, then you don't need to read table - variable $1 will hold table object.

Just fixed it. Fix will be included in 2.0-RC1.

Best regards,
Victor

I probably understand it - nodes on L3 map re connected via subnet objects, not directly - and you filtered out subnet objects. You should change your filter to allow subnets or add relevant subnet objects to your container.

Best regards,
Victor