NetXMS Support Forum

It looks like pipes are not closed ater command execution (maybe if certain conditions are met). We will investigate it further.

Best regards,
Victor

Hi all!

We just published NetXMS server version 3.7.145. It fixes single bug in interface and subnet hook scripts processing. Only server is affected.

Best regards,
Victor

Hi,

NetXMS version 3.7.144 is just published. This is patch release that provide few fixes and improvements. Only server and UI components are affected. Full change log:

- Target for event processing policy remote action can be given as node object ID
- Added agent parameters Agent.TCPProxy.IsEnabled and Agent.TCPProxy.ConnectionRequests
- Fixed bug in agent action execution from event processing policy
- Fixed incorrect boolean values handling in NXSL
- Fixed bug in "Find switch port" tool
- Fixed server crash when connection to agent is slow or unstable

Best regards,
Victor

Also, please enable debug level 4 for tag obj.poll.node and show log file during discovery (there should be lines started with text AcceptNewNode).

Best regards,
Victor

Hi,

you can develop custom notification channel driver or order one from us. I didn't check their APIs but likely can also use command actions to call their HTTP API via curl or something similar.

Best regards,
Victor

Hi,

we have TOTP authentication planned, should be added in one of next releases.

Best regards,
Victor

Quote from: Pavel on December 08, 2020, 05:37:05 PM
Доброго дня.
Подскажите, как наиболее правильно сделать такую, в общем-то простую вещь:
Когда сервер запустился - на почту отправляется письмо с текстом "сервер был запущен в такое-то время"

Можно обрабатывать событие SYS_SERVER_STARTED и отсылать почту. При помощи макросов можно добавить текущее время.

Hi all!

New patch release for NetXMS 3.7 (build 3.7.130) is just published. Changes since previous patch release:

- Per node SSH port configuration
- New user properties "email" and "phone number"
- Fixed broken reporting server connector
- Fixed issues:
        NX-1081 (Some devices are not detected correctly by CATALYST-GENERIC driver)
        NX-1663 (NXSL function GetDCIValue should read value from database if cache is not populated yet)
        NX-1965 (Inconsistencies in address range add/edit dialog)

Best regards,
Victor

At least one Nexus user reported is as fixed, so probably yes (we were unable to reproduce it locally).

Best regards,
Victor

Hello!

Probably easiest way is to create two rules in event processing policy, one for critical nodes and one for everything else, and set different severity to generated alarms. See attached screenshot for an example.

Best regards,
Victor

It's strange - there are no errors on either side, server reports normal connection closure:

2020.12.16 16:35:57.592 *D* [client.session.0   ] readSocket: connection closed

Timestamps are also quite old and not in sync between server and client - do you have correct time on server and client? If yes, are those logs latest for version 3.7? Also, are they in same time zone?

Best regards,
Victor

Hi,

you can change format string for them. It is basically Java format string with one addition - format %*s will scale value automatically and display it as k, M, G, etc. So for traffic counters you can use format string

%*sbps

It will produce something like 1.37 Mbps for original value like 1370024.

Best regards,
Victor

Preferably you should use


not $node->isPrinter

or

!$node->isPrinter


although your form will work too, because isPrinter will contain boolean value TRUE or FALSE, and if it is false then isPrinter != TRUE will produce expected result.

Best regards,
Victor

So it is deleted as duplicate:

2021.01.11 07:59:49.527 *D* [event.proc         ] EVENT SYS_DUPLICATE_NODE_DELETED [100] at {0} (ID:30074352 F:0x0001 S:1 TAGS:"") FROM NetXMS Server: Duplicate node Haas HP DL380 Gen9 (iLO) is deleted (Primary IP address 10.59.204.205 of node Haas VMWareHostB [118318] found on interface HP Ethernet 1Gb 4-port 331T Adapter of node Haas HP DL380 Gen9 (iLO) [135819])

What is node "Haas VMWareHostB" and do it really have same IP address?

Best regards,
Victor

It is not possible to configure server to use only SNMP sysName for resolving node name. However, you can synchronize node name with SNMP sysName by adding the following code to configuration poll hook script:


if (($node != null) && $node->isSNMP && ($node->name != $node->snmpSysName))
{
$node->rename($node->snmpSysName);
}


It will update node name according to SNMP sysName on each configuration poll.

Best regards,
Victor