-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v2.2.0.16 Docker ARM
] - SHDR in Connector::reader: End of file: End of file
#382
Comments
The other strange observation:
|
The agent is getting an end of file that means the other side has closed the connection. The agent would have logged if it had initiated the shutdown. It occurs right after the first heartbeat, so I wonder if something went wrong on the adapter side. |
Hmmm could be something with the ping pong. I will check. |
Definitely something on adapter side and very Docker and ARM specific. |
This is a non-issue. It was related to the restart sequence of agent and adapter. |
I found something intermittent across installations, but I can reproduce it on my Fanuc simulator (used to work without exception in 2.2.0.3 as that was our last Docker build). I start up agent and then my adapter, I can see the entire SHDR stream on 7878, and it looks like agent sees it as well. But it looks like there is an error. What is the best way to troubleshoot this? I am using https://github.com/TrakHound/MTConnect.NET 5.4.1 as the SHDR adapter. @PatrickRitchie
no eol found, waiting for more characters
The text was updated successfully, but these errors were encountered: