NetXMS Support Forum

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

Hi all!

We just published another patch release for 4.0 which fixes two important issues:

NX-2210 (Network Service HTTP polling ports above 32767 generates incorrect Host header in HTTP request)
NX-2211 (Agent crash while processing request for System.ThreadCount)

Best regards,
Victor

Hi all!

We just published patch release for version 4.0 (4.0.2148). Changes since previous release:

- New attribute "lastCollectionTime" in NXSL class "DCI"
- Notification channel driver for Twilio
- Fixed server crash on receiving SNMP trap if configuration parameter SNMP.Traps.LogAll is set to true
- Fixed bug in automatic object binding
- Fixed bug in NXSL function FormatMetricPrefix
- Fixed bug in business service state calculation
- Fixed incorrect handling of manually set Y axis range on bar charts
- Fixed issues:
        NX-2153 (Add REST API endpoint for persistent storage)
        NX-2198 (Alternative data source for agent parameters Hardware.System.* on Linux)
        NX-2209 (cpuid.h is not supported on ARM macOS)

Best regards,
Victor

Hi, do you have core dump from crash? If not, could you run netxmsd under gdb until it crashes? If you can, make sure that you have installed the following packages:

netxms-server-dbg
netxms-dbdrv-mariadb-dbg

The run as following in terminal:

gdb netxmsd
On gdb prompt, enter
run -D1

When server crashes, you will get gdb prompt again. Enter command
bt

and share the output.

Best regards,
Victor

We just uploaded patched version of UI (version 4.0.2111).

Best regards,
Victor

Hi,

probably just ignore them, or set EPP filter to prevent generation alarms. Events will be generated only once for each DCI, so they should stop appearing when new templates will be applied to all old agents.

Best regards,
Victor

This actually looks like a bug. Can you provide configuration of your dashboard (you can export it into XML by right click on dashboard object and selecting "Export")?

Best regards,
Victor

Hi,

if you have DNS names correctly updated, then you can use DNS names of those devices for communications. NetXMS server will periodically (at configuration polls) check if IP address is the same. You can also force server to make those checks more often by changing configuration parameter Objects.Nodes.ResolveDNSToIPOnStatusPoll from "Never" to "Always" or "On failure".

If you have automatic network discovery then you can turn on parameter NetworkDiscovery.UseDNSNameForDiscoveredNodes - when set server will use DNS name instead of IP address for newly discovered nodes. You should have reverse DNS to be set up properly for this feature to work.

Best regards,
Victor

Could you enable SQL trace for some time (this will generate lot of records in log)? Then it will be possible to see all bindings for this query.

You can turn it on while server is running with the following commands in debug console:
debug sql on
debug db.query 9

and to turn back off:
debug sql off
debug db.query -1

Best regards,
Victor

Да, у нас с нескольких сторон есть такие запросы. Думаю сделаем в ближайшем будущем.

Hi,

yes, missing policy database error is related to SQLite issue. We will check today.

Best regards,
Victor

No, NPI files are no longer needed. Package manager deduces package type from file name, and you can adjust it during import if detection went wrong.

Best regards,
Victor

Hi all!

We finally published NetXMS version 4.0. There are lot of new features, changes and improvements, some are visible, some are under the hood. Unfortunately we didn't finish planned changes to UI, so new UI is available as preview alongside old one, and we plan to finalize it during following patch releases.

There are few changes that may cause compatibility issues when migrating from 3.x:

1. Incompatible attributes in NXSL class "DCI": "instance" now refers to instance value (as in {instance} macro), not instance name as before. Instance name can be accessed via attribute "instanceName".
2. Operators print and println in NXSL are now functions, so arguments should be enclosed in brackets as usual for function call.

Below is full change log:

