NetXMS Support Forum

Did you initialize timescale DB with nxdbmgr init prior to importing data into it?
Can you set debuglevel = 9, run the server for 5-10 minutes and show the log?
Alternative approach would watch from the database side on what queries it's getting stuck.

Is your tomcat on the same machine where netxms server is running?
Is netxms server process (netxmsd) running?

Please run
ulimit -S -c unlimited
this will enable core dump creation.
Then run
nxdbmgr init
again. When it crashes, a file should appear in current folder named core.xxxx. Please attach this file here.

As per some post on stackoverflow, mssql is able to get into a deadlock on simultaneous insert and delete due to some things related to indexes.

Some changes will be introduced into db writing mechanism in coming patch release. Currently, when housekeeping is happening, there are two separate queues - one for housekeeping tasks and another for new data inserts.
In the coming version a running housekeeping query will pause insert queries. After housekeeper query completes, it will check the length of current insert queue, if it's above Housekeeper.Throttle.HighWatermark setting housekeeper will pause (until reaching LowWatermark), otherwise another housekeeper query would run.
As a result this should fix the deadlocking issue.

Currently the only way to make this work is to create a separate node for each slot. In configuration for each node you have to specify corresponding community string.
To avoid issues with one and the same IP address for several nodes set checkbox "This is address of remote management node" for all these nodes. And disable configuration polls for these nodes.

If you have a big network of such devices, you can contact Raden Solutions, they can develop a custom driver for such devices within sponsored development.

Do you mean exactly "status map" dashboard element, or "Alarm viewer"?
Currently there is no filtering for both of them. But please describe in more details what do you want to achieve? Do you want to show status of a node as green, when alarm is acknowledged or something else?

На какой именно?

А если вы запускаете этот скрипт просто из консоли на 2012 R2, то вывод правильный, без кракозябр?

Ok, please set DebugLevel = 7 in server configuration, start the server, wait until it crashes or exits and share the log file.

Added some info into documentation. Feel free to comment if anything else should be added.

Здравствуйте! А какая точно версия Netxms? Можете показать кусочек event log'а с этими сообщениями? И включить ненадолго 6 уровень дебага и прислать кусочек лога сервера за время, когда эти сообщения возникают.

Thanks for exact instructions. Created https://track.radensolutions.com/issue/NX-1892 for that.

1. The log file looks incomplete. Seems that you first started the server with low debug level, it ended with
2020.07.01 16:06:19.834 *E* [                   ] Error initializing component locks table

The you started with higher debug, but it did not end up with the same error. Or have the server crashed?

2. Please try to run
nxdbmgr check

What output does it produce?

I've tried installing NetXMS server 3.4.178 on a fresh install of Win Server 2019 Standard edition (x64), the installation went fine.
Installer also installed Microsoft Visual C++ 2017 Redistributable (x64).

Could there be anything special about your system? Can you show what other software you have installed? Any antivirus software?
Could you try on a fresh or another installation of Win server?

This is sort of debug menu that has a list of all possible windows that management console can open. The thing is that some of windows only work when opened in some context, e.g. when executing some command using object tools.
This debug menu will be removed in a future version.