TLS_OPEN slowed down controller
thomas.jud
Posts: 46
TLS_CLIENT_OPEN(4, 'my.hostname.com', 443, 1)
If I open a TLS Client and the Host "my.hostname.com" is not reachable but the dns server resolve the hostname, the controller queues all messages and slowed down for a while with this messages:
Anyone experience with this message?
12 2025-04-05 (21:46:40): Length Agenda File Buf 5140
13 2025-04-05 (21:46:40): Length Orig File Buf 5140
14 2025-04-05 (21:46:40): Connecting..
15 2025-04-05 (21:46:40): CA Path is factory path /usr/local/ssl/certs/
16 Line: tls_send() ERROR, no session
17 Line: tls_send() ERROR, no session
18 Line: tls_send() ERROR, no session
19 Line: Certificate validation disabled
20 Line: CIpEvent::Online 0:4:1
18 Line : SocketMan IP threshold reached, threadTCPRead pended...too many messages in queue
19 Line : SocketMan IP threshold reached, threadTCPRead pended...too many messages in queue
20 Line : SocketMan threadTCPRead resumed
21 Line : SocketMan IP threshold reached, threadTCPRead pended...too many messages in queue
22 Line : SocketMan IP threshold reached, threadTCPRead pended...too many messages in queue
23 Line : SocketMan threadTCPRead resumed
24 Line : SocketMan IP threshold reached, threadTCPRead pended...too many messages in queue
25 Line : SocketMan IP threshold reached, threadTCPRead pended...too many messages in queue
26 Line : SocketMan threadTCPRead resumed
and so on......
and so on......
and so on......
Comments
what firmware are you using? IF it is 1.8.190:
v1.8.200 Hotfix: https://help.harmanpro.com/nx-master
The v1.8 is not the final wisdom.... If you don't need features of the v1.8 (like TLSv1.3), I still prefer the v1.6....
Here you can find the last version of v1.6, v1.6.205:
https://help.harmanpro.com/NX-DVX-X2XX-Switcher-Web-Page-Flash-Fix-Firmware
IMPORTANT: If needing to downgrade from any 1.8.xxx version to any 1.6.xxx version, you must disable Authentication on Server Ports on the General tab of the Webgui prior to downgrading. After downgrade, you will need to do a reset factory to properly reset the password paths. This will also re-enable the security. Then reload your code.
Without disabling that security, after the downgrade you can't login any longer, and so you can't do the factory reset by console. In that case, the reset has to be done by the ID button on the controller, which is a little bit tricky.
We use Version 1.6.205
I think thats in combination with the DNS problems. If the controller should see a DNS Server and cannot resolve an adress, the controller no longer responds properly.