NetXMS Support Forum

We just published updated agent for Windows (version 3.9.446). This agent version correctly reports operating system name when running on Windows 11 and Windows Server 2022.

Best regards,
Victor

Then most likely netxmsd process cannot create raw sockets. You can grant it with command

sudo setcap cap_net_raw=ep /usr/bin/netxmsd

(use actual path to netxmsd)

Best regards,
Victor

Hi,

unfortunately it is a limitation inside executeSSHCommand function implementation. I've added issue to fix it: https://track.radensolutions.com/issue/NX-2200

Best regards,
Victor

Currently it is not possible. I think we should add SSH probe as part of configuration poll and handle it in a same way as SNMP credentials. It will also allow to generate relevant event when SSH is no longer responding.
You may also try SSH authentication with private key - depending on your procedures it could be easier to just distribute key for NetXMS server once.

Best regards,
Victor

What OS it is? If possible, please provide output of ifconfig -a for Linux or ipconfig /all for Windows.
Do you have NetXMS agent also running on the server? If yes, please provide output of command
nxget -l 127.0.0.1 Net.InterfaceList

Best regards,
Victor

Hi,

yo have to restart Windows service named "NetXMS Core".

Best regards,
Victor

Hi,

on what OS server is running? If Linux, do you run it under root or under dedicated account?

Best regards,
Victor

So, after more digging and experimenting, it looks like a bug in libssh (that one: https://github.com/ParallelSSH/ssh-python/issues/23, https://bugzilla.redhat.com/show_bug.cgi?id=1849069), said to be present in libssh versions up to 0.9.5. I've tested agent with libssh 0.9.6 and it works stable as expected. Master branch behaves a bit better with older libssh because of different timing (caused by internal structure changes), but still runs into this error periodically.
Unfortunately, Ubuntu 20 comes with libssh 0.9.3, and I suppose they will not update it to 0.9.6 or newer. I will add workaround for that bug (interpret remote channel closure as success if some data was received before), that should fix it for our purposes.

Best regards,
Victor

Hi,

I did some more accurate testing and it seems to be my failure - I manage to get same error with agent 3.9, but it works fine if built from master branch. So looks like we already fixed something, I just have to find out what exactly

Best regards,
Victor

Да. Документацию возможно не обновили еще. Для использования нужен portcheck субагент. Он теперь добавляет дополнительные параметры:

TLS.Certificate.ExpirationDate - дата окончания действия YYYYMMDD
TLS.Certificate.ExpirationTime - дата и время окончания действия как UNIX time
TLS.Certificate.ExpiresIn - кол-во дней до окончания действия
TLS.Certificate.Issuer
TLS.Certificate.Subject
TLS.Certificate.TemplateID

Все они принимают 3 параметра: host, port, timeout. Третий параметр можно не указывать.

Документацию возможно не обновили еще. Для использования нужен portcheck субагент. Он теперь добавляет дополнительные параметры:

TLS.Certificate.ExpirationDate - дата окончания действия YYYYMMDD
TLS.Certificate.ExpirationTime - дата и время окончания действия как UNIX time
TLS.Certificate.ExpiresIn - кол-во дней до окончания действия
TLS.Certificate.Issuer
TLS.Certificate.Subject
TLS.Certificate.TemplateID

Все они принимают 3 параметра: host, port, timeout. Третий параметр можно не указывать.

Hi,

make sure that you have automake, autoconf, and libtool installed on your system. Also, 3.3 is fairly old version, I really recommend going with 3.9.

Best regards,
Victor

Hi,

I just configured it on my home Mikrotik routers and it works, so I suspect it has something to do with Mikrotik firmware version. Mine have 7.1.1 and 6.49.1.
I will also check if I can add additional diagnostic to SSH subagent.

Best regards,
Victor

Hi,

isLocalManagement flag is set automatically. I suggest to find node that currently holds management server flag using object query or NXSL script, delete it, then set server configuration parameter RoamingServer to true and change primary IP address on node that should be local management server to 127.0.0.1. That way management node will be fixed.

Best regards,
Victor

Hi all!

We just published new patch release for version 3.9 - 3.9.420. Changes since previous patch release:

- New agent command line option -Q (query values of configuration entry)
- Windows service start mode can be changed from UI
- Improved web API for accessing collected DCI data
- Improved file transfer on slow links
- Fixed bug in network topology discovery
- Fixed issues:
        NX-290 (SSL Certificate expiration check)
        NX-781 (Convert to template item work incorrectly on cluster nodes)
        NX-1032 (Threshold violations are not shown for table DCIs)
        NX-1551 (Multiple execution completion dialogs after executing object tool on container)
        NX-1587 (Fix MySQL error: The 'INFORMATION_SCHEMA.GLOBAL_STATUS' feature is disabled; see the documentation for 'show_compatibility_56')
        NX-2122 (Table DCI last values are not loaded on server start)
        NX-2152 (Map should zoom in relation to mouse cursor, not center of map view)
        NX-2175 (Add hint to SNMP Trap Transformation Script editor)
        NX-2182 (Changing Objects.Nodes.ResolveNames actually requires server restart, but should work without server restart)
        NX-2183 (Daily Email Summary doesn't seem to resolve users properly in "Ack/Resolved by" column)

Best regards,
Victor