NetXMS Support Forum

Hi,

can you check log on proxy agent around time when SYS_SSH_UNREACHABLE generated? Make sure you have debug level 6 or more for tag "ssh".

Best regards,
Victor

Yes, only first line is taken as value of external parameter. You have to format output in your script so it return required value in first line.

Best regards,
Victor

Hi,

you can try to manually add column tt_row_number to table dct_threshold_instances (integer not null, set it to 0 if you have any records in dct_threshold_instances table), then you can try to run upgrade with -X option (it will ignore upgrade errors and continue). One of next upgrade procedures will try to rename row_number to tt_row_number, so you should end up with correct schema.
Make sure you have database snapshot or backup before trying this, and watch for possible other errors, because with -X DB manager would not stop at them anymore.

Best regards,
Victor

Hi,

you should use $$ to insert $ into command, as it is start of command argument ($1, $2, etc.).

Best regards,
Victor

Hi all!

We just published patch release for version 4.1 - 4.1.333. Changes since previous release:

- Added support for package type "zip"
- Fixed incorrect label colors on dashboards after migration from 4.0
- Minimum number of bytes required for MAC address search reduced to two
- Reading of ipAddrTable and/or ipAddressTable during configuration poll can be disabled via custom attributes
- Fixed server crash caused by incorrect value of configuration parameter ICMP.PingSize
- Multiple fixes and improvements in new UI
- Fixed issues:
        NX-2089 (Bundle prunmgr.exe with web-ui installer)
        NX-2250 (Show VLAN information on interface overview page)
        NX-2258 (No context menu on area of interactive dashboard graphs)

Best regards,
Victor

Is it mean for authenticating NetXMS users, or for use with SSH connections from NetXMS to devices? Because latter is already implemented for some time.

Hi,

yes, it can be done, but it will take some time to move all strings to message files. I will update on progress.

Best regards,
Victor

For L2 maps server consider any node without bridge capability to be end node. Bridge capability determined by attempting to access BRIDGE-MIB during configuration poll (specifically OIDs .1.3.6.1.2.1.17.1.1.0 and .1.3.6.1.2.1.17.1.2.0).

Best regards,
Victor

I've made changes to disable usage of ipAddrTable and ipAddressTable by setting to true attributes snmp.ignore.ipAddrTable and snmp.ignore.ipAddressTable. Those changes will be included into upcoming patch release.

Best regards,
Victor

Hi,

if data in IP-MIB is incorrect that it definitely can cause strange results. Do those devices provide correct address information under .1.3.6.1.2.1.4.20.1.1 (ipAddrTable)? If yes, I can made small change that will allow to disable usage of .1.3.6.1.2.1.4.20.1.1 (ipAddressTable) for specific devices.

Best regards,
Victor

Hello!

This is download link for current message files: https://cloud.radensolutions.com/s/zrYw4jDxcfTbKFG.
However, we are currently in process of moving to new UI, so it could be more productive to work on new UI when most of functions will be transferred. I expect most work to be done during May and early June. We will try to re-use translations from legacy UI as much as possible though.
Also, please note that some texts in UI are not moved to language files yet and are hard-coded as English texts. This is also work in progress.

Best regards,
Victor

Actual code that caused crash looked like this:

   int bytes = request->packetSize - sizeof(IPHDR);
   packet.m_icmpHdr.m_wChecksum = 0;
   packet.m_icmpHdr.m_wChecksum = CalculateIPChecksum(&packet, bytes);


If total packet size < 20, bytes will be negative, which will cause crash within CalculateIPChecksum. With packet size between 20 and 27, result will be positive and CalculateIPChecksum will actually calculate checksum for requested number of bytes, but invalid ICMP packet will be sent (with only part of the header).

Best regards,
Victor

Try to deploy new web under different name - will it have same issue?

Looks like old client version still deployed, or some parts of old version stuck in cache. Try to clear Tomcat working directory.

Best regards,
Victor

Quote from: troffasky on May 12, 2022, 04:18:36 PM
Is it worth bringing these up here?

Yes, absolutely. We will look into it and hopefully fix before next patch release.

Best regards,
Victor