NetXMS Support Forum

Can you actually share your powershell script (or some version of it with which gives same results).
Also, what's the version of powershell itself - it might make some difference.

I see you have two external metric providers configured. Does the problem still happen if you remove the second one?

Can you also check with Windows Task manager, if between this line
2024.08.14 16:18:01.182 *D* [procexec.2        ] ProcessExecutor::executeWithOutput(): process "CMD.EXE /C pwsh.exe -NoProfile C:\\NetXMS\\var\\test1.ps1" started (PID=2020)

and that line
2024.08.14 16:18:31.185 *D* [ext.provider      ] ExternalDataProvider::poll(): command "pwsh.exe -NoProfile C:\\NetXMS\\var\\test1.ps1" execution timeout (30000 milliseconds)

pwsh.exe -NoProfile C:\\NetXMS\\var\\test1.ps1
process is actually running, or it has already terminated? I'd try to add say 10 second delay inside test1.ps1, then it would be seen in Task Manager that this process starts and when it ends.

Can you please enable
DebugLevel = 7
in agent configuration file and set it to log to file
LogFile = /path/to/log/file

let it run until it finishes second call of the script and share the log (you can sent it to me as private message if needed)

Quote from: Spheron on August 13, 2024, 02:08:09 PMhaving here a similar problem with a Netgear GS728TPv3.

Any chances we can get remote access to your device for a few days? SNMP-only access is enough, it can be some test device not connected to real network

Make sure you've selected Legacy Authentication Method when installing MySQL as described in MySQL notes in this chapter: 
https://netxms.org/documentation/adminguide/installation.html#id14

On Initialize Database page in the installer "Create database and database user before initialization" should be checked, DBA login name should be "root" and DBA password is the password you entered when installing MySQL.

Event if this step fails, NetXMS software is fully installed, so you can connect to your MySQL DB with any client and issue queries to create user and database:

CREATE DATABASE netxms CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
CREATE USER 'netxms'@'localhost' IDENTIFIED BY 'PaSsWd';
GRANT ALL on netxms.* to 'netxms'@'localhost';

You may also need to adjust NetXMS configuration file to match these credentials, the file is here: C:\NetXMS\etc\netxmsd.conf 

The way this is implemented is that you need to have DCIs that do actual traffic information collection. In other options of these DCIs related interface object should be specified and interpretation, e.g. "Interface traffic - Outbound - bytes/sec" should be set.
When adding DCIs from context menu of interface(s), these parameters are set automatically. You can check, if these are set correctly by checking Overview tab of the interface - it should now have "Inbound utilization" and "Outbound utilization" lines.

Currently only Outbound utilization is taken, so a list should have these DCIs on both ends. Color schema is such, that link with 0% traffic is gray, but it should change it's color with traffic.

This is a new feature, so some improvements might be made to make it simpler/more understandable.

Right, this is always good practice to have DB backup prior to upgrade. 

In addition, you can also run 
nxdbmgr check
ideally two times - one prior to NetXMS upgrade and the other one after. First run fixed issues, if any, so upgrade runs in a clean way. Second time happens with newer version of nxdbmgr that may have new checks added. 

Normally reporting server is installed on the same system as netxms server itself. But theoretically yes, you can disable netxms server service and have only reporing service enabled. 

That's right, .nxms folder is for the "old" client, but since in v 4.x "new" client was introduced, it stores files in .nxmc4 folder

Seems to be too much requests, but could be legit, as NetXMS requests a lot of information via snmp.

If you are using unencrypted snmp communications, please capture network exchange dumps. Then we can see specific OIDs that are being requested.

If your server is on Linux, use this command to capture to file in wireshark format:
tcpdump -s 0 -w snmp-exchange.pcap host = DEVICE_IP

On Windows you can use Wireshark for that.

Different colors and time frame - that's definitely a bug, I've created an issue for that: https://track.radensolutions.com/issue/NX-2559 , you can subscribe to it to get notification when it's fixed.

Zooming - yes, it's currently absent, there are thoughts to make this a bit differently: https://track.radensolutions.com/issue/NX-2560

Historically there are two approaches to WIndows Event Log - Log Synchronization mentioned by Tatjana and Log File Monitoring. First one has the benefit that whole text of events is stored on the server. Second approach does not require to modify agent configuration file - configuration is uploaded via policy, events are generated by agent. Let me describe it in more details:

Under "Templates" create a new template. Third tab in the template - "Agent Policies". Create a new "Log Parser" policy, give it some name. In the policy click "Add file" and put
*Security
into File path field. This means that Windows security log will be parsed. Add a new rule. You can filter by Level, ID and Source as well as by log entry text ("Matching regular expression" field, it parses all lines of the entry as one long string). 

For testing you can use (.*) as the regex - it will capture whole message as parameter of the generated event - if you double-click an entry en event log, you'll see all the information.

