NetXMS Support Forum

I suppose you are building from source. Try to do make install again, but before remove directory /usr/local/lib/netxms (and preferably everything from /use/local/lib as well). Then start server under debugger as per this instruction: https://wiki.netxms.org/wiki/Running_NetXMS_under_debugger and post output here.

Best regards,
Victor

Just added two new configuration options for version 3.3: driver blacklisting and switching SNMP probing into one OID per request mode. Either one should fix this issue.

Best regards,
Victor

If log ends abruptly that likely means server process crash. I suggest to upgrade to latest version (3.2.400), and if problem persist we will continue to debug it. There were lot of fixes since 3.1.261, so it is better to try upgrade first.

Best regards,
Victor

You can do full edit if you export dashboard into XML, edit it, and then import back. XML for individual elements can be edited directly from GUI (including layout properties).

Best regards,
Victor

Yes, that should be enough for building topology. Could you set debug level to 6, run topology poll on few switches, and provide server log file along with console output for the poll?

Best regards,
Victor

Another approach would be to set option "this is IP address of remote management node" in communication options.

Best regards,
Victor

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 байт?