NetXMS Support Forum

Your syntax is wrong - you should use -> operator for accessing object properties (dot is string concatenation). Also, brackets denote capture group in regular expression, you should escape them with backslashes.


return $node->productName ~= "ePMP3000 \\(FCC\\)";


should work.

Best regards,
Victor

Hello!

We have updated repository with forked Zest version and it seems to break build of older versions. To fix it you should hard set versions of Zest plugins in product file. The following patch should fix it:

diff --git a/src/java/netxms-eclipse/Product/nxmc.product b/src/java/netxms-eclipse/Product/nxmc.product
index 2cdd05dee0..79a110983b 100644
--- a/src/java/netxms-eclipse/Product/nxmc.product
+++ b/src/java/netxms-eclipse/Product/nxmc.product
@@ -597,9 +597,9 @@ Copyright (c) 2003-2020 Raden Solutions
       <plugin id="org.eclipse.ui.workbench.texteditor.nl_pt_BR" fragment="true"/>
       <plugin id="org.eclipse.ui.workbench.texteditor.nl_ru" fragment="true"/>
       <plugin id="org.mozilla.javascript"/>
-      <plugin id="org.netxms.gef4.zest.core"/>
-      <plugin id="org.netxms.gef4.zest.jface"/>
-      <plugin id="org.netxms.gef4.zest.layouts"/>
+      <plugin id="org.netxms.gef4.zest.core" version="2.0.6"/>
+      <plugin id="org.netxms.gef4.zest.jface" version="2.0.6"/>
+      <plugin id="org.netxms.gef4.zest.layouts" version="2.0.6"/>
       <plugin id="org.netxms.ui.base"/>
       <plugin id="org.netxms.ui.eclipse.actionmanager"/>
       <plugin id="org.netxms.ui.eclipse.agentmanager"/>


Best regards,
Victor

What if you run full configuration poll on it manually? Also, do this node respond to ping or it is only accessible via SNMP?

Best regards,
Victor

You can encode such password with nxencpasswd tool. For example:


nxencpasswd dbuser dbpass#123


will produce string


MKGI20iIOABe/NdxPN/ZMjCyW8ng20jLMLJbyeDbSMs=


which you can use as value for DBPassword parameter.

Best regards,
Victor

Hi all!

NetXMS 3.8 patch release 3.8.193 is just published. It is must have update for Timescale DB users as it fixes critical compatibility issue with Timescale DB 2.x.
Full change log:

- Fixed Timescale DB 2.x compatibility issues
- New methods isDirectChild, isDirectParent, isChild, isParent in NXSL class "NetObj"
- New NXSL function GetCurrentTimeMs
- Fixed possible server crash when agent tunnel is closing
- Always use UTF-8 instead of current system character encoding for exported CSV files
- Fixed process handle leak in Windows agent when external parameter providers are used
- Westerstrand SNMP device driver can read device geolocation
- NXSL function PollerTrace works in autobind filter scripts and instance discovery filter scripts
- Improved diagnostic output for manually started polls
- Improved network map tooltip data update

Best regards,
Victor

For zoned environments probably the only way is to use filtering script that will check allowed ranges per zone. Mapping tables or custom attributes on zone objects can be used to store allowed or forbidden ranges.
But in general I think we need per zone address range filters, probably implemented as zone object properties.

Best regards,
Victor

Most likely server processes already queued discovery tasks. Restart of netxmsd should fix it.

Best regards,
Victor

Currently it's not possible. I just added new function for that - GetCurrentTimeMs(). It will be available in next patch release.

Best regards,
Victor

Quote from: Akira on March 02, 2021, 08:08:25 AM

Quote from: Victor Kirhenshtein on March 01, 2021, 06:55:21 PM
Ну значит он падает, а не виснет. Сможете прислать дампы?

сервис запущен был.
Там дамп 200мб, как передать?

Можно сюда залить: https://cloud.radensolutions.com/s/GAWHMA9ppyz78LF

Hi,

second issue (404 errors for certain parameters) are normal system activity - server requests various data from nodes, but not every node support all parameters, so 404 response is expected.

PDH error is a bit more strange. When collecting performance counter metadata, agent reads all available objects and counters for each object. Such error means that PDH API reports object, but on attempt to read counters for that object returns error that such object is not found. We will add actual object name to this error message in next patch release - it will help to debug this issue further.

Best regards,
Victor

Yes, it is working. Make sure that nxmc really picks up Java 11.

Best regards,
Victor

File nxmc.properties should be placed anywhere in class path. For Tomcat 9 good choice will be shared class path, by default it is $CATALINA_BASE/lib (unless redefined by the common.loader property in $CATALINA_BASE/conf/catalina.properties). You can find more details on Tomcat 9 class loader here: https://tomcat.apache.org/tomcat-9.0-doc/class-loader-howto.html.

Best regards,
Victor

Ну значит он падает, а не виснет. Сможете прислать дампы?

Rule number 5 - it has no condition, so it catches every event, and sends notification.

Best regards,
Victor

Most likely you have some sort of "catch all" rule that also triggered for those events without explicitly listing them (like "all events from object"). If you can show your full policy I can comment further.

Best regards,
Victor