NetXMS 3.8 version 3.8.382

[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

[Matthew-Beckett]

Docker images available - https://github.com/Matthew-Beckett/netxms-dockerfiles/releases/tag/3.8.382

[lweidig]

Received this when upgrading Ubuntu server to 3.8-382:

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)
Rolling back last stage due to upgrade errors...

After I tried to use nxdbmgr upgrade and get:

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)
Rolling back last stage due to upgrade errors...
Database upgrade failed

The netxmsd service will not start now.  This was coming from 3.8-314.

[lweidig]

An update to my last post, decided to live on the edge and run nxdbmgr -X upgrade which resulted in:

# 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...

[sds]

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?

[victor]

@lweidig said in NetXMS 3.8 version 3.8.382:

An update to my last post, decided to live on the edge and run nxdbmgr -X upgrade which resulted in:

# 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

[victor]

@sds said in NetXMS 3.8 version 3.8.382:

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

[sds]

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.
[/quote]

With log level=7:

SocketListener/AgentTunnels: Incoming connection from 172.24.0.101
SocketListener/AgentTunnels: Connection from 172.24.0.101 accepted
SetupTunnel(172.24.0.101): minimal TLS version set to 1.2
SetupTunnel(172.24.0.101): Cannot configure TLS context
CorrelateEvent: event SYS_TUNNEL_SETUP_ERROR id 1743331 source NetXMS server (0.221) [161]
CorrelateEvent: finished, rootId=0
EVENT SYS_TUNNEL_SETUP_ERROR [118] at {0} (ID:1743331 F:0x0001 S:3 TAGS:"") FROM NetXMS server (0.221): Error setting up agent tunnel from 172.24.0.101 (Cannot configure TLS context)

[victor]

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

Best regards,
Victor

[sds]

@victor said in NetXMS 3.8 version 3.8.382:

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

No, not used and not specifically configured

[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

[sds]

Thanks. Temporarily changed the importance of the event to "Normal". I couldn't delete the rule even under the admin account.

[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

[sds]

Thanks. I correct event policy.