NetXMS Support Forum

DSN должен быть системным. При проверке DSN, используете пользователя sa и пароль?

Попробуйте приложеную версию драйвера.

Hi,

can you please try with == OK and != OK?

Best regards,
Victor

Hi,

situations are not persistent - this is actually a bug. We plan to simplify situation usage a bit in 2.1 and will fix persistence issue as well. The only workaround currently is to use node's custom attributes instead of situations - they are persistent.

Best regards,
Victor

There is an issue in bug tracker: https://dev.raden.solutions/issues/976. I'll try to implement it in 2.1 branch.

Best regards,
Victor

Hi,

what views you have open at time of freeze?

Best regards,
Victor

Hi,

were those DCIs instance discovery DCIs? If yes, 2.0.5 most likely will fix it - possible deletion of wrong DCIs when deleting instance discovery DCIs was one of the bugs fixed in instance discovery code.

Best regards,
Victor

Hi,

do you use instance discovery in those templates? If yes, try version 2.0.5 - there were fixes in instance discovery.

Best regards,
Victor

Hi,

from the screenshots and exported config everything seems to be correct. I cannot reproduce this myself - I don't have iLO 3 board to test your template on, but I create sample table with same transformation and threshold works just fine. What NetXMS version you are using? Also, please try to modify event by adding script call like this: "%[TableData]" and create script called TableData in script library as following:


table = GetDCIValue($node, $event->parameters[3]);
row = $event->parameters[4];
return table->get(row, table->getColumnIndex("Smart Status"));


and change to not like to trigger event. You should see actual value for the cell in place of %[TableData]. It will be possible to check if it is actually correct.

Best regards,
Victor

Hi,

LVM monitoring extension for Linux agent is currently in development, and likely will be part of 2.1-M1 release. You can wait a bit and use NetXMS agent when this function will be available. Currently the only alternative is to create wrapper scripts for lvdisplay and use them as external parameters in agent.

Best regards,
Victor

Добрый день,

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

В аттаче драйвер с изменениями (для 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