NetXMS Support Forum

Hi,

DataCollectionObject is a base class for DataCollectionItem and DataCollectionTable. You should create new DataCollectionItem object and pass it to createItem. Pass 0 is ID for new DCI.

Best regards,
Victor

Hi,

could you please run netxmsd under debugger and post a backtrace (https://wiki.netxms.org/wiki/Running_NetXMS_under_debugger)?

Best regards,
Victor

Hi,

it's strange that 0.0.0.0 is not working - it did on my system. Are you sure that after you set system IP server uses tunnel istead of direct connection? Also, in 2.1-RC1 that just released we have added tunnel manager in the GUI, so you can see active tunnels and bind/unbind them from UI.

Best regards,
Victor

Hi all!

NetXMS version 2.1-RC1 is released. It is release candidate, and if there will be no big issues, next release will be officially declared stable.

Changes since previous release:

- External tables in agent
- Script source for table DCIs
- Driver for IgniteNet devices
- Network device database (allows some device specific information to be provided without drivers)
- Server certificate's key can be stored in separate file
- Multiple CA certificates can be specified in server configuration file
- Number of samples can be configured for table thresholds
- Null value can be used as "no change" option in auto bind scripts
- Grafana integration
- Management console:
        - Node's zone name shown in alarm browser and object overview when zoning is enabled
        - Sorting option in table based charts on dashboards (to implement "Top N" style charts)
        - Full text object search
        - Agent tunnel manager view
- Fixed issues: NX-386, NX-1127, NX-1128, NX-1210, NX-1211, NX-1222, NX-1231, NX-1239, NX-1240, NX-1242

Best regards,
Victor

Похоже на configuration poll. Перепроверю логику работы - в теории сначала должна пробоваться текущая версия протокола.

Добрый день!

Пакет выглядит нормально. Сама станция заведена в NetXMS? Если да, то адрес правильный?

 А можно посмотреть исходники проблемных скриптов?

Hi,

should be fixed by now. Fix will be included in 2.1-RC1 release.

Best regards,
Victor

Hi,

environment variables is not needed, you need only libpq-fe.h in include path, and libpq.so in library path. You can specify path to your PostgreSQL installation in --with-pgsql configuration option, like

./configure --with-pgsql=<postgres install dir>

Best regards,
Victor

Hi,

make sure you have package postgresql-devel installed.

Best regards,
Victor

Yes, I think it's quite important. I'll try to schedule it for 2.1-RC1.

Best regards,
Victor

Hi,

there are few issues already found in 2.1-M3, especially with new back-connect functionality. We plan to release RC version in a week or two, which will be followed by stable 2.1 release.

Best regards,
Victor

Hi,

is it same question: https://www.netxms.org/forum/general-support/netxms-server-capability/?

Best regards,
Victor

Hi,

starting with 2.1-M3 there is agent-to-server connection option, so you can have site proxies behind firewall connecting to NetXMS server. Server itself should handle 50k nodes without issues, although you will need quite big amount of RAM (I would recommend 8 GB at least). Database will definitely require some tuning (but actual load and size requirements highly dependent on how much data you will collect and how often). Network connections should be fine because you will have connections open to proxies, and everything else will be between proxies and end nodes.

Best regards,
Victor

Попробуйте заменить

pResult->values

на

result

в строке 576.