Closed e-dsouza closed 1 month ago
@e-dsouza, thank you for creating this issue. We will troubleshoot it as soon as we can.
Triage this issue by using labels.
If information is missing, add a helpful comment and then I-issue-template
label.
If the issue is a question, add the I-question
label.
If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted
label.
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable G-*
label, and it will provide the correct link and auto-close the
issue.
After troubleshooting the issue, please add the R-awaiting answer
label.
Thank you!
It is looking for a local Otel backend to push trace due to tracing is enabled by default.
To disable it, set SE_ENABLE_TRACING=false
@VietND96 Thank you for the response. I added SE_ENABLE_TRACING: 'false' to ConfigMap, it did remove the ERROR: Failed to export spans. The request could not be executed. Error message: Failed to connect to localhost/[0:0:0:0:0:0:0:1]:4117, from Chrome, Firefox and Edge nodes however it had no impact on hub container(image: selenium-hub:4.25.0-20240922), I still see the error in log.
If you are adding to ConfigMap, ensure that all component containers should refer to that CM. Since every component will send its traces data separately.
If you are using Helm chart delivered in this repo, just to set tracing.enabled: false
okay, the hub yaml didnt have configMap configuration in it. Thank you.
Hello @e-dsouza @VietND96
I am also facing similar issue. In my case I am getting this error: 11:56:51.331 ERROR [ThrottlingLogger.doLog] - Failed to export spans. The request could not be executed. Error message: Failed to connect to localhost/127.0.0.1:4317 java.net.ConnectException: Failed to connect to localhost/127.0.0.1:4317 at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.kt:297) at okhttp3.internal.connection.RealConnection.connect(RealConnection.kt:207)
Since you have mention about the configMap, I guess you are using K8s for running the cluster. But in my case, I am using the ECS fargate which is using the Task Definition for defining the container configuration.
Can you please confirm where exactly in you Config Map you did the modifications. So, that I can update the same changes i n the Task Definition file that I am using!
Hi, if not using K8s, you can directly set env var SE_ENABLE_TRACING=false
to all components (in docker compose or docker command).
If Task Definition
has the concept to share common config across containers, then add a config for env var SE_ENABLE_TRACING
to false
Hello @VietND96 I have added the environment variable SE_ENABLE_TRACING=false in my task definition for both the selenium hub and selenium firefox services. This has resolved the issue for selenium firefox but I am still getting the same error for selenium hub container. Thanks for help!
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
What happened?
When updated hub, chrome, firefox and edge images to 4.25.0-20240922, the OCP containers has following repeatative error in log, however it doesnt seems to be impacting execution
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
Ubuntu
Docker Selenium version (image tag)
4.25.0-20240922
Selenium Grid chart version (chart version)
None