NetXMS Support Forum

Hi,

currently it is not possible. I've added feature request for that: https://track.radensolutions.com/issue/NX-1785

Best regards,
Victor

Hi,

I just increased maximum password length for nxencpasswd in 3.2 branch.

Best regards,
Victor

Hi,

DCI value length is limited to 255 characters. In your case you can use external parameter provider instead of external parameter, do JSON parsing in agent side script and output all parameters you are interested in as name = value. Then you'll be able to collect them by name as any other agent's parameters.

Best regards,
Victor

Hi,

one option is to use zones and put those routers into different zones. Another option is to mark internal interfaces as "exclude from topology". Second option is easier if you are not interested in anything behind those interfaces.

Best regards,
Victor

Could you show screenshot of overview and interfaces tabs for those nodes?

Best regards,
Victor

Hi,

configuration file looks correct. How exactly you run nxdbmgr? Try to specify full path to old DB config and make sure it is accessible.

Best regards,
Victor

Could you please show output of commands

nxadm -c "show lldp id"

for both nodes, replacing id with actual node ID?

Best regards,
Victor

Hi,

fifth argument to File.FolderCount represents age filter. If < 0, only files created after now - abs(value) will match; if > 0, only files created before now - value will match. For example, to count folders older than one day in /tmp (without recursion) you can use

File.FolderCount(/tmp,*,0,,86400)

Best regards,
Victor

If you get "connect timed out" after you press "Login" button in web UI, that means that backend application cannot connect to NetXMS server. Is NetXMS server on same machine? If not, check that port 4701 on NetXMS server is reachable from web server and that address of NetXMS server set correctly in web application properties.

Best regards,
Victor

Create file batch.sql containing single line

ALTER TABLE idata_119 DROP COLUMN raw_value;


and run command

nxdbmgr batch batch.sql

Best regards,
Victor

Hi,

seems that DB schema is inconsistent. If only one table is corrupted you can drop "raw_value" column from it and try to run upgrade again. Otherwise you may run nxdbmgr with -X option (it will ignore upgrade errors) and after completion manually check all errors.

Best regards,
Victor

deb build is in progress, will be available within hour or so.

Best regards,
Victor

Hi all!

We have published NetXMS 3.1 patch release 2. Most components have version 3.1.297 and some (Windows packages and UI) have version 3.1.300. This patch release should fix multiple issues found since patch release 1 including server deadlock reported recently by multiple users.

Best regards,
Victor

Hi,

we were unable to reproduce this issue. Please try to upgrade to latest version and check if it is still persist.

Best regards,
Victor

Yesterday we have fixed bug that cause deadlock on object access. It can be root cause for your issue as well. We will publish new patch release for 3.1 today - please check if it will help.

Best regards,
Victor