- Two-factor authentication for users
- SMTP implemented as a notification channel and e-mail actions replaced by notification actions
- Added 'DefaultNotificationChannel.SMTP.Html' and 'DefaultNotificationChannel.SMTP.Text' server configuration parametes for default SMTP channel names used by internal functions
- Removed lock for user management view
- Strings "true" and "false" interpreted as boolean values when accessing custom attributes from NXSL
- Database manager can create database and database user before database schema initialization
- OPC UA subagent moved to core product
- Added option to manually create subnet
- Separately configurable timeouts for agent's external parameters and external command execution
- Zoning is enabled by default
- Value of any type can be used as boolean in NXSL
- NXSL operator "in" works for strings and hash maps
- Single-quoted strings in NXSL (without escape characters)
- Multiline string constants in NXSL
- Operators "print" and "println" in NXSL converted to functions
- New methods "contains" and "remove" for NXSL hash maps
- Improved string manipulation functions in NXSL
- Integer division operator in NXSL
- Multi-OID SNMP requests in NXSL
- Macros can be used in object comments
- New threshold type "absolute deviation"
- Added option for L2 network maps to create links using physical links
- Configurable HTTP request method and request data in web service definitions
- Polling intervals can be overridden on object level via custom attributes
- Implemented DCI search on container
- Improved Web API
- Improved SSH subagent
- Inherited object access rights visible in object properties in UI
- Correlated events can be processed in event processing policy
- Escalation level for responsible users
- Structured alarm filter in UI
- Log parser debug output only controlled by debug level for tag logwatch.parser (parser option "trace" is deprectated)
- Added support for multi-select fields in report execution forms
- Improved package deployment via agents
- New event template option "hide from event monitor"
- Reporting server uses XLSX format instead of XLS
- Fixed small isues in object custom attribute inheritance
- Fixed issues:
   NX-1 (New threshold type: absolute deviation)
   NX-251 (Service check for pop3s and smtps)
   NX-436 (Add an option to secure syslog server)
   NX-1354 (Object ACL editor should not allow empty list of users without "inherit access rights" checkbox)
   NX-1382 (NXSL '$dci->instance' has 'instance-name' value)
   NX-1452 (User filter for Process.Count parameter)
   NX-1468 (Status from network map objects is not propagated to map groups)
   NX-1487 (Grace period for automatic template removal)
   NX-1611 (Macro expansion in object comments)
   NX-1660 (Generate event on ICMP status poll failure)
   NX-1673 (DCI Performance tab - {instance-name} doesn't work)
   NX-1698 (SNMP query for printer status string is unreadable)
   NX-1766 (File transfer implementation issues)
   NX-1776 (Forbid deletion of events that are used in thresholds or policies)
   NX-1822 (DCI should stay disabled, if it stops getting discovered by instance discovery and gets discovered again)
   NX-1829 (Misleading error message, when trying to rename protected image in image library)
   NX-1838 (Files in file delivery policy should be exported as part of configuration export)
   NX-1859 (Implement two-factor authentication in NetXMS server)
   NX-1923 (Enforce unique event names)
   NX-1972 (Add extended version of System.Processes table having info on CPU and memory consumption per process)
   NX-2013 (Add ability to send audit log to syslog in UTF-8)
   NX-2025 (Add macro expansion in timer delay and snooze time fields in EPP action properties)
   NX-2062 (Add option to specify community string in CreateSNMPTransport)
   NX-2066 (Add more parameters to events created on server within Windows Event Log synchronization)
   NX-2068 (Rename column "check_responce" in table network_services to "check_response")
   NX-2069 (Collect hardware information about HDD/SSD and network cards on Linux)
   NX-2095 (Add option to access node hardware inventory information from NXSL)
   NX-2098 (New action type "Execute command on remote node via ssh")
   NX-2100 (Add "support level" or "escalation" value to Responsible persons)
   NX-2111 (Add ability to configure web service proxy in node properties)
   NX-2167 (Add context to SYS_SCRIPT_ERROR event)
   NX-2173 (File integrity monitoring)
   NX-2174 (Periodically check telegram API if it's operable)
   NX-2178 (Configurable encoding for SNMP)
   NX-2179 (Configurable encoding for syslog)
   NX-2184 (Notification channels SMTPS support)
   NX-2185 (Certificate pinning for agent tunnels)
   NX-2189 (Typo when interfaces are removed during polling)
   NX-2190 (Add NXSL function that will convert numeric value to human-readable form with multipliers)
   NX-2191 (Ignore node unreachable state when performing manual configuration poll)
   NX-2194 (Add option to access node software inventory information from NXSL)
   NX-2195 (DB Checker inefficiencies with IsDciExists)
   NX-2198 (Alternative data source for agent parameters Hardware.System.* on Linux)
   NX-2199 (Agent parameters to get certificate information from file)
   NX-2200 (Remove length limit on command in NXSL method Node::executeSSHCommand)
   NX-2204 (Agent not recognizing Windows 11)
   NX-2205 (Generate event if LDAP sync failed)
   NX-2207 (Implement System.OS metrics for Linux, AIX, FreeBSD and Solaris)
   NX-2208 (Zone UIN being reused)

Best regards,
Victor