NetXMS Support Forum

Update: we have found bug in alarm termination code, in upcoming release 2.2.14 this issue will be fixed.

Best regards,
Victor

Hi,

you can use Process.CPUTime to monitor CPU usage by specific process. Process.CPUTime returns cumulative counter in milliseconds of processor time spent by given process. You can use transformation as following to convert it to percentage:

1. Select delta calculation type "average delta per second".
2. Use the following transformation script:

return $1 / 10;

Best regards,
Victor

Hi,

in the autobind script you can access node's parents and check if any of them are MainServer or routers. There should be examples of enumerating parent objects on forum or wiki.

Best regards,
Victor

Hi,

Threshold table has reference to DCI table (items) via item_id column which in turn has reference to owning node (via node_id column).

Best regards,
Victor

From the server side it looks like agent did not provide certificate:

SetupTunnel(<public ip here>): Agent certificate not provided

Can you check that agent certificate actually exist on machine with agent? What operating system agent is running on? What versions you are using?

Best regards,
Victor

Hi!

Do you mean table DCI in NetXMS or SQL database table?

Best regards,
Victor

Hi,

this is most likely related to relatively large total number of active alarms. We will investigate this further.

Best regards,
Victor

Hi,

server checks OID .1.0.8802.1.1.2.1.3.2.0 (lldpLocChassisId) as test for LLDP support on device. Did your device returns anything under .1.0.8802.1.1.2.1.3 (lldpLocalSystemData)?

Best regards,
Victor

Hi,

most likely you had user database view open when did logout. Console remembers opened views and try to reopen them at login. Because current user does not have access rights to user database, it gets this error. Just close user database view of it is open and on next login there will be no error.

Best regards,
Victor

I've updated web site version as well. Will keep it updated during new releases.

Best regards,
Victor

Hi all!

NetXMS version 2.2.13 is out! Changes since previous release:

- TimescaleDB supported as backend database
- Added option to show SELECT output in nxdbmgr batch
- New attribute "parameterNames" in NXSL class "Event"
- New attribute "instanceData" in NXSL class "DCI"
- Added option to play alarm notifiacation sound only for active dashboard
- Required object access is "read" for all forced polls except full configuration poll which requires "modify" access
- Improved server startup and shutdown time
- Added option to save network map as image file
- New nxmc command line options -take-map-snapshot and -exit-after-open
- Fixed issues:
        NX-241 ("nxdbmgr batch" should support stdin)
        NX-887 (Additional variables in threshold script)
        NX-1388 (Event correlation route should start at proxy)
        NX-1536 (No output from forced status poll without "modify" object access right)
        NX-1552 (NXSL function to check for EPP timer existence)
        NX-1558 (Add ability to change node's comment from script)
        NX-1561 (Unexpected SYS_SNMP_DOWN events after SNMP proxy node restart)
        NX-1567 (EPP selection gets stuck)
        NX-1569 (Agent crash on 32 bit Windows 10)
        NX-1571 (Option to automatically terminate resolved alarms after timeout)

Best regards,
Victor

Hi,

try to delete them from database (can do that with query DELETE FROM scheduled_tasks WHERE taskid='Execute.Action';)

Best regards,
Victor

Hi,

please make sure that you have debug level 6 for tag agent.tunnel on server side and provide debug output for tunnel establishing.

Best regards,
Victor

Hi,

you can also create symbolic link named "jre" within "nxmc" directory pointing to JRE 8 - nxmc will pick up that JRE then.

Best regards,
Victor

Hi,

this is a bug in delayed action execution. As temporary workaround you can find and delete in database scheduled tasks of type "Execute.Action". You can find them using the following query:

SELECT * FROM scheduled_tasks WHERE taskid='Execute.Action';

We will provide fix soon.

Best regards,
Victor