NetXMS Support Forum

Perfect. Thank You very much.

Martin

We just fixed bug in database upgrade, we will start packing release 5.0.3 soon.

Best regards,
Victor

We just fixed bug in database upgrade, we will start packing release 5.0.3 soon.

Best regards,
Victor

There is not a link_styling_script field (currently running 4.5.6 version(restored from backup)

There is result of query as .csv attachment
SELECT id,filter FROM network_maps WHERE filter <> '';

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 can turn on sql trace for some time, from linux command line

nxadm -c "debug sql on"
and
nxadm -c "debug sql off"
afterwards.

This will turn on detailed sql query logging, log will be huge, but there will be more detailed information.

object_properties table is updated when objects are updated (renamed, custom attributes changed, etc). Changes are saved into db once per minute.

Quote from: Victor Kirhenshtein on May 11, 2024, 10:59:09 AMI 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

Thanks Victor, look forward to it.

Quote from: Filipp Sudanov on May 10, 2024, 08:47:24 PMNot sure why this is happening. Can you run the script I've shared manually (via Execute Script from context menu) on a couple of nodes which we bound to that container, but should not and share the output.

Hi Filip, attached is a screenshot of executing the script on a node that had an existing parent.  It always seems to return true whether on a node that has no other parent or an existing node.