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
No matter the issue, the end result is that the python agent will attempt to connect to the socket, fail, and ultimately stop trying after a few attempts. We'll start by tracking when the connection attempts are exhausted.
The current code setup means that the CoreAgentSocketThread won't be involved in any of the errors you listed there, so it's not the right place to add this logging.
The right place is inside CoreAgentManager.
#482 tracks moving the download under the thread, to avoid blocking application startup. I will look into that as a follow-up of this.
What
We'd like to track socket connection issues with the core agent so we can identify issues and fix them proactively.
Why
The socket connection might fail for multiple reasons, which might include
core_agent_dir
core_agent_socket
pathnoexec
is set on the volume wherecore_agent_dir
residescore_agent_dir
resides on a bind mount inside a docker container on an OSX host and creating a socket results in aname too long
error. Can't run swarm tests in Docker for Mac moby/moby#23545 (comment)No matter the issue, the end result is that the python agent will attempt to connect to the socket, fail, and ultimately stop trying after a few attempts. We'll start by tracking when the connection attempts are exhausted.
How
POST
tohttps://checkin.scoutapp.com/apps/diagnostics.scout
?key=#{org_key}&name=#{app_name}
The text was updated successfully, but these errors were encountered: