node-chrome-debug:2.47.1 xvfb-run: error: Xvfb failed to start #91
Comments
|
I see you run a debug node attached to the hub. Maybe there are timing issues in spinning up a hub and then adding a node... A better way may be to start a The hub plus nodes is a good setup when you need to spin 20 nodes for example because you need to run parallel tests. |
|
I started running into this issue as well using the node-chrome docker image. |
|
I've just hit this, I happened to notice it started when I upgraded to docker 1.8.1 from docker 1.7.1. |
|
Okay, after a bit of fun trying to reproduce and bisect, I've discovered why it's happening. It's actually my docker-compose upgrade that did it, not docker's upgrade. I can reproduce it on both 1.7 and 1.8. The difference is with docker compose 1.4, if you don't use Now that I know this, I'm able to reproduce it without docker-compose. In one window, run this: Then in another: |
|
Anyone with solution to this? I'm having the same problem selenium:
hostname: selenium
image: selenium/standalone-firefox:2.48.2alexander@rincewind:~$ docker-compose -v
docker-compose version: 1.5.1
alexander@rincewind:~$ docker -v
Docker version 1.9.0, build 76d6bc9 |
|
I had the same issue as @alexander-lazarov. I was able to get past this error using |
|
Intermittent "xvfb-run: error: Xvfb failed to start" on selenium/standalone-firefox-debug |
|
I have the same issue with selenium/standalone-firefox, I've tried with different tags and it can be reproduced in all of them. Here are the results of a docker diff on the container, I hope it helps. |
|
The solution for me was to use --force-recreate flag when launching through Docker Compose: "docker-compose up --force-recreate". It forces recreation of containers even if their configuration and image haven't changed. |
|
What I noticed is that if I change the value of |
|
--force-recreate worked for me too, thanks @oholubyev |
|
Ok it's no longer working for me, I start with 1 firefox container but when I try to scale I get the same error, and force recreate changes nothing. |
|
Same issue Docker: 1.10.0 |
|
I couldn't scale above one firefox node, on 5 different servers, because of this issue. For me, it was because of port 4444 conflicting, with all the nodes on the same IP... |
|
Same issue with |
|
I've tested with 2.52 version and the error continues. |
|
We had the same problem with the standalone-chrome-debug image. The image executes the following file /opt/bin/entry-point.sh. It tries to start an xDisplay on port 99.0. After we restarted the image the following lock file was present /tmp/.X99-lock. Because of this file xvfb could not be started. |
|
@garagepoort Can you make a fix in the entry-point.sh and a pull request please? |
|
@caioquirino: based on what @garagepoort shared, using this https://gist.github.com/alexander-lazarov/3851614fdd9ab33a1182 |
|
Hi @alexander-lazarov, |
|
Hi @caioquirino, |
|
I have tested @garagepoort fix and that worked well. |
|
My pull request has been merged and included in release 2.53.0. This issue can be resolved? |
|
I have this on 2.53.0 firefox-debug (2.53.0 selenium-grid) docker v1.10.3 related? same? new issue? Chrome loads fine. I have also tried --force-recreate flag a few times... ignore - my issue looks to be this #208 |
|
@garagepoort I just had the same issue with |
|
@aleshaczech Ok I'll create a pull request for them all. |
|
@garagepoort I can reproduce the error event on selenium/standalone-chrome-debug:2.53.0. Here's the output of ./opt/bin/entry_point.sh call: My docker version is 1.11.1, build 5604cbe. Could you please give me some hints how to make it work? |
|
I have the same issue as @kchudy and I think it is caused by this line In this case, This is my workaround in docker-compose.yml |
|
@xlc nice observation. To the developers: what is that code trying to do? I interpret that it's passing the root environment through, but just for variables which are set in the |
…start xvfb. The issue is documented here: SeleniumHQ#91 Looks to be an problem with the lock files preventing a restart intermittently. Adding a line here to remove the lock files on startup.
|
@adamlievrouw This is inside the container. Why would the host lock the X-server? |
|
Was experiencing this issue on selenium/standalone-chrome-debug and selenium/standalone-firefox-debug latest. Current workaround based on xlc's solution seems to cover both issues. Just added this to my docker-compose. |
|
So I deleted the container and image for selenium/standalone-chrome-debug. Container still has exited with 127. See docker ps -a results below. Thought this was fixed in latest CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES docker logs -f 5af24880c451 |
|
I have the same problem with @nuggit32 , I hope someone can give some advise. |
|
Same error with this configuration: selenium-hub:
container_name: selenium-hub
image: selenium/hub:2.53.0
ports:
- "4444:4444"
selenium-chrome:
image: selenium/node-chrome-debug:2.53.0
environment:
- HUB_PORT_4444_TCP_ADDR=selenium-hub
- HUB_PORT_4444_TCP_PORT=4444
links:
- selenium-hub
ports:
- "5900:5900"switching to |
|
#256 the pull request must fix it... make sure the VNC password is set by the seluser but the bug was, that root was setting that and seluser failed to access it and this failed.... |
|
I use your @gurukiran007 code and then it work well. Thank you very much for fixing it. |
|
Issue still happens for me Mac mini ( 10.10.5 ) with docker 1.12.1 ( build: 121333) + selenium debug version 2.53.0 |
|
Got this working with below command docker run -d -P -e no_proxy=localhost -e HUB_ENV_no_proxy=localhost --link selenium-hub:hub selenium/node-chrome-debug |
…start xvfb. The issue is documented here: #91 Looks to be an problem with the lock files preventing a restart intermittently. Adding a line here to remove the lock files on startup. Signed-off-by: Daniel Davison <daniel.jj.davison@gmail.com>
|
This seems to happen because the in That should stop it from getting cached, right? |
|
Funny thing:
|
|
@Loki-Afro you can avoid this error like this: To restart the container: To stop the container: |
|
Where is the Cache stored in any chrome docker containers? i want to clear the cache and cookie after every test and rerun the test only after cleaning up the cache and cookies currently using /selenium-chrome-node:54.0.0 container I am looking for cache /opt/google/chrome , dont see anything in the directory? |
|
Is this what you're looking for?
|
|
what I am trying to do is run a test on a chrome node (access my internal web app) which caches some content in the chrome node. however when i run the above command
|
|
I'm not sure if it's useful, but I use this in many of my selenium scripts to achieve what your talking about.
|
|
The following bug, signaled above, occurs only on Docker4Mac (and not on Docker4Windows) even when a proxy is not specified at the Docker Engine level: This is due to the default value of the Exclude textfield of the Advanced pane of Docker4Mac settings which is greyed out initially but nevertheless taken into account by the Docker Engine. One can see it using this simple command: If this value is changed to a single space character, the no_proxy variable disappears: => it is a docker4mac bug |
|
Thanks @ecirtap, you saved me a lot of time. |
|
This is mac specific - If you run into the same error change the proxy setting on docker service on a mac change the proxy settings to "No Proxy" - it should fix the xvfb issue.
|
|
It seems that also |
|
@punitmishra funny thing that I don't have that radio button on mac :D |
|
@ivycas Getting the selenium images to work in docker-compose, good. I'm stuck trying to get them working in Codeship, a bit more restrictive. Also fancy seeing one of your comments here! |
|
For those who might still face this issue: If you try to run multiple nodes with the docker networking mode set to |
|
@ejoebstl Actually it's codeship which uses a bridge network always. |
and others
I have the following setup in a docker-compose.yml:
when I launch my test, I often receive the following error from the logs of the chrome container:
xvfb-run: error: Xvfb failed to startand my test runner (nightwatchjs) says:
Error retrieving a new session from the selenium server { status: 13, value: { class: 'org.openqa.grid.common.exception.GridException', message: 'Error forwarding the new session cannot find : Capabilities [{platform=ANY, acceptSslCerts=true, javascriptEnabled=true, browserName=chrome, name=Evaluator Login, chromeOptions={args=[--no-sandbox, --window-size=1400,1100, --lang=de, --disable-web-security]}}]' } }When I connect with VNC to the container previous to running the tests, it works 100% of the time. However, I want this to be part of the CI process, so it also has to run unattended. Any ideas? Thanks, Marcelo
The text was updated successfully, but these errors were encountered: