NetXMS Support Forum

Hi!

Macros only works in string expansion for events, alarms, and actions. Strings withing scripts are just strings. If you want to set current node name as custom attribute, you can do it like following:

SetCustomAttribute($node, "Node_HostName", $node->name);

You can find interface object using FindInterfaceObject function, and then use SetCustomAttribute as usual to set custom attribute for interface.

Best regards,
Victor

Скорее в df странные проценты. Агент получает значения total, used, и avail для файловой системы и из них считает проценты. Available space - это место доступное не root'у (free - резерв, обычно 5% от объема).

/mnt/storage

used %: 103 / 187 * 100 = 55.08021390374332 = 55
free %: 100 - 55 = 45
avail %: 75 / 187 * 100 = 40.10695187165775 = 40

/
used %: 25 / 173 * 100 = 14.45086705202312 = 15
free %: 100 - 15 = 85
avail %: 139 / 173 * 100 = 80.34682080924855 = 80

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

I'll try to reproduce this in my test environment later today.

Best regards,
Victor

Parameter list always show local parameters - even if proxy node is set. I've registered a bug for that and will fix it eventually. Currently you either have to enter parameter name manually, or create DCIs on management server, then move them to fritzbox node and set proxy node.

Best regards,
Victor

You can use "proxy node" property of the DCI to place DCIs on right object. Create DCIs as usual on fritzbox object, but set proxy node to management server object - actual data collection will occur on management server. Don't forget to add fritzbox object as trusted node to  management server object.

Best regards,
Victor

Hi!

You can use external parameter or external parameters provider in NetXMS agent. For example, adding

ExternalParameter = Test:my_script.sh

to nxagentd.conf will add new parameter called "Test" to your agent, with value being whatever was sent by script "my_script.sh" to stdout.
Search forum for more information - there should be a lot of topics about external parameters.

Best regards,
Victor

Hi!

As it looks like you have core file from the crash, can you please send me backtrace obtained with gdb. Instruction is following:

1. Run gdb as

gdb /usr/bin/nxagentd core

(replace core with actual core file location)

2. At (gdb) prompt, enter command bt

Best regards,
Victor

Насчет русских букв - а в какой кодировке они по SNMP приходят? Я бы рекомендовал использовать UNICODE сборку сервера и поставить CodePage в netxmsd.conf в кодировку, используемую в SNMP.

Спасибо, к следующему релизу приведу в порядок пакеты.

Thanks, I'll fix packages until next release.

Отфильтровать аудит лог по пользователю и сообщению (по маске User%logged in%) с убывающей сортировкой по дате - верхняя запись будет последним логином.

Hi!

Recently I've found a bug that prevents console from sending keep-alive messages to the server, and so server can forcibly disconect session after 15 minutes. Looks like it could be ypur problem as well. It is fixed in upcoming 1.2.13 release.

Best regards,
Victor

Похоже что каким-то образом создался обьект с пустым именем. Можете прислать результат команды

nxadm -c "show objects"

?
Ну и после этого можно попробовать найти этот обьект и дать ему какое-то имя руками.

Yes, it is available (you can get current sources by cloning git repository http://git.netxms.org/public/netxms.git and switching to branch "develop"). But it is client side change, and building console may be non-trivial task (you will need Maven for building client library and Eclispe 3.7 with right set of plugins listed in src/java/eclipse_addons.txt for building console).

Best regards,
Victor

Hi!

There is hard-coded read timeout on server side, which is used to detect dead sessions. Normally it should not happen, because client sends keep-alive messages once per minute. However, there is a bug in 1.2.12 which prevents client from sending these messages, and so inactive session terminated after 15 minutes. I already fix this bug, and after 1.2.13 release problem should be gone.

Best regards,
Victor

Hi!

Seems that there is a problem with application server embedded into current installer. I replace it with latest Jetty version and everything looks good now. I just updated web UI installers on our download page. Remove existing web UI version before installing new one.

Best regards,
Victor