NetXMS Support Forum

Hi,

management console now based on Eclipse 4.11 (2019-03), so you have to use this Eclipse version.

Best regards,
Victor

I just uploaded agent installer version 3.2.381 - please try that one.

Best regards,
Victor

Hi,

you can add /LOG or /LOG=file to installer command line. If file name is not provided log file will be created in user's TEMP directory.

Best regards,
Victor

Hi all!

We just published NetXMS 3.2 patch release 1. It mostly fixes few issues found so far. Changes since initial release:

- New attribute "primaryHostName" in NXSL class "Node"
- Fixed memory leak in log parser subagent
- Fixed incorrect value reported by internal parameter Server.MemoryUsage.DataCollectionCache
- Fixed broken Windows Event Log monitoring in logwatch subagent
- Fixed issues:
        NX-1794 (Problems with map decorations selection)
        NX-1798 (Incorrect default EIP port number)
        NX-1799 (Login name is limited to 13 characters if CAS is used)
        NX-1800 (If CAS response contains proxy information ticket is always rejected)

Not all components are affected, so most agents and integration tools were not updated to 3.2.380.

Best regards,
Victor

Похоже не влезает MAC адрес. Могут быть какие-то ноды с интерфейсами, у которых MAC длиннее 6 байт?

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