NetXMS Support Forum

Hi,

we decided to drop combined server/console package as part of overall effort to reduce number of packages and thus required support efforts. Actually we did expect that in most cases server is installed on separate machine and users are connected from remote workstations.

Best regards,
Victor

Hello!

I suppose netxmsd is not starting for some reason. Can you share netxmsd log file?

Best regards,
Victor

Hi all!

NetXMS 3.2 patch release 2 (version 3.2.400) is officially published. Changes since 3.2 patch release 1:

- Proxy nodes does not collect DCI data from SNMP nodes marked as down
- Configurable address block size and inter-block delay for active network discovery
- Fixed server memory leak in instance discovery code
- Fixed broken Net.ArpCache and Net.IP.RoutingTable lists in Linux agent
- Fixed issues:
        NX-791 (CPU Count DCI not supported on HP-UX)
        NX-1440 (After netxmsd restart custom schedule DCIs does not have value)
        NX-1607 (Primary IP address should not be used for topology if it is not present on any interface)
        NX-1768 (Server configuration variable Objects.Interfaces.UseAliases has no options to select)
        NX-1773 ("Apply policy" in context menu of node is meaningless and does nothing)
        NX-1803 (Configuration import with "Replace existing object tools" checkbox set does not replace them)

Best regards,
Victor

Since version 3.2 NetXMS we start adding support for EtherNet/IP communication protocol (https://en.wikipedia.org/wiki/EtherNet/IP). This message merely indicates that server cannot connect to device on EtherNet/IP TCP port (44818 by default) - which is expected unless you have EIP capable device.

Best regards,
Victor

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