NetXMS Support Forum

Currently the bet option to find problems in credentials is to use virsh tool. Something like this:
virsh -c esx: //root@vcenter. mydomain.local/?no_verify=1 list

This tool will give more information about the problem that occurred wile connection.

Hi,

You can send request to [email protected]

Looks like debug symbols are not installed on your system so core dump does not contain information.
Can you please install netxms-server-dbg and attach core dump again.

Also can you please provide result of "SELECT id,passive_elements FROM racks" query in NetXMS database?

This bug is present in both 3.0 and current 3.1. It will be fixed in next patch release.

You can set it in server configuration - then it will be the default behaviour of the whole system.
It was done as it was assumed that either node has connected and have all DCI's or it has no connection, so that users do not need to make any manual actions if instance gone.

Issue created: https://track.radensolutions.com/issue/NX-1727

Created issue: https://track.radensolutions.com/issue/NX-1726

There is no option to make instance discovered DCIs only user deletable, but you can set instance retention mode to custom and define how many days missing instances should be kept.

Created issue: https://track.radensolutions.com/issue/NX-1725

It should be in 3.1, but we recently found that it is missing for Windows build. New patch release for Windows build will be on Monday.

It's similar to object query dashboard element: NXSL script is executed for every node in the system and if script return true - iti will be included in the list.

Some examples:
1:
haveAlarms = { return $node->alarms->size > 0; }
type == NODE and haveAlarms

2:
type == NODE and name match "^EPE.*"

3:
true

Last will return all objects

Hi,

It is just a warning, that means that node does not return anything on next oids:
.1.3.6.1.2.1.17.1.4.1.2
.1.3.6.1.2.1.17.7.1.2.2.1.2
.1.3.6.1.2.1.17.4.3.1.1

It might be normal situation.

Hi,

I have updated documentation: https://www.netxms.org/documentation/adminguide/event-processing.html#drivers

All roles are managed inside the NetXMS, LDAP is used onlu to log in. You can create required groups inside the NetXMS or use groups that are imported from LDAP and just assign required access rights to those groups, you can add groups inside the groups. If your LDAP structure does not change a lot you can use imported groups, but I personally create group with correct rights just in case if in LDAP group will be removed all rights will not be lost. I add LDAP imported groups in to the manually created groups.

We use object class to verify if it is user or group. Your user has classes classes: top,vasco-DPToken, but does not have user or group class(that are defined in your config). It looks like you can use vasco-DPApplication class as a user class. And you should check what class is group class the same way it was done for users.