NetXMS Support Forum

Hi,

I just fixed it. Fix will be included into next release.

Best regards,
Victor

Most likely you are trying to delete event itself, which is not possible, because it is system event. I was talking about processing rule (go to Configuration -> Event Processing policy, and look for SYS_TUNNEL_SETUP_ERROR in rule conditions - there will be rule that generates alarm from that event).

Best regards,
Victor

Then it looks like some agents or even unrelated to NetXMS application attempts to connect to port 4703. Most likely can safely ignore this. To avoid spamming disable or delete EPP rule that process SYS_TUNNEL_SETUP_ERROR event. Alternatively, you can block access to port 4703 on firewall.

Best regards,
Victor

Are you actually using agent tunnels? Usually this error indicates problem with server certificate or one of trusted CA certificates.

Best regards,
Victor

Мне хочется его доделать, просто руки не дошли пока. Постараюсь найти время в ближайшую неделю.

Quote from: sds on June 02, 2021, 09:23:53 AM
Только потом не получается удалить нарисованную связь. Приходится удалять узел с линком с карты, а потом добавлять его назад

Можно выделить сам линк на карте, и правой кнопкой мыши на нем вызвать меню, там будет пункт "remove". Главное попасть в линк чтобы именно он выделился.

Еще если выделено два объекта на карте, томожно нажать на клавиатуре CTRL + L вместо нажатия иконки вверху.

Quote from: sds on June 02, 2021, 09:11:42 AM
After upgrading to version 3.8.2, the server for some nodes began to issue the error "Error setting up agent tunnel from ... (Cannot configure TLS context)". It is issued for client computers with agents of different versions.
How can this be fixed?

You should check server log for more details (turn on debug level 7 for tag agent.tunnel.* if needed). Most likely you had those tunnels before, in version 3.8.382 we just have added event and alarm for those cases.

Best regards,
Victor

Quote from: lweidig on June 01, 2021, 11:49:33 PM
An update to my last post, decided to live on the edge and run nxdbmgr -X upgrade which resulted in:

Code Select Expand

# nxdbmgr -X upgrade
NetXMS Database Manager Version 3.8.382 Build 3.8-382-gc0100d1389 (UNICODE)

Upgrading database...
Upgrading from version 38.16 to 38.17
SQL query failed (Duplicate column name 'rule_description'):
ALTER TABLE alarms ADD rule_description varchar(255)
SQL query failed (Data too long for column 'rule_description' at row 75):
UPDATE alarms SET rule_description=(SELECT REPLACE(REPLACE(REPLACE(REPLACE(comments, ?, ' '), ?, ' '), ?, ' '), '  ', ' ') FROM event_policy WHERE event_policy.rule_guid=alarms.rule_guid)
Database upgrade succeeded

Server now starts, but concerned what the long term impact of this might be...

Should be no long-term impact. Some existing alarms will be missing rule description, but nothing more.

Best regards,
Victor

Terminated alarms are kept in alarm log and cleaned by housekeeper (by default after 90 days, this period can be changed). You can access them via "Alarm Log" view or directly in database.

Best regards,
Victor

Автоматическое обнаружение в такой ситуации будет работать только если создать отдельную зону и указать агент как прокси этой зоны.

Hi,

I suppose that smtp.office365.com will require authentication, which is not supported by built-in SMTP sender. Easiest way is to install mail forwarder on same machine, configure NetXMS server to send mails to 127.0.0.1 and then forward everything to smtp.office365.com with proper authentication and encryption There are multiple SMTP relays available for Windows. Quick search reveals post for dealing with exact same problem (sending mail to office365 from software that can only do plain SMTP): https://xo.tc/simple-windows-smtp-relay.html

Best regards,
Victor

Hi,

this is bug NX-1964: https://track.radensolutions.com/issue/NX-1964. It is fixed in development branch, but not in version 3.8. In the meantime, create user and database manually and choose to initialize existing database in installation wizard.

Best regards,
Victor

It has to be done on per-node basis. However, you can use configuration poll hook script to automatically disable it on all or selected nodes. To disable routing table poll on all nodes add the following line to library script Hook::ConfigurationPoll:

$node->enableRoutingTablePolling(false);


Best regards,
Victor

Hi all!

We just published minor patch release for version 3.8 - 3.8.382. Changes since previous patch release:

- New method "enable8021xStatusPolling" in NXSL class "Node"
- Linux agent reports correct MTU for interfaces
- Data view created for report execution only if explicitly requested in report properties
- Fixed database upgrade issue on Microsoft SQL Server
- Fixed issues:
        NX-2048 (More information in System.Services table)
        NX-2052 (nxdbmgr cannot drop orphaned TDATA tables created by older server versions)

Best regards,
Victor

Hello, everyone.

Now we also post project-related news and articles on LinkedIn. Feel free to visit product page https://www.linkedin.com/products/raden-solutions-netxms/ or company page https://www.linkedin.com/company/raden-solutions/.

Please follow us there!