Yes use of the Lexicon support solved my issues too. Though I fear that the issues might arise again. I hope I am wrong
For what it is worth, I use TLS to make secure connections to a cloud server to obtain propane usage data and also to a weather service to obtain current weather and forecast data. I too get the TLS/SSL_read syscall failure error every time I connect to the servers and obtain data. It does not however seem to have any negative effect since I am able to open the connection, obtain all of the desired data, and then close the connection. Below is a log file sample that illustrates the error when obtaining data from a TLS connection to the weather server. Similar log entries exist for the propane usage cloud server as well. Log entries with 'RSS Weather Module: ' are from my module -- remaining log entries are generated by Netlinx internally.
Line 99 2019-01-28 (15:12:34):: RSS Weather Module: TIMELINE event (DarkSky) - opening connection to obtain weather current conditions
Line 100 2019-01-28 (15:12:34):: CA Path is factory path /usr/local/ssl/certs/
Line 101 2019-01-28 (15:12:35):: Certificate validation disabled
Line 102 2019-01-28 (15:12:35):: CIpEvent::OnLine 0:29:100
Line 103 2019-01-28 (15:12:35):: RSS Weather Module: initiated processing of DarkSky weather current conditions
Line 104 2019-01-28 (15:12:36):: RSS Weather Module: completed processing of DarkSky weather current conditions
Line 105 2019-01-28 (15:12:36):: Closing SSL connection as requested by NetLinx for idx 5, fd=165 api.darksky.net
Line 106 2019-01-28 (15:12:36):: TLS/SSL_read syscall failure. Error: 5/0/(null)
Line 107 2019-01-28 (15:12:36):: SSL Shutdown end of read
Line 108 2019-01-28 (15:12:36):: CIpEvent::OffLine 0:29:100
It seems to be an internal Netlinx error that only occurs with TLS connections and data retrieval but as I said above, at least in my case, it does not have any negative impact on the modules and seems to work fine. In both cases, HTTP get requests are sent to the servers to authenticate and request data and JSON data is returned and parsed accordingly.
I have tried with Chrome and Firefox navigators and in incognito mode. Here's a pic of the view:https://drive.google.com/open?id=0B8-6lU7xfbXCd3hFRkJJVE15dWN5QnRnN05uWkw5NWd2eVRN
If you haven't reached out to the RMS team here in Support, please do.
Given the information you have, this could be either a booking/message is stuck in the troller_message table in the SQL DB or one of the meetings is corrupted/has an issue and is causing the troller to choke.
I tried that but never received an answer. I meanwhile contacted the german distributor
AUDIO PRO HEILBRONN Elektroakustik GmbH.
They were very helpful and friendly! I am a happy owner again.
Did anyone solve that issue meanwhile? I have the same problem here for a couple of days now. Sometimes I am getting it to run after a couple of minutes. On other days it just does not work forever. I love that desk and my whole studio is dependent on that console. I have the pops, the FX are not selectable and the the Mixer does not appear in the Audio/MIDI setup. It's not a MAC issue. I have the same problem when running bootcamp and windows 7.
In windows you can see that the device manager updates the devices view with each second pop. So the desk fails to init on a USB request I would think. That maybe results in FX init as well as the sample rate jumps between internal and external control. (just an idea)
BTW.: I am the guy who did one of the most popular Soundcraft Signature MTK videos on youtube. I really love the console and are looking forward to get it to run again.
We used Atlona products for years and found them reliable and sturdy. Tech support is generally quick and comprehensive. That said, we stopped using their HDMI switches 2 years ago when we had HDMI issues.
Specifically, we found that a number of TV's, including LG OLED units that comprise the majority of new installs, do not keep their HDMI handshake alive when turned off (probably due to that damned Green rating). And the Atlona switches we were using would presume that there was no device on the output, so it "helped" us by ignoring switching commands to feed said outputs. With no visible error. And once so ignored, it might or might not ever send anything to that output again even if the TV woke up and again was willing to handshake. To correct it, a reboot of the Atlona HDMI switch was required. Which could not be done from the front panel - a hard AC removal was required. Which was madness for rack mounted systems.
Atlona finally supplied us with their EDID emulator ($250 each) for each of the sites affected. And we stopped installing more of them, and tried other vendors. Which each, it turns out, has new and fascinating ways of treating HDMI handshakes poorly.
I talked at length with Atlona support and product folks about the two issues - ignoring commands and locking up outputs without notice on the front panel, and the inability to recover from the front panel. They saw my points and suggested that newer products would have this looked at... I don't know if they made any changes since. They were acquired by PANDUIT and it looks like decisions aren't entirely local anymore.
Just yesterday we installed another LG OLED at an Atlona site that required the emulator to stay working. We didn't install an emulator, and the TV appears (so far) to not exhibit the offline behavior that was 100% repeatable with the 3 year old OLED and 3 year old Atlona we struggled with before. So maybe LG is now keeping the handshake in new models? Time will tell.
I very much like Atlona, their prices, and their support (we're actually only 5 miles from their main offices). After struggling with alternatives, we are likely to try them again.
Yes, just had to reset my password before I could log in. It did send a password reset e-mail though. After using a new password, I'm back in.
Back. Thanks, Rob!
@richardherman You may need to configure/adjust the firewall settings for NSX. With HTTP transfers NSX acts as a server so any outbound connections blocked through the firewall won't work.
As you might notice in the release notes I'm trying to implement some things not only needed for developers but also some things that might be wanted, such as allowing fonts with ligatures. (At the very least, I'm "sneaking" in things that I find useful, helpful, neat, cool, etc. in each release), but priority is always to make sure the core functionality works and this was a big one. I know it's a pain to update via USB - been there, done that too much in the past.
If we can't get it to work for you by disabling the firewall then please be sure to reach out to tech support so a ticket can hit my desk and look into it.