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

selenium client disconnected while waited in queue #438

Open
BlueBlueSummer opened this issue Feb 20, 2025 · 1 comment
Open

selenium client disconnected while waited in queue #438

BlueBlueSummer opened this issue Feb 20, 2025 · 1 comment

Comments

@BlueBlueSummer
Copy link

Hi,
I frequently get following error when opening url
selenium client disconnected while waited in queue

And I cannot find any detail logs, also I tried to find loglevel in moon2, but no luck.
I checked the cpu/mem usage in moon2, is in low state.

image: 'quay.io/aerokube/moon:2.3.6'
imagePullPolicy: IfNotPresent
name: moon
ports:
- containerPort: 4444
protocol: TCP
resources:
limits:
cpu: 500m
memory: 256Mi
requests:
cpu: 125m
memory: 256Mi

As for browsers, we have enough nodes to hold them, no idea why this disconnection happens, my moon2 helm chart version is 2.3.7

@artashova
Copy link

Hello, I would like to add to this issue that we have the same error message (both for selenium and playwright) in the newer Moon version 2.7.2.
Also, according to Moon logs (please see attachments), the browser was opened successfully and quite fast (in 3 seconds), but the client (our application) never received the response from it. In nginx and app I only see correct error messages, that they were disconnected after 3 minutes because of timeout.
This happens sporadically (1 session out of 30-50), and seems to be independent of load.

chromium-playwright.log
moon.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants