Thank you for all the command-line reports, wiley42.
Our server team has checked things on our side, and I can report that there are no server-side issues at the moment. So, we need to focus on why the connection is behaving in this way.
As reflected client-side (your logs), our servers get many data transmission timeouts that can also be seen from all the broken pipeline lines in the logs. This means that the Shake is actively trying to transmit, but then the interruptions you’ve seen happen.
Let’s try this test by checking what happens when the Shakes are connectet singularly:
- Disconnect the 3D and 4D, and leave the Boom on for 24h
- Then disconnect it, and reconnect only the 3D for 24h
- And, last, disconnect that and connect only the 4D for 24h
This is to check if the data volume that the three instruments are trying to update is behind what we are seeing. We already know that the Boom works fine, but it will be interesting to see the result of the experiment above.
Additionally, another element you can check (if you haven’t already) is this.
No trouble at all; you’re more than welcome!