NetXMS Support Forum

Sorry for delay, dmg uploaded now.

Никто не мешает выставить вам какую угодно маску. Сервер получает информацию с агента (или через SNMP), и если такая подсеть ему еще не известна - создает (с реальной маской). Если после этого другое устройство сообщает ту же подсеть, но с другой маской - генерируется событие - потому что это означает, что на одном из устройств маска неправильная, и неплохо бы админу ее поправить.
Единственный случай, когда сервер использует /24 - если добавили устройство из неизвестной сети, и это устройство не отвечало на запросы к агенту или SNMP в момент добавления. В этом случае сервер создает /24 - что не хуже любого другого значения по умолчанию.

А про отключение - уберите правило в EPP для события SYS_INCORRECT_NETMASK (ну или добавьте правило с action=stop processing). Если хочется убрать из event log - откройте редактирование события и уберите флажок "Log event" (но в event monitor всё равно мелькать будет).

Удалите неправильный сабнет, на следующем configuration poll подсеть будет пересоздана правильно.
Только убедитесь, что ноды из сабнета есть где-то в infrastructure services, чтоб сервер их не удалил автоматически.

Hello.

I just installed netxms-server package on clean Ubuntu 18.04.1 LTS without any issues.
Make sure that you include "universe" repository and run "apt-get update" prior to installing netxms-server.

Package info: https://packages.ubuntu.com/bionic/libzmq5

Installation steps:

wget http://packages.netxms.org/netxms-release_1.2_all.deb
dpkg -i netxms-release_1.2_all.deb
apt-get update
apt-get install netxms-server netxms-dbdrv-pgsql

Not at the moment - there are multiple ways to configure is using existing tools:
* on most UNIXes you can use existing MTA (Postfix, Exim, Sendmail, e.t.c.) to use smarthost over TLS.
* For Windows there is http://emailrelay.sourceforge.net/ (I recommend version 1.9)

Looks like "server already configured" marker is missing from the registry.

Check key HKLM\Software\NetXMS\Server, there should be DWORD value "ServerIsConfigured" (actual value does not matter, it just should exist).
If "ServerIsConfigured" does not exist - wizard will start in interactive mode.

Yes, mysqldump lock tables, that's normal.
There are two solutions:
1) use mysql replication for backup
2) block SYS_THREAD_HANG for backup timeframe (I use this option in most setups).

Add new EPP rule at the top of the policy:

Event: SYS_THREAD_HANG
Script:
  now = localtime();
  return (now->hour == 3 && (now->min >= 10 && now->min =< 20));
Action: Stop processing

(I assume that backup is between 3:10 and 3:20 - adjust script as needed)

Quote from: isoftcom on November 19, 2018, 08:12:37 PM
Is there way on how to tell netxms not to generate a lot of these history?

Sure.
1) Increase collection interval for the table DCI (it's once a minute by default)
2) Decrease retention time for the table DCI (1 month by default)

You can change these settings per-DCI.

To find out which DCI consume most of the space, you can query table in question:

select item_id,count(*) c from tdata_122 group by item_id order by c desc;

ID is the same as shown in data collection editor for the node

When node goes into maintenance mode, event MAINTENANCE_MODE_ENTERED is generated. Unique ID of the resulting event is saved into maint_event_id.

It's simple insert with 3 field and single composite index, it should not be expensive.
Please show explain / query plan.
What DB you are using?
How many objects in the system?
How big the database is?
What is retention time for tables DCIs on node 122?

Java10 is not supported by the Eclipse platform we use.
You need to modify nxmc.ini and specify path to JVM (: https://wiki.eclipse.org/Eclipse.ini#-vm_value:_Linux_Example

Install DB on the new server
Install NetXMS on the new server, cancel configuration wizard
Dump old database / restore on the new server
Copy configuration files (c:\netxms\etc\*.conf)
Adjust configuration files (credentials, IP addresses, etc.)
run "nxdbmgr upgrade"
Start "NetXMS Core" service.

We can perform migration for you remotely, please contact us at [email protected] for a quote.

Hello.

Yes, windows 10 is fully supported. Any version can be upgraded to latest using standard installer.
Upgrade process is really simple - install new binaries, then upgrade database schema. By default, schema upgrade is performed by the installer automatically but I'd do it manually:

1) backup existing database
2) run integrity check: "c:\netxms\bin\nxdbmgr check" and fix errors if any.
3) migrate existing database to new server, if required
4) install new binaries using latest sever installer. In installation wizard select option "do not upgrade database schema". Cancel server configuration wizard if installing on the new server, copy netxmsd.conf and nxagentd.conf from c:\netxms\netxms to the new server (to the same location)
5) adjust database credentials in netxmsd.conf
6) run cmd.exe, then run "c:\netxms\bin\nxdbmgr upgrade". This will upgrade schema (and convert data when needed) to latest version.
7) run integrity check again ("c:\netxms\bin\nxdbmgr check"), most likely this run will find some leftovers / minor inconsistencies which were not detected by the old version
8) start sever in debug mode: "c:\netxms\bin\netxmsd -D4" (4 - debug level)

if everything is in order, stop server with "down" command and restart as windows service.

Hello.

What version of the NetXMS you are installing? This issue was fixed in 2.2.9.

Dear users!

We got a request for developing Asterisk monitoring extension for NetXMS. Request initiator is willing to partially fund this project and we are looking for co-funding. If you are interested in this functionality as well and willing to become a sponsor for this development please contact us.

Thank you in advance for your support!