NetXMS Support Forum

Hi,

default templates re-imported from file system on server startup. You can disable this behavior by setting server configuration parameter ImportConfigurationOnStartup to 0.

Best regards,
Victor

Yes, console needs at least Java 7. Strange that it starts at all. I'll check that.

Best regards,
Victor

Can somebody please run upgrade with -t option and post output? Also, content of failed table before upgrade could be helpful.

Best regards,
Victor

Hi,

tdata tables holds table DCI values, so you should check your table DCIs. If you don't use them then everything should be fine.

Best regards,
Victor

Hi,

it should be safe. I recommend to backup database before upgrade though nxdbmgr upgrade should handle everything, and if you are using Windows installer, it will be handled by installer.

Best regards,
Victor

In 2.1 user admin is an ordinary user which gets it's access from "Admins" group. Login with user "system" (it is superuser that always has full access) and check that "Admins" group has full permissions (or give explicit permissions directly to user "admin").

Best regards,
Victor

Hi,

seems that global permissions was not updated during upgrade. In 2.1 we introduce alarm categories, and new global access right "access to all alarm categories" which should be enabled for all users to keep behavior compatible with 2.0. Make sure your user/group has this access right set.

Best regards,
Victor

Hi,

try to upgrade to 2.1 if possible.

Best regards,
Victor

Using same version as server will always work. Other versions may or may not work - protocol version may stay the same between product versions. Usually if you got this error that means that your client is too old and you just upgrade to version matching your server version.

Best regards,
Victor

HI,

check that your user/group has global permission "access all alarm categories".

Best regards,
Victor

Hi,

what was exact error message?

Best regards,
Victor

Hi all!

NetXMS version 2.1 is released. It is first stable release in 2.1.x branch which also makes 2.0.x branch obsolete. We strongly encourage 2.0 users to migrate to 2.1. Changes since previous release (2.1-RC1):

- Improved audit logging
- Improved data reconciliation between agent and server
- Improved Grafana integration
- Server detects changes in installed packages during configuration poll
- Added MariaDB database driver
- Fixed excessive CPU usage by agent on AIX
- nxshell can connect to server on non-standard port
- Driver for Netonix switches
- NXSL:
        - New methods for arrays: append, insert, pop, push, remove
        - Table methods get and set can accept column name instead of column index
        - Table row method get can accept column name instead of column index
        - Added table row method set
        - Access to DCI owner object in data collection and instance discovery scripts via $targetObject variable
- Management console:
        - Improved layout of dashboard elements
        - Added option to indicate alarm severity with background color in alarm list
        - Fixed bug in folder download in file manager
        - Proper support for ANSI colors in object tools output in web UI
        - Object dragging on map disabled if user don't have write access to map object
        - Option to hide sub-interfaces in UI (currently works only for Juniper switches)
- Fixed issues: NX-1039, NX-1041, NX-1166, NX-1180, NX-1194, NX-1195, NX-1212, NX-1214, NX-1215, NX-1234, NX-1236, NX-1243, NX-1244, NX-1251, NX-1253, NX-1256, NX-1257, NX-1260, NX-1262, NX-1264

Best regards,
Victor

Hi,

tables are cleaned by internal housekeeper process according to configured retention times. All tdata_* tables contains data for table DCI. You can reduce their size by reducing retention times on table DCis. Also, version 2.1 uses different format for table data storage, more efficient in terms of consumed space (but less efficient for random access).

Best regards,
Victor

Hi,

if standard MIBs are working then there is no need for changes in a driver. If you don't see LLDP peers then problem is missing and/or incorrect information in these MIBs.

Best regards,
Victor

Hi,

fixed in release 2.1

Best regards,
Victor