NetXMS Support Forum

Добрый день,

пришлите пожалуйста лог ручной отправки из терминала.

В аттаче драйвер с изменениями (для 64 бит Windows). В SMSDrvConfig надо будет поставить тип сообщения NTEXT, например:

COM1:,9600,8,N,1,NTEXT

Hi,

registered it as an issue (https://dev.raden.solutions/issues/1264), somebody will take a look.

Best regards,
Victor

Hi,

you should not modify anything in database directly while server is running. Server caches lot of information in memory and do not expect changes in database. They will be either ignored or even rewritten. You should use Java API or Python scripts (nxshell) to manipulate data in NetXMS programmatically.

Best regards,
Victor

Hi,

nxdbmgr can detect some logical errors in database (mostly inconsistent or missing data), but it does not check that every table can be read for example. What you have seems to be badly corrupted database files - this is beyond the scope of nxdbmgr checks.

Best regards,
Victor

Hi all,

NetXMS version 2.0.5 is out. Changes since previous release:

- Data collection script can return null to indicate data collection error
- Added option to set type of each varbind in nxsnmpset
- Fixed memory leak in PostgreSQL database driver
- New attributes "source" and "sourceId" in NXSL class "Event"
- New method toJson() in NXSL class "Event
- LVM monitoring parameters on AIX
- Added option to get normalized server thread pool load average
- Fixed bug in self-monitoring termplates
- Management console
        - Fixed possible deadlock when executing server script
        - Fixed area charts on dashboards
        - "Interactive" option for line chart dashboard elements
- Fixed issues: #1018, #1039, #1239, #1250, #1255

Best regards,
Victor

Без патча не получится. Я сегодня/завтра соберу драйвер с изменением, можно будет попробовать.

Hi,

seems that agent read network mask incorrectly. I'll check it.

Best regards,
Victor

Hi,

it is not possible to transfer collected data from one server to another. However, agent can work simultaneously with multiple servers - you just have to list them in agent's config file. It is possible to change agent configuration from NetXMS server if this server address listed in MasterServers parameter on agent. You can edit agent config from management console by right-clicking on the node and selecting "Edit agent configuration".

Best regards,
Victor

Hi,

node object in FindObject call is not for limiting search scope, but for access control (it will only find objects where this node set as trusted if trusted nodes check is on). If you have trusted nodes check off, you can pass null as node parameter.

Best regards,
Victor

На мой взгляд совершенно правильно - каждый скрипт заимается своим делом.

Another option besides source code change is to create local port mappings on NetXMS server itself on some fake subnet, different local virtual IP for each NAT'ed device.

Best regards,
Victor

Hi,

this message could also mean that server cannot find required dll for pgsql.ddr. Check that postgreSQL client dll's are in your PATH.

Best regards,
Victor

Could you delete it again, turn on debug 6, run configuration poll, and send me log messages related to that node?

Best regards,
Victor

Планируется что будут появляться и другие шаблоны - поэтому для старых инсталляций параметр по умолчанию 0. Сейчас только несколько шаблонов для мониторинга самого сервера. Сломать ничего не сломает, просто будут дополнительные шаблоны и события.