NetXMS Support Forum

It will be there, just not moved from old UI yet.

Best regards,
Victor

Hi,

there are two independent polls that produce those two events. One is status poll, that checks node connectivity using agent, SNMP, and finally ICMP if neither SNMP agent nor NetXMS agent are responding. This poll can generate events SYS_SNMP_UNREACHABLE, SYS_AGENT_UNREACHABLE, SYS_NODE_UNREACHABLE, and SYS_NODE_DOWN. Difference between SYS_NODE_UNREACHABLE and SYS_NODE_DOWN is that "unreachable" generated when server can detect network failure between itself and target node.
Another poll is ICMP poll, it was added in version 4.0. It's main use is to do regular ICMP pings and collect response time and packet loss statistic. In addition, it will generate event SYS_ICMP_UNREACHABLE when node is not responding to ICMP. If that happen after SYS_NODE_DOWN then ICMP unreachable event will be correlated to node down event, but because those two types of poll run asynchronously it is possible that node became actually unreachable after last status poll run and before next ICMP poll run, thus generating ICMP unreachable event that cannot be correlated to node down event.
You can effectively hide those ICMP unreachable events by disabling or removing rules that generate alarms from them, and unchecking "write to event log" option in event template configuration for SYS_ICMP_UNREACHABLE and SYS_ICMP_OK.

Best regards,
Victor

Hi,

what server version you are using? Also, try to set debug level to 5 on server and check server log for lines starting with NXSL: F_AgentExecuteAction.

Best regards,
Victor

Hi,

what exact server version you are using? There was a bug in auto-apply functionality, but it should be fixed in latest patch release.

Best regards,
Victor

Hi,

if nodes already classified into one of two containers, all you need to do is to change relevant rules in event processing policy to only trigger for nodes in "critical" container (just add that container as source filter in the rule).

Best regards,
Victor

Hi,

should be safe.

Best regards,
Victor

Hi,

General support for Ubuntu 16 ended in 2021, so we decide to exclude it from general release. Packages may still be made available if there will be request from customers with valid support contract (but we didn't get any yet).

Best regards,
Victor

Quote from: Watchman on February 22, 2022, 05:15:21 PM
Hi!

I'm facing some problems with package deployment.

For example: msi-Package "A" is successfully deployed to most nodes but for some the message "file transfer failed" appears.
msi-Package "B,C,D" are successfully deployed to nodes where Package "A" fails.

Another case: Message "timeout" appears - in fact package has been successfully deployed (not really a problem)

Best regards.

Hi,

could you provide logs from problematic agents (preferably on high debug level, 5 or 6)?

Best regards,
Victor

Quote from: lweidig on February 22, 2022, 06:54:06 PM
The Ubuntu package for the agent does not include mysql.nsm subagent or any of the others, though only interested in mysql at this point.  I also installed the netxms-dbdrv-mariadb package (as the mysql package not available for Ubuntu 20) and it did not provide that either.

That's packaging issue, subagent itself can use mariadb driver, but seems that it is packaged only if mysql driver is selected. We will fix it for next release.

Best regards,
Victor

Quote from: Spheron on February 22, 2022, 06:10:37 PM

Hello @all,

i fenced a problem too... If i select more then 16x DCI and choose Line Chart from the right click menu, the chart is not display correct. This bug i have in dashboards, too.

Bug is present since V4.0.2157.

Greetings
Marco

Hi,

actually charts does not support more than 16 items, and it was like this since very old versions.

Best regards,
Victor

Hi all!

We just published another patch release for 4.0 that fixes some newly found issues:

NX-2212 (Agent segmentation fault when accessing table Hardware.NetworkAdapters)
NX-2213 (Set event parameter from NXSL by index)

It also adds new parameter Oracle.Cursors.MaxPerSession to Oracle subagent.

Best regards,
Victor

Hi,

no, not cross compile - just if you have a choice of platform then Linux is easier to work with.

Best regards,
Victor

Hi,

most likely there was short period of time when system clock was set at 24.08.2033. Now server is not scheduling those DCIs to poll because current time is less than last value timestamp. Try to stop the server and run nxdbmgr check - it should delete incorrect records thus allowing normal data collection scheduling.

Best regards,
Victor

Hi,

you need Visual Studio 2017, and some precompiled 3rd party libraries: OpenSSL, libssh, libmosquitto, libcurl, database client libraries. You should add those libraries to include path and library path of Visual Studio. You will also need flex, bison, and perl in your path.
In general, setting up Windows build environment is much more complicated than Linux one, so if you have a choice, I'd really recommend going with Linux.

Best regards,
Victor

Hi,

you can set custom attribute on a node to current time from first event, and for the second event use script macro to read custom attribute value and return the difference with current time. For example:

1. Create script in script library called SetSignalLossTime:

$node->setCustomAttribute(".signalLossTime", time());


2. Create script in script library called GetSignalLossDuration:

t = $node->getCustomAttribute(".signalLossTime");
return (t != null) ? time() - t : 0;


3. Create server action of type script that will execute script SetSignalLossTime.

4. Add action from #3 to EPP rule where you generate alarm for signal loss.

5. In the message template for recovery event add %[GetSignalLossDuration] to insert duration of signal loss.

Best regards,
Victor