NetXMS Support Forum

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

Yes, remote installation actually contacts running agent and instructs it to upgrade itself (by running installer in unattended mode). Remote upgrade without running agent is not possible.

Best regards,
Victor

Hi!

There are no ready-to-use solution for JMX integration. Some work is underway, but it's not ready yet. What we currently have is ability to write custom sub-agents in Java - you probably can use it to develop own subagent in Java relatively easy.

Best regards,
Victor

Hi!

I don't really understand what do you mean by "output window". Can you share a screenshot maybe?

Best regards,
Victor

Hi!

Do you have agent's log from this server? Otherwise it's hard to tell what was happening... One of possible issues could be that there was too many connections hanging, so agent stop accepting new connections.

In 1.2.12 it is possible to get node summary per subnet or container - just select subnet in object tree and in object details view you'll have "Nodes" tab where all nodes inside this subnet or container will be listed, including agent version.

Best regards,
Victor

Hi!

On what OS? If this is Windows, can you try to run installer on one node manually and check it it will report any errors?

Best regards,
Victor

Hi!

Seems like common problem, there are few other very similar bug reports. We are trying to reproduce it and fix.

Best regards,
Victor