NetXMS Support Forum

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!

Quote from: pzandvoort on September 04, 2018, 10:11:44 PM
https://netxms.org/download/releases/2.2/2.2.8/netxms-websvc-2.2.8.war doesn't seem to be available....

Fixed, thanks for the report

MySQL8 now use "row_number" as a keyword.
We'll look into it.
Thank you for report.

Quote from: Spheron on August 28, 2018, 10:30:01 AM

Hello @all,

i would like to update from 2.2.7 to 2.2.8. The database upgrade doesn't work. It throws the following error:

Code Select Expand


Upgrading database...
Upgrading from version 22.35 to 22.36
SQL query failed (You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'row_number=0 WHERE row_number IS NULL' at line 1):
UPDATE dct_threshold_instances SET row_number=0 WHERE row_number IS NULL
Rolling back last stage due to upgrade errors...
Database upgrade failed



NetXMS is running on Windows 7 (64bit) and MySQL 8.0.12 (64-bit).

Any help will be welcome... Thanx.

Greetings
Marco

There is a known issue with upgrading utf8/16 database on older mysql (pre-5.7):

Upgrading from version 22.32 to 22.33
SQL query failed (Specified key was too long; max key length is 767 bytes):
CREATE TABLE policy_timer_cancellation_list (   rule_id integer not null,   timer_key varchar(255) not null,   PRIMARY KEY(rule_id,timer_key))
Rolling back last stage due to upgrade errors...
Database upgrade failed

We are working on that, but in a meantime you can perform this upgrade step manually:

CREATE TABLE policy_timer_cancellation_list(rule_id integer not null, timer_key varchar(191) not null, PRIMARY KEY(rule_id,timer_key));

UPDATE metadata SET var_value='33' WHERE var_name='SchemaVersionMinor';

After these changes, re-run "nxdbmgr upgrade" to finish upgrade.

Hello

NetXMS version 2.2.8 is out. Changes since previous release:

- Delayed actions in event processing policy
- Raw event data stored in event log
- New hook scripts: PostObjectCreate and DiscoveryPoll
- Implemented watchdog functionality for external subagents
- SNMP port and context can be specified in NXSL function CreateSNMPTransport
- Fixed Summary DCI table fail when row limit set
- Fixed menu path creation for Summary DCI Table and folder creation for graph view
- New command line options for Windows agent installer: /FORCECREATECONFIG, /LOGFILE=, /FILESTORE=, /CONFIGINCLUDEDIR=
- Server optimization for high load
- Fixed SQL errors during database import or migration
- New dashboard element "Port view"
- Fixed issues:
   NX-1377 (Can't upgrade sqlite database from version 21.4 to 21.5 with error "Unable to set not null constraint")
   NX-1435 (AgentTunnelListenPort configuration parameter is missing from config table)
   NX-1458 (DB upgrade from 0.454 to 0.455 failing for sqlite)
   NX-1459 (Online upgrade for 22.21 failed on sqlite)
   NX-1471 (Add option to create node in maintenance mode)
   NX-1472 (Physical Hyper-V Hosts are reporting as Node Type "Virtual" in 2.2.7)
   NX-1480 (Varbinds in SNMP Traps restricted to 255 characters)
   NX-1481 (Configuration option to disable topology based event correlation)
   NX-1482 (NetXMS server ignoring Syslog and Traps from devices in a Zone which are sending directly to NetXMS server)
   NX-1484 (Corrupted event messages if MySQL is used as backend database)
   NX-1488 ("Use active thresholds" checkbox gets checked after clicking on OK in map link properties)
   NX-1492 (Changes in object status not reflected on geo map)

Выложил новую сборку на веб

Hello.

Unlock and set password for user "system", then use this user to grant access rights to admin.
Once done, re-lock user "system", as it should not be used in normal day to day operations.

I just pushed correct 2.2.4 libraries to maven central. Try rebuilding tool.

Key in netxms-keyring.gpg is installed using netxms-release package which is available in the repos (and I suggest to upgrade it this way).
You can upgrade it manually:

wget https://packages.netxms.org/netxms-release_1.2_all.deb
dpkg -i netxms-release_1.2_all.deb