You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have installed the Sumologic collector as a Docker container.
I'm running docker on an EC2 instance on AWS. When this exception shows, I stop receiving logs from only one of the containers on the Sumologic console, this application is a Java server using spring. I can see the logs of this application using the docker logs command.
has there been any progress on the resolution of this issue?
We are also experiencing problems with the same error in the logs on just one sumo logic container on one out of three swarm nodes
Hi
I have installed the Sumologic collector as a Docker container.
I'm running docker on an EC2 instance on AWS. When this exception shows, I stop receiving logs from only one of the containers on the Sumologic console, this application is a Java server using spring. I can see the logs of this application using the
docker logs
command.I keep getting this error:
jvm 1 | Exception in thread "onError:DockerLogManager:0000000001565CB5:'Docker-logs':44" java.lang.RuntimeException: java.net.SocketTimeoutException: Resource temporarily unavailable
Full log (until first time the error shows, then the error keeps repeating):
The text was updated successfully, but these errors were encountered: