Skip to content
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

[🐛 Bug]: Could not start a new session. Response code 500. Message: Failed to read marionette port #2020

Closed
diemol opened this issue Nov 22, 2023 · 4 comments · Fixed by #2018

Comments

@diemol
Copy link
Member

diemol commented Nov 22, 2023

What happened?

When using any of the Firefox images and a random user ID (not the seluser ID in Ubuntu), session creation fails and GeckoDriver responds with "Failed to read marionette port".

Command used to start Selenium Grid with Docker

docker run --user 24397 -d -p 4444:4444 --shm-size="2g" selenium/standalone-firefox:4.15.0-20231122

Relevant log output

Could not start a new session. Response code 500. Message: Failed to read marionette port

Operating System

Any of them

Docker Selenium version (tag)

4.15.0-20231122

Copy link

@diemol, thank you for creating this issue. We will troubleshoot it as soon as we can.


Info for maintainers

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!

@diemol diemol pinned this issue Nov 22, 2023
@VietND96
Copy link
Member

This issue is fixed together with PR #2018. Test NodeFirefox images with random user (true) is added back

@diemol
Copy link
Member Author

diemol commented Nov 27, 2023

Thank you!

Copy link

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.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants