Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Victor Kirhenshtein

#46
Announcements / NetXMS 4.5 released
December 24, 2023, 06:12:30 PM
NetXMS version 4.5.0 is just published. It is intermediate release on a way to version 5.0, and it includes improvements and fixes that are too big to be considered for patch release but important enough to be published before 5.0 is ready.

Full change list since version 4.4.5:

- XPath can be used for querying XML-based web services
- New NXSL operation "?." (safe dereference)
- New method "join" in NXSL arrays
- Server-side custom attributes (not visible by clients)
- Additional argument in NXSL method createSNMPTransport to control if it should fail when node is marked as unreachable via SNMP
- Updated drivers for Eltex and TP-Link switches
- Added agent metric Agent.LocalDatabase.FileSize
- Fixed internal metrics PollTime.\*
- Fixed issues:
   - NX-1409 (Implement separate access right for editing object comments)
   - NX-2275 (Option for ignoring interfaces in NOT PRESENT state)
   - NX-2412 (Separate access right for editing agent configuration file)
   - NX-2440 (Wildcard imports in NXSL)
   - NX-2485 (XPath support in web service queries)
   - NX-2487 (Any changes to object from UI or via Java API wipe out responsible users list)
#47
General Support / Re: NetXMS WebUI 4.2.395 not starting
December 19, 2023, 09:59:07 PM
Could you please explain where you configuring it and what exception are you getting? I have little experience with Tomcat, but I can check if I can adapt packages to it if I'll be able to setup test environment.

Best regards,
Victor
#48
General Support / Re: JVM Monitoring
December 19, 2023, 09:51:14 PM
I have found the problem with classpath setting in JMX plugin. Try to replace jmx.jar on your system with this version: https://cloud.radensolutions.com/s/WDCCtmPKHXGZwyo.
If you installed agent on Linux from packages it will be inside /usr/lib/netxms/java.

Best regards,
Victor
#49
Wildcard import implemented in current development branch and will be included in release 5.0 (and 4.5 if it will be publicly released).

Best regards,
Victor
#50
Announcements / NetXMS 4.4 patch release 5
December 08, 2023, 09:11:42 AM
NetXMS version 4.4.5 is just released. It fixes two critical issues: server crash on polling TP-Link devices (bug that was introduced in 4.4.4), and severe performance degradation when monitoring multiple (thousands) SNMP devices via single proxy.

Full change log since previous patch release:

-  Improved SNMP proxy performance under heavy load
-  Added limit on number of nested NXSL VMs (to prevent accidential infinite loop of script execution)
-  Fixed server crash on polling TP-Link switches
-  Fixed bug in dashboard element "status indicator"
-  Fixed bug in status map view
-  Fixed bug in database manager check function
-  Fixed "Failed to register resource" error in web UI
-  Fixed database import/migration to TimescaleDB
-  Java components switched to logback 1.3.13 (fixes CVE-2023-6378)
Fixed issues:
-  NX-2465 (List of saved queries in Tools->Find Object is not updated when query list is altered in Configuration)
-  NX-2479 (Misleading error messages when loading properties for root objects)
#51
Should be as simple as running
nxdbmgr.exe init
from command line. It may ask additional information and will show result in console.

Best regards,
Victor
#52
General Support / Re: NetXMS Grafana Plugin
December 04, 2023, 03:57:14 PM
Rewriting Grafana plugin is in our pipeline, I hope we can make it in January or February.

Best regards,
Victor
#53
We made a fix recently (in 4.4.x) for stalled client sessions from web API - that may fix this issue too.

Best regards,
Victor
#54
General Support / Re: JVM Monitoring
December 04, 2023, 03:38:37 PM
Hi,

this (and other) metrics requires JMX server name as an argument. You define JMX servers in agent configuration file (see https://www.netxms.org/documentation/adminguide/jvm-monitoring.html#configuration) Unfortunately, there is no agent list to return all configured JMX servers on that particular agent (we can add one in next release). So for now you cannot use instance discovery if you have multiple JMX servers monitored by one agent.

Best regards,
Victor
#55
Hi!

Try to use server_name\instance_name in DBServer. Also you can try IP address instead of DNS name.
Check that TCP/IP and named pipes enabled for Native Client.

Another alternative is to create ODBC DSN and switch to odbc driver (use DBDriver=odbc instead of DBDriver=mssql). In that scenario you should use ODBC DSN as value for DBServer.

Best regards,
Victor

#56
Announcements / NetXMS 4.4 patch release 4
November 28, 2023, 09:43:29 PM
NetXMS version 4.4.4 is just published. Changes since version 4.4.3:

-  New methods in NXSL class "InetAddress": contains, equals, inRange, sameSubnet
-  Constructor for NXSL class "InetAddress" accepts mask length as second argument
-  Fixed incorrect ICMP polling if ICMP proxy set on node level
-  Improved topology discovery on TP-Link devices
-  Improved driver for DLink devices
-  Added driver for TP-Link devices
-  Added driver for Eltex devices
-  Added driver for Q-tech devices
-  nxencpasswd can read password from terminal
-  GUI clients built with patched version of simple-xml (fixes CVE-2017-1000190)
-  Fixed deadlock after login in legacy web UI

Fixed issues:
-  NX-2431 (Implement agent list Net.IP.RoutingTable for AIX)
-  NX-2478 (Named function parameters does not work for entry points)
#57
Announcements / NetXMS 4.4 patch release 3
November 02, 2023, 04:45:19 PM
NetXMS version 4.4.3 is just published. Changes since previous patch release:

-  Package deployment can be scheduled
-  Server-side macro expansion in package deployment command
-  Use compact JSON format when saving events to database
-  Improved event processing performance
-  Improved NXSL function "random"
-  New event processing macros %d (DCI description), %D (DCI comments), %L (object alias), and %C (object comments)
-  Added driver for FortiGate devices
-  Fixed server crash during execution of delayed EPP action
-  Fixed server crash when processing interfaces with 8 byte MAC address
-  Fixed session disconnect handling in new management client application
-  Fixed bug in physical disk information reading on Windows
-  Fixed bug in SSH key store
-  Improved debug logging
-  Minor fixes and improvements in new management client application
-  Fixed issues:
   -  NX-1063 (Interface icon is incorrect)
   -  NX-2224 (Command history in nxadm)
   -  NX-2446 (Increase timeout for agent tunnel binding)
   -  NX-2463 (Add metric to measure execution time of background queries in dbquery subagent)
   -  NX-2467 (Allow to execute same action multiple times in one EPP rule)
   -  NX-2468 (NetworkService.Status SMTP call to curl_easy_perform failed (56: Command failed: 502))
   -  NX-2469 (Empty "Parameters" line should be interpreted as no arguments in Execute Script)
   -  NX-2471 (Add agent list and table to list physical disks)
   -  NX-2475 (netsvc: ServiceCheck.SMTP() uses VRFY command, which is disabled on most servers)
#58
General Support / Re: TCPProxy -
October 16, 2023, 10:58:21 AM
Hi!

You should be able to use all the % macros in object tools (same macros as in event processing), so you can use custom attribute to define TCP port for example.

Currently there is no control on local port number - system allocates random port, typically from an ephemeral port range. It should not be a problem for desktop client, as this port is used only on loopback interface. FOr web client it could be an issue though, if you use web connect object tool from web client.

Best regards,
Victor
#59
General Support / Re: NetXMS 4.4.1 server failed
September 05, 2023, 06:09:47 PM
This looks like a bug in the server. Please try upgrading to 4.4.2, if this will not help, please try to run netxmsd under debugger and provide stack trace after crash.

Best regards,
Victor
#60
General Support / Re: Teltonika driver, node name
September 05, 2023, 06:08:32 PM
There is no such option in the driver. However, it is possible to use configuration poll hook to test if node name is "name" and driver is "TELTONIKA", and rename it as desired. Sample script that does this and sets node name to product name:

if ($node->name == 'name' and $node->driver == 'TELTONIKA')
{
   $node->rename($node->productName);
}

Best regards,
Victor