NetXMS Support Forum

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

Hi,

looks like server cannot retrieve all links for some reason. Could you please provide output of SNMP walk for .1.0.8802.1.1.2.1.4.1.1 for both nodes?

Best regards,
Victor

Hi,

looks like a bug. What version you are using?

Best regards,
Victor

No, it is not possible without server source code changes.

Best regards,
Victor

Hi,

this script will transform first argument from hex string (space separated) into text:

l = length($1);
out = "";
for(i = 1; i < l; i += 3)
out .= chr(x2d(substr($1, i, 2)));
return out;


You should be able to use it as is in DCI transformation.

Best regards,
Victor

Hi,

it is a bug. We have fixed it in development branch, fix will be included into version 3.2 and next patch release for 3.1.

Best regards,
Victor

У события может быть один или несколько тагов, сейчас наличие тага можно проверить скриптом. Также таги видны в логе событий. Можно делать правила которые срабатывают на все события с определенным тагом например.

nxsnmpwalk и сервер не поддерживают символические имена OID'ов. MIB используется только для MIB browser'а, а при конфигурации надо задавать OID в числовом виде.

Just fixed this. Bug is actually in source code parser - it is not related to custom attributes but rather to negative constant passed as function parameter. Fix will be included into next patch release.

Best regards,
Victor

Hi all!

We just published patch release 1 for version 3.1 (product versions 3.1.260 and 3.1.261). Only server, client applications, and Solaris agents are affected. Changes since 3.1.242:

  * More diagnostic information in manual poll output
  * LDAP attribute names are case insensitive
  * Fixed command line parsing bug in remote action execution from EPP
  * Fixed bug in saving custom attribute changes
  * nxevent command line tool can generate events in a loop
  * Microsoft Teams driver allows use of message subject
  * Missing notification channel drivers added to Windows server installer
  * Fixed memory leak in C++ client library
  * Fixed server crash
  * Fixed bugs in database schema upgrade

Best regards,
Victor

Hi,

database driver you are using is definitely wrong (looks like leftover from old manual installation). You should use

DBDriver = pgsql.ddr

In general you need to specify full path to database driver in very special circumstances only - in 99% of the cases referencing driver by name only is preferred way.

Best regards,
Victor