NetXMS Support Forum

Looks to be a bug, I've created a ticket for this
https://github.com/netxms/netxms/issues/3219

There are now special custom attributes:

ssh.login
ssh.password
ssh.port

so e.g. %{ssh.port} macro should work

Правой кнопкой по ноде, которая прокси, Change zone... и там выбрать зону.

Текущую зону ноды видно на закладке Overview в разделе Communications. 

В приложении тестовый отчет (он есть на гитхабе: https://github.com/netxms/sample-report, там есть чуток инфы в readme). На Линуксе его надо положить в директорию /var/lib/netxms/nxreportd/definitions, репортинг сервер его должен подцепить - это проявится тем что там должна появится директория users-1.0.0.

В настройках сервера адрес репортинг сервера нужно написать именно в IPv4 виде - 127.0.0.1, потому что localhost может раскрывать в IPv6, а репортинг его не умел.

Если не хочет работать, покажите лог репортинга
journalctl -u netxms-reporting.service

I've created a ticket for this: https://github.com/netxms/netxms/issues/3214

What is your NetXMS Server version exactly?
Can you show reporting server log for the moment when - if you are on Linux, this command will show it
journalctl -u netxms-reporting.service
Also note, that if you changed some parameters in SMTP-Text notification channel properties you need to restart reporting server for the changes to have effect

Your server is v. 6.1.1, but web UI still stays on 6.0.x.

Have you replaced the .war file in Tomcat/Jetty with the new one (https://netxms.com/download/releases/6.1/nxmc-6.1.1.war)?

If yes, sometimes Tomcat/Jetty is hesitant with switching to new file, try removing .war file, restarting Tomcat/Jetty, putting .war file and restarting again.

Database query planning is a separate mystery on its own. Anyways, developers restored additional index as it was before v. 6.0, that will be included in next patch release.

Еще одной штуки не хватает, когда этот тикет закроется тогда можно будет прикручивать:
https://github.com/netxms/netxms/issues/3199

А как сконфигурированы прокси - они прописаны в свойствах ноды, или ноды в удаленных офисах выделены в зоны? Если второе, то прокси тоже нужно поставить тоже в эти зоны.

Да, сейчас мы читаем только нормализованное значение, а нужны raw. Сделал тикет: https://github.com/netxms/netxms/issues/3199

raw_dci_values table is just a cache of most recent DCI values. You can just truncate it and proceed with the upgrade:

TRUNCATE TABLE raw_dci_values;

Possible case could be a locking of some server thread. You can capture server threads when you see delays in working with the server from the GUI, here's the script: https://github.com/netxms/netxms/blob/master/tools/capture_netxmsd_threads.sh
Script should be executed 3 times with 20-30 second interval. It needs gdb and netxms-dbg packages installed on the system.

Also to check - on netxms server node there should be Server: Number of Processed Events (based on internal Server.TotalEventsProcessed metric) - just to verify that there we no sudden spikes in event quantity.
In overall there's quite a few metrics there, e.g. Server QueueSize ones, it's worth checking them for any big spikes.
If you don't have Server.ImportConfigurationOnStartup set to Always, you might not have the most recent template with above mentioned DCIs, you may want to import them from /usr/share/netxms/templates/netxms_server.xml

Hi,

Please show value of
DefaultNotificationChannel.SMTP.Text
from Configuration->Server Configuration.

If above is set to "SMTP-Text", pls show configuration of SMTP-Text notification channel. If above is set to something else, pls show configuration of that notification channel.

Can you show a screenshot to understand what exactly is in which language?