NetXMS Support Forum

No, they are not. Put // in front of each line.

Best regards,
Victor

It hangs in same place. It looks like zlib bug, for deeper debugging we need actual data being compressed. As a workaround you can try to disable NXCP compression for client sessions by commenting out lines 1894 and 1895 (should looks like

            m_dwFlags |= CSF_COMPRESSION_ENABLED;
            msg.setField(VID_ENABLE_COMPRESSION, true);

in src/server/core/session.cpp and recompile server.

Best regards,
Victor

Я скорее всего разобрался (на днях отвечал в английском форуме). Мне удалось повторить у себя эту ситуацию и исправить. В 2.2.8 должно работать.

Just found the place. Seems that server enters infinite loop deep within libz (compression library). Check if new version is available. Also, you can try to rebuild server with configure option --with-internal-zlib.

Best regards,
Victor

Are you sure that CPU usage was high when you capture this dump? I see lot of locks inside (that could be an indicator of another problem) but cannot find anything that can cause high CPU load.

Best regards,
Victor

Hi,

do you want to do those actions manually? If yes the your configuration seems to be correct. Do you get any output from your tool?

Best regards,
Victor

Hi,

this is simple nxshell script that do what you need:


import csv, sys

w = csv.writer(sys.stdout, dialect='excel')
w.writerow(['name', 'ip', 'type']) # Header

for node in [o for o in s.getAllObjects() if isinstance(o, objects.Node)]:
    enabled = node.getCustomAttributes().get("RANCID_ENABLED")
    if enabled != None and int(enabled) == 1:
        w.writerow([
            node.getObjectName(),
            node.getPrimaryIP().getHostAddress(),
            node.getCustomAttributes().get("RANCID_TYPE")
        ])


You can find more information about nxshell here: https://wiki.netxms.org/wiki/Using_nxshell_to_automate_bulk_operations

Best regards,
Victor

Hi,

I was able to reproduce and fix this issue. Fix will be included into 2.2.8 release.

Best regards,
Victor

Hi,

sorry, I forgot to attach script. Now it's attached. Script expects netxmsd to be in your PATH. If it is not, change 'netxmsd' in script's second line to full path to netxmsd.

On Centos you likely build NetXMS from sources - then debug information is embedded into binaries. You only have to install gdb package if not installed already:

yum install gdb

Best regards,
Victor

Hi,

I was able to reproduce this issue and fixed it in current development branch. Fix will be included into next release.

Best regards,
Victor

Hi,

it seems that trap OID is different for version 1 and versions 2-3. For version 1 it is .1.3.6.1.4.1.2589.1.2.0.8 and version 2 it is .1.3.6.1.4.1.2589.1.2.8
(no .0 before last element). I'm not sure if it is NetXMS bug in parsing trap PDUs or device bug - will check that further. Anyway you just need to create second mapping with v2/3 OID and it will work.

Best regards,
Victor

Hi,

please do the following:

1. Enter

debug client.* 6

in server console. This will turn on debug of incoming client requests.

2. Connect with console and wait for CPU to go up.

3. Capture threads using attached script (you should have gdb and all relevant netxms-*-dbg packages installed).

Send me thread dump (will be in /tmp) and server log file (part for the duration of client session).

Best regards,
Victor

Hi,

I assume those nodes does not have SNMP nor NetXMS agent. In that case server relies on ARP caches to find MAC addresses for corresponding IP addresses - so it need access to some device(s) where those IP addresses are in ARP cache. Check that NetXMS server has SNMP access to your core switch and that it can read ARP table from that switch.

Best regards,
Victor

Hi,

Do you have any service checks below node link? They are needed to do actual service status calculation. If you have at least one, check it's status. If it's unknown most likely you have an error in check script.

Best regards,
Victor

Hi,

response time 10000 means "unreachable". Are you sure that devices will respond to ICMP ping from node with agent?

Best regards,
Victor