webrtc / KITE

KITE is a test engine designed to test WebRTC interoperability across browsers
Apache License 2.0
468 stars 126 forks source link

Unable to invoke chrome browser in Linux using putty #146

Closed kavyasetty456 closed 4 years ago

kavyasetty456 commented 4 years ago

Hi,

I am working in Linux system using putty and I am able to connect as a node where as hub is in other system(Windows). When I am running the command to run my script, it is not able to invoke the chrome browser. Please find images below for better understanding,

linuxusingPutty

And for your information I also checked the google chrome in that location(/usr/bin) it is available and working

NodeinPutty

Above image is putty terminal which is showing chrome started sucessfully.

Note: Working fine with out any issues if the Ubuntu system is not running on the server side (GUI available)

What is the issue if I use graphical terminal program(putty) unable to invoke browser?

Thanks Kavya Polisetty.

namvuCosmo commented 4 years ago

Hi,

Can you try running in headless mode:

    {
      "browserName": "chrome",
      "platform": "LINUX",
      "headless": true
    }
kavyasetty456 commented 4 years ago

Yeah just now I tried with headless mode but getting same error.

namvuCosmo commented 4 years ago

Hi, sorry for the late reply, I've been quite busy last couple of weeks.

Do you still facing this issue?

Can you tell me how you're setting the grid, which commands did you use to put up the node, with which version of chrome & chromedriver?

Can you also include your config file you're running the test with?

just in case you want to give this a try, you can also specify the location for the chrome binary and chromedriver like this (84 is currently the stable version):

java -Xmx4G -Dwebdriver.chrome.driver=/home/ubuntu/chrome84/./chromedriver  -jar selenium-server-standalone-3.141.59.jar -role node -hub http://hub_ip:4444/grid/register -maxSession 3 -browserTimeout 300 -sessionTimeout 86400 -port 4447 -remoteHost http://node_ip:4447 -browser browserName=chrome,version=84,platform=LINUX,maxInstances=3,chrome_binary=/home/ubuntu/chrome84/chrome
kavyasetty456 commented 4 years ago

Yes I am still facing the same issue.

For connecting as a node I am using: java -jar /home/Nodesetup/selenium-server-standalone-3.141.59.jar -role node -maxSession 5 -port 6001 -host localhost -hub http://HUB IP address:4444/grid/register -browser browserName=chrome,version=83,platform=LINUX,maxInstances=5 --debug

Hub: @echo off setlocal title Hub java -cp ";../;." org.openqa.grid.selenium.GridLauncherV3 -role hub --debug -host localhost -capabilityMatcher io.cosmosoftware.kite.grid.KiteCapabilityMatcher endlocal pause

*Chrome and Chrome driver version=83

Config file:

{
"name": "WebTesting",
"callable": true,
"grids": [
    {
        "type": "local",
        "url": "http://Hub_IP:4444/wd/hub"
    }
],
"tests": [
    {
        "name": "AddParticipant %ts",
        "tupleSize": 1,
        "description": "Initiate call",
        "testImpl": "org.webrtc.kite.sample.test.Add",
        "payload": {
            "takeScreenshotForEachTest": true,
            "meetingDuration": 60
        }
    }
],
"clients": [
    {
        "browserName": "chrome",
        "platform": "LINUX",
        "useFakeMedia": true,
                    "headless": false,
                    "technologyPreview": true

    }
]

}

Sure will make a try with 84 version(Chrome browser and driver) and let you know But I don't think its the problem with chrome browser or driver version as it is working fine when I am using Unix system with out Putty terminal.

namvuCosmo commented 4 years ago

In your node command, I don't see the part regarding the chrome driver.

Before -jar, you need to have -Dwebdriver.chrome.driver=path/to/chromedriver. Please take a look at the command I wrote above.

namvuCosmo commented 4 years ago

closed due to no activity