I am not sure about correct event ID, but it seems that 4624 is capturing logon events, so regex .* and ID 4624 will capture these events. You need to specify an event in the rule.

Create event template, this defines what parameters are included into message field. E.g. the following in the message field:
User %<variable6> was successfully logged on (Event ID: %<eventId>, Severity: %<severity>, Network Address: %<variable19>)

Try netxms-agent-mariadb, it should be same as MySQL

We don't have a list in the documentation, just some chapters mention that specific subagents are needed, e.g. Network Service monitoring requires netsvc.
If you check list of available packages with dnf, you'll see them all:

root@localhost:~# dnf search netxms-*
Last metadata expiration check: 1:38:40 ago on Wed 31 Jul 2024 10:42:43 AM EEST.
=================================================================================================================================================== Name Matched: netxms-* ===================================================================================================================================================
netxms-agent.x86_64 : NetXMS agent and extensions (subagents)
netxms-agent-asterisk.x86_64 : Agent extension (subagent) for monitoring Asterisk
netxms-agent-asterisk-debuginfo.x86_64 : Debug information for package netxms-agent-asterisk
netxms-agent-debuginfo.x86_64 : Debug information for package netxms-agent
netxms-agent-java.x86_64 : Agent extension (subagent) for running java-based monitoring providers
netxms-agent-java-debuginfo.x86_64 : Debug information for package netxms-agent-java
netxms-agent-mariadb.x86_64 : Agent extension (subagent) for monitoring MySQL/MariaDB databases
netxms-agent-mariadb-debuginfo.x86_64 : Debug information for package netxms-agent-mariadb
netxms-agent-mqtt.x86_64 : Agent extension (subagents) for communicating wiht MQTT brokers
netxms-agent-mqtt-debuginfo.x86_64 : Debug information for package netxms-agent-mqtt
netxms-agent-oracle.x86_64 : Agent extension (subagent) for monitoring Oracle databases
netxms-agent-oracle-debuginfo.x86_64 : Debug information for package netxms-agent-oracle
netxms-agent-pgsql.x86_64 : Agent extension (subagent) for monitoring PostgreSQL databases
netxms-agent-pgsql-debuginfo.x86_64 : Debug information for package netxms-agent-pgsql
netxms-agent-vmgr.x86_64 : Agent extension (subagents) for monitoring virtualization platforms
netxms-agent-vmgr-debuginfo.x86_64 : Debug information for package netxms-agent-vmgr
netxms-base.x86_64 : Common NetXMS libraries and tools
netxms-base-debuginfo.x86_64 : Debug information for package netxms-base
netxms-client.x86_64 : Integration and diagnostics tools for the NetXMSX server.
netxms-client-debuginfo.x86_64 : Debug information for package netxms-client
netxms-dbdrv-mariadb.x86_64 : ...
netxms-dbdrv-mariadb-debuginfo.x86_64 : Debug information for package netxms-dbdrv-mariadb
netxms-dbdrv-odbc.x86_64 : Middleware for interfacing with any compatible database engine via ODBC
netxms-dbdrv-odbc-debuginfo.x86_64 : Debug information for package netxms-dbdrv-odbc
netxms-dbdrv-oracle.x86_64 : Middleware for interfacing with Oracle database engine
netxms-dbdrv-oracle-debuginfo.x86_64 : Debug information for package netxms-dbdrv-oracle
netxms-dbdrv-pgsql.x86_64 : Middleware for interfacing with PostgreSQL database engine
netxms-dbdrv-pgsql-debuginfo.x86_64 : Debug information for package netxms-dbdrv-pgsql
netxms-dbdrv-sqlite3.x86_64 : Middleware for interfacing with SQLite3 database engine
netxms-dbdrv-sqlite3-debuginfo.x86_64 : Debug information for package netxms-dbdrv-sqlite3
netxms-debuginfo.x86_64 : Debug information for package netxms
netxms-debugsource.x86_64 : Debug sources for package netxms
netxms-java-base.x86_64 : Common java libraries used by the NetXMS components
netxms-java-base-debuginfo.x86_64 : Debug information for package netxms-java-base
netxms-reporting.x86_64 : JasperReports-based reporting server integrated into NetXMS
netxms-server.x86_64 : Monitoring server core
netxms-server-debuginfo.x86_64 : Debug information for package netxms-server

netxms-agent-* are different subagents, netxms-dbdrv-* drivers for various databases (used both by server for it's database and by agent to perform queries to databases, netxms-base has common things needed both for server and agent, netxms-reporting is the reporting engine, that's basically it

Hi,

That's correct, 5.0.6 is the newest version of NetXMS.
The latest postges on Fedora 40 is 16.3 (which should get installed when installing postgresql-server), please try with that version.

Did you use regular Postgres or Timescale when initializing the DB?


P.S. You can use
journalctl -u netxms-server.service
to get log of just NetXMS process. Or, alternatively, you can configure logging to file in /etc/netxmsd.conf