NetXMS Support Forum

So the problem is in upgrade (similar to what was reported on other thread). We will publish 5.0.3 today or tomorrow, hopefully this will be fixed by that moment.

Best regards,
Victor

Looks like nxdbmgr crashes during schema update. Could you please provide result of query

SELECT id,link_styling_script,filter FROM network_maps WHERE link_styling_script <> '' OR filter <> '';

(maybe you'll need to change condition, I'm not sure it is correct for MariaDB, but idea is to get all records where one of those fields is not empty).

Best regards,
Victor

Version 4.5.7 of UI client application and web UI is available in download archive. It should fix object tree update problem reported by multiple users. If you are using version 4.5, try to update your client to version 4.5.7 and report if object tree update issue is still there or is finally solved.

Best regards,
Victor

You likely can use Windows performance counters. There are quite a lot of them for GPU. I didn't try to collect them from NetXMS, but my Windows notebook seems to provide GPU utilization and GPU memory usage among other stuff, and they should work as any other perf counter using "Windows Performance Counter" source for DCI.

Best regards,
Victor

I just updated client application so that nodes without parent objects in infrastructure tree are not shown as root level objects. This change will be part of release 5.0.3.

Best regards,
Victor

Update: I just checked, and seems that there is another bug with same conversion (of instance filter scripts), that may lead to script corruption. We are currently building version 5.0.2 with the fix in upgrade procedure. If possible, restore database from backup and run upgrade again with version 5.0.2. Alternatively, restore only content of column "instd_filter" in table "items", and do script conversion manually where needed.

Best regards,
Victor

Hi!
This is instance filter script, number in script name is DCI ID. Please find this DCI and show the script.
Best regards,
Victor

For out of the box templates, if you didn't change them, you can just re-import them, either manually or by changing server configuration option Server.ImportConfigurationOnStartup to "always" and restarting server.

Best regards,
Victor

Quote from: Spheron on May 03, 2024, 04:01:33 PMHello @all,

noticed that there are no more windows server downloads online, except for users with active support contract... Are there any announcement that i missed?

I never heard or read of this change. I only noticed this cause i take a look in the download section of the NetXMS website.

It would have been nice if you had announced the change a bit in advance, then everyone could have thought about how to deal with it...

Greetings
Marco

Yes, I agree that we should have had announced it in advance. I will discuss it with the team and announce if there will be any changes to new policy.

Yes, it's database corruption caused by upgrade to 5.0.0 (fixed in 5.0.1, but unfortunately fix will not help if database is already converted).
Bug in upgrade procedure caused instance discovery filters to be replaced with transformation scripts for instance discovery DCIs where transformation scripts were defined. If you don't have lot of instance discovery DCIs best option is to go through them and re-create instance filters manually (or restore only "instd_filter" column in table "items" from database backup).

Best regards,
Victor

Patch release 5.0.1 published (it fixes bug in database upgrade procedure).

Quote from: Egert143 on May 03, 2024, 09:08:56 AMI was looking for the server installer for windows and saw that now support is needed for this. That is why i asked if it was no longer free.

is building windows installer for server from source complex task ?

Depends on your experience of course Build itself is straight-forward - there is Visual Studio solution file in the root of source tree, it will handle all the builds. Tricky part is to get all the dependencies (openssl, libcurl, libssh, libjq, libmodbus, libmosquitto, libpcre, database client libraries, breakpad, libmicrohttpd). Some of those are for specific components only, which you can exclude from build if you don't need them.

Most likely you have to install SQL Server Native Client which is needed for mssql.ddr to work.

Best regards,
Victor

We will try to reproduce that, but it likely will take some time.
I registered it a s a bug: https://track.radensolutions.com/issue/NX-2527

Hi,

delete file /usr/local/share/netxms/mibs/netxms.mib - it is old compiled MIB database and should not be there. Most likely leftover from running MIB compiler directly in /usr/local/share/netxms/mibs at some point.

Best regards,
Victor