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

Driver not started due to i/o timeout error #939

Open
dmtgrinevich opened this issue Oct 5, 2023 · 2 comments · May be fixed by #940
Open

Driver not started due to i/o timeout error #939

dmtgrinevich opened this issue Oct 5, 2023 · 2 comments · May be fixed by #940
Labels
bug Something isn't working

Comments

@dmtgrinevich
Copy link
Contributor

router_1 | time="2023-10-05T08:57:18Z" level=info msg="Failed to start driver, stopping service..." _taskId=0a42efd2bead446cbd2d560a1d663689 _uuid=339a8ba3-a0b1-4fce-a55d-5ce24d32a093 attempt=0 driver url="http://172.31.66.231:32792/session" error="Post \"http://172.31.66.231:32792/session\": dial tcp 172.31.66.231:32792: i/o timeout" family=dev-linux-edge-112-0 latency=4m39.480084043s remote=3.90.174.150 user=devtests

@dmtgrinevich
Copy link
Contributor Author

dmtgrinevich commented Oct 5, 2023

call to selenoid container (post ../session) for creating a new session
error was returned after 30 seconds
selenoid's default timeout for session creation:

-session-attempt-timeout duration
    New session attempt timeout in time.Duration format (default 30s)

https://github.com/aerokube/selenoid/blob/89ea1c09d2572cdec47f10c865f673fd21a60a30/main.go#L244

@dmtgrinevich
Copy link
Contributor Author

Selenoid would have returned New session attempts retry count exceeded but request doesn't make it to get to the selenoid process stage.
Possible reason: selenoid's container firewall blocking this incoming request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant