NetXMS Support Forum

Эти алармы должны найтись во View->Alarm browser

Но для этого нужно зайти под юзером system (по умолючанию этот юзер отключен, его нужно включить в Configuration->User manager)

Он все еще в состоянии "когда-нибудь" - вещь хорошая, но на разработку нужно порядочно времени. Единственный шанс, чтоб он быстро появился - если кто-нибудь закажет разработку за деньги.

Была проблема с тем, что инсталлятор NetXMS не ставил в систему какой-то из C++ runtime и драйвер постгреса из-за этого не работал. Это починено, но видимо в какой-то из следующих версий, чем 3.3.323
Если можете, попробуйте проапгрейдится.

Hi!

Did you try to connect from desktop client, not the web one? Did you suceed?

We did some testing on this.

If the node has NetXMS agent, everything works properly - domain name is resolved into IP, we connect to agent on this IP, agent replies.
In this case agent will report that the node has two interfaces, one will be UP, the other DOWN. In interface configuration you would need to set expected status to IGNORE, otherwise one of the interfaces will always produce an alarm on the node.

The other case is when node does not has NetXMS agent. In this case we use ICMP checks, which take IP address from interface. The thing is that in current version IP address on interface is not updated on status poll.

Do I understand correctly that you do not have NetXMS agent on these laptops?

We will need to test this internally. It should work this way, if dns name gets properly updated.

There's also an alternative approach to use tunnel connections - in this case nodes are connecting to server and are identified by their unique identifier.

Please share the dump file with the help of any online service, e.g. wetransfer.com (choose Get transfer link there in properties to get a link to the file)

The reasons for that could be two things - either slow database performance or locks in server process.

Please set LongRunningQueryThreshold server configuration parameter to, e.g. 10000. If queries that take longer then 10 second would happen, they will be written to server log file.

If not responding events are happening, but no log running queries are logged, then it's probably locks in server process.
If your server is on Linux and can catch the moment, when this event happens, try running this script:
https://github.com/netxms/netxms/blob/master/tools/capture_netxmsd_threads.sh

gdb should be installed on the system to run this script. Script should be run 3-4 times with interval 30-60 seconds. It will create files with debug information in /tmp. Please share these files.

It's also possible to run this script as action for not responding event, but care should be taken not to run this script too often, as it's quite heavy temporarily pauses all netxms processes. So the action should have a script that stores last launch time in, e.g. persistent storage and checks that some time passed since that time.

Could be something on the database side. What database do you use?

Let's try to get some logging information. Please issue in server console (or via nxadm):

debug 0
debug client.* 8

then try show sessions again and share server log file for that moment.

Also, please attach console log file - it's located in ~/.nxmc/data/.metadata/.log

Hi,

What would happen if you issue
nxadm -c "show sessions"

from server command line? Will it reliably produce output there?

Есть еще план добавить WebAPI вместе с WebUI в общий Windows инсталлятор https://track.radensolutions.com/issue/NX-1949

Currently there is no out of the box functionality for that. It would be nice to have, but it depends of available development resources.
And the other question is how this should be implemented. Should we compare the actual value with average for, say an hour? Or with average value one day ago? Or with average on the same day of week or last business day?

First of all, you can try mean deviation threshold, it probably should increase if the value drops significantly. Number of samples in this case is the time during which the mean deviation is calculated. You need to experiment on this.

The other approach is to have two DCIs. First is collecting data as usual. Second is scheduled, e.g. every 10 minutes (it should not be too frequent to avoid producing load on the system), calculates average value of the first DCI for a period of time and stores it. First DCI then has script threshold that compares actual value with the average value. This script threshold can be quite advanced - compare value 24h ago, etc...

Please give an update how you implement this for you.

Hi!

Let me comment the steps that you've performed.

1) Part starting from tar zxvf netxms-3.5.90.tar.gz
You did compilation from sources here. For Ubuntu it's actually not needed, since we provide packages (which allow to install/upgrade software via apt-get)

2) Part starting from wget http://packages.netxms.org/netxms-release-latest.deb
If you look in the documentation, there are two sections there - "Using netxms-release package" and "Manually".
Only one of these was meant to be performed and the recommended is first one.
You can delete the last line in /etc/apt/sources.list.d/netxms.list that was added by steps from "Manually" section, but it's probably not causing problems (at least, for now).

3) Now, the reason for the error: Your database has format version 35.15, but server is compiled for version 34.16
When you did installation from sources, you used netxms-3.5.90.tar.gz., so it's version 3.5.90. And you did /usr/local/bin/nxdbmgr init there, so the database was initialized for that version.
But when you did install from packages, you got previous netxms version, because 3.5.90 was not available in packages yet (it was just released on that day and the packages were still prepared).

As of today, you can do
apt-get update
apt-get upgrade

and you should get 3.5.90 from packages. You can check package versions by running
dpkg -l | grep netxms

When you have 3.5.90, chances are that netxms will just start. But I am not sure about that, since you had
/usr/local/bin/nxdbmgr: error while loading shared libraries: libnxdbmgr.so.35: cannot open shared object file: No such file or directory
error when initializing the database.

So it's recommended that you delete your netxms database, recreate it and initialize it:
echo "DROP DATABASE netxms;" | mysql -u root -p

echo "CREATE DATABASE netxms;" | mysql -u root -p
echo "GRANT ALL on netxms.*to 'netxms'@'localhost' IDENTIFIED BY 'PaSsWd';" | mysql -˓→u root -p

in netxmsd.conf you have some old way of specifying database driver, please specify this way (a proper file example usually installs when installing package, but you already had this file, so it was not overwritten):
DBDriver=mysql.ddr

Then initialize the database - you also had old way of doing this, currently you should do just:
nxdbmgr init

Just tried on ubuntu 18, netxms-dbdrv-mysql is available there. What's your ubuntu version?