NetXMS Support Forum

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

Hi!

Could you please share script you are using? I did some tests and otherwise SSH to Mikrotiks seems to be working.

Best regards,
Victor

Цвет иконки зависит от статуса ноды, можно поменять правила подсчета статуса, чтобы один интерфейс например не загонял ноду в critical.

Currently named capture groups are not supported. Looks like a good idea though, I'll check if we could do that.

Best regards,
Victor

I think I've found logical flaw in topology building code. Will fix it today or tomorrow, next patch release likely will work correctly.

Best regards,
Victor

Next it tries to open second connection to database, which I suppose is not working for SQLite. Do you have any network maps configured?

If you DO NOT have any network maps, you can do this step manually by executing the following queries (it will delete any configured links on network maps):


DROP TABLE network_map_links;
CREATE TABLE network_map_links
(
  map_id integer not null,
  link_id integer not null,
  element1 integer not null,
  element2 integer not null,
  link_type integer not null,
  link_name varchar(255) null,
  connector_name1 varchar(255) null,
  connector_name2 varchar(255) null,
  element_data varchar null,
  flags integer not null,
  color_source integer not null,
  color integer not null,
  color_provider varchar(255) null,
  PRIMARY KEY(map_id,link_id)
);
CREATE INDEX idx_network_map_links_map_id ON network_map_links(map_id);
UPDATE metadata SET var_value='9' WHERE var_name='SchemaVersionMinor';


And then run nxdbmgr upgrade again - it should continue from next step.

Best regards,
Victor

The problem here is that $object for SYS_IF_DOWN points to node object, not interface object. Correct script will look like this:


iface = $node->getInterface($event->parameters[5]);
return iface != null and iface->peerNode == null;


Best regards,
Victor

Hi all!

We just published NetXMS Jira connector version 3.9 which should be compatible with Jira 8. It also supports passwords obfuscated with nxencpasswd.

Best regards,
Victor