NetXMS Support Forum

Hi,

attached is patched server core (for 64 bit Windows).

Best regards,
Victor

Hi,

what database you are using?

Best regards,
Victor

К сожалению это именно баг. К следующему релизу обязательно исправим.

Добрый вечер,

1. А на пинги устройство отзывается? Если нет, то единственный вариант наверное - мониторинть состояние порта коммутатора к которому подключено это устройство.

2. А при компиляции не было ошибок?

3. В DCI можно таким скриптом:


return right(int32($1 / 3600), 2, "0") . ":" . right(int32($1 % 3600 / 60), 2, "0") . ":" . right(int32($1 % 60), 2, "0");


превратит количество секунд в hh:mm:ss.

4. Да, именно для этого они и нужны. Можно написать например так:

Нагрузка: %s%%

Можно использовать любые символы из Java Formatter: https://docs.oracle.com/javase/7/docs/api/java/util/Formatter.html

5. Нет

Hi,

you specify node height and top unit number. Depending on rack numbering direction it will be lowest unit number (for top-bottom numbering) or highest unit number (for bottom-top numbering). Below are example for one and two units devices with both numbering schemes:

top-bottom numbering


UNIT  DEVICE
1
       ------------------
2     | NODE1 (2U)
       |
3     |
       -------------------
4     | NODE2 (1U)
       ------------------
5


you specify position 2 for node 1 and position 4 for node 2.

bottom-top numbering


UNIT  DEVICE
5
       ------------------
4     | NODE1 (2U)
       |
3     |
       -------------------
2     | NODE2 (1U)
       ------------------
1


you specify position 4 for node 1 and position 2 for node 2.

Best regards,
Victor

I found the bug. It is SQLite-specific. It will be fixed in 2.0.2, I can also provide custom build for server if needed. Switching to any other database will help as well.

Best regards,
Victor

Попробуйте обновится на 2.0.1, если не поможет, то надо будет смотреть детально что за ноды. На тестовой системе мне не удалось повторить проблему.

Hi,

could you please run it with debug level 9 and post output?

Best regards,
Victor

Yes, definitely. It is one of the goals for next major release.

Best regards,
Victor

At some point, definitely I cannot promise exact release when it will be implemented though. You can keep track of it: https://dev.raden.solutions/issues/1118.

Best regards,
Victor

Hi all!

NetXMS version 2.0.1 is out. It is pure bugfix release which fixes important issues with ODBC and MS SQL database drivers. Also, minor issues #1052 and #1063 were fixed.

Best regards,
Victor

Hi,

that probably will require additional element - chassis - that will be placed into rack, and blade servers will be bound to chassis in a same manner they are bound now to racks - be giving position and size.

Best regards,
Victor

Hi,

it's only visible when you open dashboard in "Management" perspective by selecting "Open" on dashboard object (or double click on it).

Best regards,
Victor

Hi,

this field contains root event id detected by event correlation module. When node is in maintenance mode all events will be correlated to "enter maintenance" event, but there are also other possible situations, for example when node goes down, all "interface down" events for ech interface correlated to "node down" event.
You can distinguish if events was correlated to maintenance mode start event by checking event code of root event.

Best regards,
Victor

Hi,

you have few options here:

1. Run nxdbmgr with -X option so it will skip failing queries;
2. Install newer sqlite from backports;
3. Build NetXMS from sources and specify --with-internal-sqlite option to configure to use bundled sqlite;
4. Migrate to another database (actually, recommended option).

Please note that in the future SQLite support as backend database will be dropped completely.

Best regards,
Victor