Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Victor Kirhenshtein

#1591
Announcements / Re: NetXMS 2.2.7 released
August 16, 2018, 12:12:39 PM
Hi,

could you describe your issue in more details (preferably with configuration and result screenshots) in separate topic or in bug tracker ticket? It could be issue that was solved or it could be completely different bug.

Best regards,
Victor
#1592
Добавьте ?lang=en к URL.
#1593
Try to run configuration poll manually (right click on node, Poll, then Configuration). Check what agent will report.

Best regards,
Victor
#1594
Hi,

check agent configuration file - it should have correct log settings and correct management server address in MasterServers. You can also tun agent in foreground with maximum debug as

nxagentd -D9

and check what is going on.

Best regards,
Victor
#1595
General Support / Re: NetXMS CPU Usage High
August 10, 2018, 01:54:43 PM
No, they are not. Put // in front of each line.

Best regards,
Victor
#1596
General Support / Re: NetXMS CPU Usage High
August 10, 2018, 11:11:46 AM
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
#1597
Я скорее всего разобрался (на днях отвечал в английском форуме). Мне удалось повторить у себя эту ситуацию и исправить. В 2.2.8 должно работать.
#1598
General Support / Re: NetXMS CPU Usage High
August 09, 2018, 03:53:09 PM
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
#1599
General Support / Re: NetXMS CPU Usage High
August 09, 2018, 03:30:58 PM
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
#1600
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
#1601
General Support / Re: Netxms rancid export script
August 09, 2018, 02:34:52 PM
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
#1602
General Support / Re: Discovery of MAC addresses
August 09, 2018, 02:24:00 PM
Hi,

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

Best regards,
Victor
#1603
General Support / Re: NetXMS CPU Usage High
August 09, 2018, 12:15:06 PM
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
#1604
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
#1605
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