NetXMS Support Forum

Hi,

the ticket was a bit lost in the development queue. Do you still have these devices, as we'd need some additional information from them.

Add
DebugLevel = 6
in agent's config and restart the agent. They try running configuration poll for that node. Agent's log should have information from which IP it is getting the connection - it's probably some address that you don't have in MasterServers line.

The other option is to configure tunnel connection - this requires some effort to create certificates for the server, but then connection will be established from agent to the server (https://netxms.org/documentation/adminguide/server-management.html#server-configuration-for-agent-to-server-connection-tunnel-connection)

I've created https://track.radensolutions.com/issue/NX-2872 for this

Is this still with SQLite?

Is it still the same in 5.2.7?

use Package_filter;

просто делает функции из библиотеки Package_filter доступными в текущем скрипте, но не вызывает ни одну из этих функций.
Можно в фильтре в EPP сделать так:

return Package_filter::main();

Ну или можно вообще весь код поместить в фильтр в EPP.

From another thread is seems that you've installed with SQLite. This could be the reason for server locking. I'd recommend to migrate to MySQL, MSSQL or Postgres (I personally prefer the last option, but it's just whatever you are comfortable with).

One you've configured parameters for the new DB in netxmsd.conf, and ran "nxdbmgr init" to initialize new databases's tables, you can use

nxdbmgr import <path-to-your-sqlite-db>

to migrate your exising sqlite database into the new one.

Yes, messages about
Thread "Syncer Thread" does not respond to watchdog thread
Thread "Recurrent scheduler" does not respond to watchdog thread
mean that something is not good with the server process (netxmsd).

First thing to check memory consumption by netxmsd, may be it goes up and system starts swapping.

What are the specs of the machine? What DB do you use? Is the DB on the same machine?

Yes, we will fix that in a future version.

Also note that SQLite is for testing only as it may not handle multiple parallel queries well. But is should be fine for a few tenths of nodes.

Да, таки в разные документы, у нас тут инфраструктура в процессе переезда.
Вот в этом коммите видно то что должно появиться в доке:
https://github.com/netxms/netxms-doc/commit/d5dc8c519edabffab11ed39965e617e597184e1f

In case of SQLite database login and password is not used. There is no need to check "Create database and database user before initialization". Just fill in "Path to database file", folders in that path should exist after installer finishes extracting files, so C:\NetXMS\server.db should be fine. NetXMS will create the database automatically.

And you don't need to run installed again, you can just put this into netxmsd.conf:

DBDriver=sqlite.ddr
DBName=C:\NetXMS\server.db

And run
nxdbmgr init
this should initialize the database.

For APs that work with a controller the process is that controller node is added to a wireless domain. Then all APs that are found on that controller should appear under that wireless domain.

Current situation is the following:

Ubiquity - only airMAX stand-alone devices are supported, these just appear as nodes.

Ruckus - there's a prototype driver which gets information from controller via mqtt, but we would be interested in development of SNMP driver.

Meraki - no support.

It looks like, in your case, new drivers would need to be developed to obtain more monitoring information. Would you be interested in a quote? We can prioritize this work within our custom development services, and it would take roughly two days. If you're interested, please send a note to [email protected]

In 5.2.7 Windows client F9 and Shift+F9 work for me for these.

Yes, shortcuts were reworked (and something still may not work). F2 is typically a "rename", so that's what it now does in object tree and all executions (script, object query and log) are on F9

Вот тут описано, есть как single value метрика, так и листы
https://netxms.org/documentation/adminguide/appendix.html#list-of-supported-metrics

Agent has a copy of unzip that gets installed into C:\NetXMS\bin and we can add this to agent's config

[ENV]
PATH=%PATH%;C:\NetXMS\bin

so that agent would be able to run this unzip binary, but then there's another issue as agent puts parameters for unzip in single quotes and unzip does not like that.

I've created a ticket for all this - https://track.radensolutions.com/issue/NX-2862.

Currently you can make a self-extracting binary and ship is as executable package. Or may be you can just put the .zip file and set it as executable and then in Command field you can put the actual unzip command, file location will be in ${file} macro.