NetXMS Support Forum

Try renaming the .war file to nxmc.war and deploying it.

There is no need to install intermediate version - latest version should be able to upgrade all the way through.
However, upgrade process ran into in issue on one of the steps. Can you please open psql, connect to your netxms database and show the output of the following commands:

\d alarms;

select count(*) from alarms;

\d old_alarms;

\d event_log;

\d  event_log_v35_2;

В Object Details в поле Driver что показывает для 1900-16 и 1920-48?

А какой драйвер определился на 1900-16 и 1920-48?

Импорт MIB файлов нужен для того, чтоб более удобно выбирать OID при создании DCI. На то, как отображаются интерфейсы устройста это не влияет, за это отвечает SNMP драйвер.

Для мониторинга состояния RAIDа также нужно найти OID, отдающий эту информацию и настроить DCI.

Оно в таком виде запускается: -d директория с исходными файлами, -o результирующий файл:
nxmibc -d /usr/share/netxms/mibs -o /usr/share/netxms/mibs/netxms.mib

и исходные файлы все должны быть с расширением .txt

I would restart the agent just to make sure, but you probably already did that.

There could be a few ways for the agent to read another config then the default one
- running it with -c <config_file_name>
- running it with -M <server_ip> - it would get config file from server
- configuration policies that add up to the config - they reside in system32/config/systemprofile/appdata/local/nxagentd/config_ap/   (or other user home folder, if agent is started under other user, not system one).

10 lines of log are not enough - they span for less then 0.1 seconds. Let's improve the process:

nxadm -c "debug client.* 6"
nxadm -c "logmark"
<replicate the error>
nxadm -c "debug client.* -1"

This will produce
2020.12.16 18:20:52.119 *D* [                   ] ******* MARK *******
line to server log. We need the log file from that mark to the end of the file.

In NetXMS the management console keeps all objects (containers, nodes, etc) in memory with their statuses. When object information changes on server, it sends information about this to connected consoles. If there are a lot of changes, but communication to a console is slow, it could happen that server won't be managing to send the updates. In this case server send a message to the console to display that warning.
Currently there is no healing mechanism, so once this message has appeared one would need to restart the console.
In 3.7, which is hopefully coming in next few days communication to console has been improved, so it might become better with this.

Not sure. At hand I have Centos 7.8, it has gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) and ./configure in 3.3 runs fine on it.

also not sure why you are specifying openssl, curl and pcre locations - are they not available from packages?

This might be the reason:
/usr/bin/ld: error while loading shared libraries: libbfd-2.20.51.0.2-5.48.el6_10.1.so: cannot open shared object file: No such file or directory

this file seems to be in binutils package.

Can you share your config.log?

Let's try to get some more debug information. Can you please run the following command in the command line on the server:

nxadm -c "debug client.* 6"
This will increase debug level for log messages related to communication with the console.
Then try to open IP neighbors window and wait for the error.
When the error shows, turn off the additional debugging
nxadm -c "debug client.* -1"
and send us server log file

Are you sure that nxagentd.conf portion is exactly the same that the agent is running with? Was agent restarted to work with actual config?
For me "RunExternal (shell exec): worker thread created" only appears when ExternalParameterShellExec is used (by the way this soon gonna be reworked and all actions and external parameters will be lauched as ShellExec).

I've tried with agent 3.6.300. Here's my config:
ExternalParameterShellExec=Get-ScheduledTask(*):powershell.exe -NoProfile -Command "$$Parameter = \"$2\"; Write-Host (Get-ScheduledTask -TaskName \"$1\").$$Parameter"

And that's the log:

2020.12.16 03:41:40.720 *D* [comm.cs.50         ] Requesting parameter "Get-ScheduledTask("Test Task", "State")"
2020.12.16 03:41:40.720 *D* [comm.cs.50         ] H_ExternalParameter called for "Get-ScheduledTask("Test Task", "State")" "Spowershell.exe -NoProfile -Command "$$Parameter = \"$2\"; Write-Host (Get-ScheduledTask -TaskName \"$1\").$$Parameter""
2020.12.16 03:41:40.720 *D* [exec               ] RunExternal called for "Get-ScheduledTask("Test Task", "State")" "Spowershell.exe -NoProfile -Command "$$Parameter = \"$2\"; Write-Host (Get-ScheduledTask -TaskName \"$1\").$$Parameter""
2020.12.16 03:41:40.720 *D* [exec               ] RunExternal: command line is "powershell.exe -NoProfile -Command "$Parameter = \"State\"; Write-Host (Get-ScheduledTask -TaskName \"Test Task\").$Parameter""
2020.12.16 03:41:40.720 *D* [exec               ] RunExternal (shell exec): worker thread created

Ethernet/IP is a protocol used on some industrial controllers, this message informs that netxms was not able to connect via this protocol.

PDH error is related to windows performance counters. On configuration poll netxms is trying to read the list of performance counters. If this was successful, when adding a DCI of type "Windows performance counters" under "Select" button there will be a list of available counters.
In node properties -> Polling it's possible to turn this off - "Disable reading of Windows performance counters metadata" checkbox.

Here's an old post that mentions same PDH error:
https://www.netxms.org/forum/general-support/problem-with-windows-performance-counters/

А как именно вы пытаетесь добавлять MIBы?

Во этих MIB файлах есть зависимость от SNMPv2-SMI.txt
Он должен был проинсталлироваться вместе с NetXMS в директорию mibs, туда же нужно добавлять ваши mib файлы и запустить mib compiler.