NetXMS Support Forum

You should not use tags 3.0, 3.1, 3.2, etc. - they are pointing to start of appropriate version development, not release point. Instead you should use latest commit in appropriate branch stable-3.0, stable-3.1, etc. We didn't create stable-3.2 branch yet as currently 3.2 is not yet diverged from master.

Best regards,
Victor

Can you check actual file presence there and compare MD5 hashes for original and transferred files?

Best regards,
Victor

Are you sure that findObjectByName didn't fail? Try to check return value for None before using it for getObjectId.

Best regards,
Victor

Hi,

I just tried to build 3.1.241 on Ubuntu 18.04 with your configure options and build went fine. Make sure your source package is not broken, maybe try 3.2.350 instead. Also you can use generic Linux agent binaries - they should work on most modern distros.

Best regards,
Victor

Hi,

setCustomAttributes methos now expects Map<String, CustomAttribute> instead of Map<String, String>. Try to replace line

MODIF.put("UR1location", Location)

with

MODIF.put("UR1location", CustomAttribute(Location, 0, 0))

Best regards,
Victor

Hi,

you can check log file on those agents - it may have indication on why incoming file transfer failed.

Best regards,
Victor

Yes, looks like images cannot be read correctly. Can you send me actual image somehow so I can test it?

Best regards,
Victor

You can just delete all tables in the database and re-run nxdbmgr init. You can delete all regular tables with attached SQL. Tricky part is to delete all idata_ and tdata_ tables. One option is to use command like this to generate SQL file (Postgres version):

psql -c "SELECT id FROM nodes" | grep -ve '[(i-]' | sed -e 's/\s*\([0-9]*\)/DROP TABLE idata_\1; DROP TABLE tdata_\1;/' > drop_data_tables.sql

and then run drop_data_tables.sql

Best regards,
Victor

We just published 3.2 which is current stable release now. I think we will made those internal changes in 3.3, so April seems reasonable.

Best regards,
Victor

Hi,

I think that we should have TR-069 support. I have registered it as feature request: https://track.radensolutions.com/issue/NX-1777. I'll try to experiment with it as time permits.

Best regards,
Victor

Hi,

you should have Apache Maven installed and available in your PATH, then you can build it with following commands (from root of source tree):

mvn -f src/java/netxms-eclipse/pom.xml -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:update-pom -Pconsole

mvn -f src/java/netxms-eclipse/pom.xml clean package -Pconsole -Dtycho.disableP2Mirrors=true

Generated files will be in src/java/netxms-eclipse/target

Best regards,
Victor

Hi all!

New stable version of NetXMS - 3.2 - is officially released.

Changes since previous release:

- Data collection from web services
- Nodes within chassis and chassis view
- EtherNet/IP device discovery
- Image library configurator completely rewritten
- Maximum password length supported by nxencpasswd increased to 64 characters
- Removed support for ancient custom CheckPoint SNMP agent on port 260
- Added option to control case sensitive matching in log parser rules
- New internal parameters for server stats (object count, alarm count, etc.)
- Method "setMapImage" of NXSL class "NetObj" accepts null value as "reset to default" indicator
- Fixed issues:
        NX-50 (Allow per-DCI SNMP version settings)
        NX-58 (Refactor Image Library)
        NX-896 (Display blade chassis and servers in rack)
        NX-1476 (NetXMS Server crashes when sending alarm summary email)
        NX-1523 (Store object creation time)
        NX-1525 (Use HTTP response data as DCI value)
        NX-1724 (Implement agent parameters for inode usage)
        NX-1741 (Node placement within chassis)
        NX-1748 (User agent should check on startup if it is already running in same session)
        NX-1750 (Configurable retention time for node hardware and software components)
        NX-1754 (HTTPS and SOCKS proxy options in Telegram channel configuration)
        NX-1767 (File manager may be unable to access file with percent sign in name)
        NX-1781 (Process launched by ExternalParametersProvider inherits file handles of agent process)
        NX-1782 (Windows installer offers generic.sms SMS driver, while the server is now reworked to have notification channels)
        NX-1792 (Unable to use script with parameters for instance discovery)
        NX-1796 (WebUI and REST API not connected securely to the NetXMS server)

Best regards,
Victor

Hi,

what exact console version you are using? Is it desktop or web based?

Best regards,
Victor

Hi,

one of the biggest issues with multi-tenant setup is event processing configuration. Currently there is single policy and access to it is controlled by global access rights. For proper multi-tenant setup we also need separate event processing policies, action configurations, etc. Depending on what you want to achieve it could be easier to run multiple instances of netxmsd, using docker containers for example.

Best regards,
Victor

Debian/Ubuntu packages now available in repository.

Best regards,
Victor