Unable to create session on remote device (while it works on local device) #740

ShubhangiShingade · 2023-07-10T10:11:48Z

ShubhangiShingade
Jul 10, 2023

I have a hub and node setup with each running a android simulator.
Both node and hub can access the dashboard, device farm.

However the test fails to create session on remote simulator while it succeeds on local simulator.

[debug] [AppiumDriver@fb34] Calling AppiumDriver.createSession() with args: [null,null,{"firstMatch":[{}],"alwaysMatch":{"platformName":"Android","appium:app":"/Users/shubhangi/Downloads/app-google-mobile-release_4.0.8.0.167159.apk","appium:deviceName":"emulator-5554","appium:deviceOrientation":"portrait","appium:platformVersion":"14","appium:automationName":"UiAutomator2","appium:newCommandTimeout":3000,"appium:appWaitActivity":"com.ixolit.ipvanish*","appium:autoGrantPermissions":"true"}}]
[AppiumDriver@fb34] Plugins which can handle cmd 'createSession': device-farm,appium-dashboard
[AppiumDriver@fb34] Plugin appium-dashboard is now handling cmd 'createSession'
[AppiumDriver@fb34] Plugin device-farm is now handling cmd 'createSession'
{
platformName: 'Android',
'appium:app': '/Users/shubhangi/Downloads/app-google-mobile-release_4.0.8.0.167159.apk',
'appium:deviceName': 'emulator-5554',
'appium:deviceOrientation': 'portrait',
'appium:platformVersion': '14',
'appium:automationName': 'UiAutomator2',
'appium:newCommandTimeout': 3000,
'appium:appWaitActivity': 'com.ixolit.ipvanish*',
'appium:autoGrantPermissions': 'true',
'appium:clearDeviceLogsOnStart': true,
'appium:nativeWebScreenshot': true,
'appium:mjpegServerPort': 56296
}
[device-farm] {"platform":"android","platformVersion":"14","name":"","busy":false,"userBlocked":false}
[device-farm] Waiting for free device
[device-farm] 📱 Device found: {"adbPort":5037,"systemPort":50963,"sdk":"14","realDevice":false,"name":"sdk_gphone64_x86_64\n name: \nnufacturer_name: 0,","busy":false,"state":"offline","udid":"emulator-5554","platform":"android","deviceType":"emulator","host":"http://192.168.1.120:4723","totalUtilizationTimeMilliSec":0,"sessionStartTime":0,"offline":false,"userBlocked":false,"meta":{"revision":2,"created":1688982088944,"version":0,"updated":1688982302731},"$loki":1,"dashboard_link":"http://10.120.75.2:31337/dashboard?device_udid=emulator-5554&start_time=2023-07-10T09:39:12.376Z","total_session_count":0,"newCommandTimeout":3000}
[device-farm] 📱 Blocking device emulator-5554 for new session
[device-farm] Remote Host URL - http://192.168.1.120:4723/wd/hub/session
[device-farm] Creating cloud session
[HTTP] --> GET /device-farm/api/devices
[HTTP] {}
[HTTP] --> GET /dashboard/api/sessions?start_time=2023-07-10T09:39:12.376Z
[HTTP] {}
[HTTP] <-- GET /dashboard/api/sessions?start_time=2023-07-10T09:39:12.376Z 200 3 ms - 47
[HTTP]
[HTTP] <-- GET /device-farm/api/devices 200 50 ms - 1160
[HTTP]
[HTTP] --> GET /device-farm/api/queue
[HTTP] {}
[HTTP] <-- GET /device-farm/api/queue 200 1 ms - 1
...
....
...
[device-farm] 📱 Device UDID emulator-5554 unblocked. Reason: Remote Session failed to create
[AppiumDriver@fb34] Command 'createSession' was not handled by the following behaviours or plugins, even though they were registered to handle it: ["default"]. The command was handled by these: ["device-farm","appium-dashboard"].
[debug] [AppiumDriver@fb34] Encountered internal error running command: TypeError: Cannot read properties of undefined (reading 'data')
[debug] [AppiumDriver@fb34] at /Users/shubhangi/.appium/node_modules/appium-device-farm/lib/plugin.js:174:59
[debug] [AppiumDriver@fb34] at Generator.next ()
[debug] [AppiumDriver@fb34] at fulfilled (/Users/shubhangi/.appium/node_modules/appium-device-farm/lib/plugin.js:5:58)
[debug] [AppiumDriver@fb34] at runMicrotasks ()
[debug] [AppiumDriver@fb34] at processTicksAndRejections (node:internal/process/task_queues:96:5)
[HTTP] <-- POST /wd/hub/session 500 60008 ms - 715

Has anyone encountered this before, if so how did you fix it ?

Thanks,
Shubhangi

saikrishna321 · 2023-07-10T10:44:18Z

saikrishna321
Jul 10, 2023
Maintainer

@ShubhangiShingade Can you please provide the remote appium server logs.

9 replies

saikrishna321 Jul 12, 2023
Maintainer

Can you show me the hub and node configuration please

ShubhangiShingade Jul 13, 2023
Author

@saikrishna321 Sure

Hub

{
  "server": {
    "port": 31337,
    "plugin": {
      "device-farm": {
        "platform": "android"
      }
    }
  }
}

Node

{
    "server": {
      "port": 4723,
      "plugin": {
        "device-farm": {
          "platform": "android",
          "hub": "http://10.120.75.2:31337/"
        }
      }
    }
  }

ShubhangiShingade Jul 13, 2023
Author

@saikrishna321 To add to earlier comment, me and my colleague are on the same VPN.

saikrishna321 Jul 13, 2023
Maintainer

@ShubhangiShingade Can you navigate to this file in /Users/shubhangi/.appium/node_modules/appium-device-farm/lib/plugin.js:174:59 and change to throw new Error(${error}, Please check the remote appium server log to know the reason for failure);

Save the changes and run again and see the logs what is the error.

From the logs given I can't see a call made to the node machine from the hub.

ShubhangiShingade Jul 13, 2023
Author

Thanks @saikrishna321 , This might take a while, collogue who I was testing this setup with is on holiday for a couple of week.
Let me check this and come back to you.

ShubhangiShingade · 2023-08-09T10:28:20Z

ShubhangiShingade
Aug 9, 2023
Author

@saikrishna321
I see the details after doing the suggested update to see error.

device-farm] 📱 Device UDID emulator-5554 unblocked. Reason: Remote Session failed to create [AppiumDriver@0871] Command 'createSession' was *not* handled by the following behaviours or plugins, even though they were registered to handle it: ["default"]. The command *was* handled by these: ["device-farm","appium-dashboard"]. [debug] [AppiumDriver@0871] Encountered internal error running command: Error: Error: connect ETIMEDOUT 192.168.1.120:4723, Please check the remote appium server log to know the reason for failure [debug] [AppiumDriver@0871] at /Users/shubhangi/.appium/node_modules/appium-device-farm/lib/plugin.js:174:31 [debug] [AppiumDriver@0871] at Generator.next (<anonymous>) [debug] [AppiumDriver@0871] at fulfilled (/Users/shubhangi/.appium/node_modules/appium-device-farm/lib/plugin.js:5:58) [debug] [AppiumDriver@0871] at runMicrotasks (<anonymous>) [debug] [AppiumDriver@0871] at processTicksAndRejections (node:internal/process/task_queues:96:5)

Please find the logs attached.

hub.log
node (1).log

0 replies

saikrishna321 · 2023-08-09T15:13:52Z

saikrishna321
Aug 9, 2023
Maintainer

@ShubhangiShingade Error: connect ETIMEDOUT 192.168.1.120:4723 I think the hub is not able to connect to node.

0 replies

saikrishna321 · 2023-08-09T15:14:45Z

saikrishna321
Aug 9, 2023
Maintainer

Node also does not connect hub

2023-08-09 10:09:44:433 [device-farm] Updating remote android devices http://10.120.75.2:31337/device-farm/api/register 2023-08-09 10:09:44:484 uncaughtException: connect ECONNREFUSED 10.120.75.2:31337 Error: connect ECONNREFUSED 10.120.75.2:31337 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1574:16)

0 replies

ShubhangiShingade · 2023-08-10T07:48:06Z

ShubhangiShingade
Aug 10, 2023
Author

Thank you for looking into it.
For the POC, Me (runs hub) and a colleague (runs node) are connected to same VPN. Hub and node are able to ping each other.
Not sure if it needs any other setup.

Can you recommend how nodes and hub should be configured ?

Also FYI, the hub registered the device connected to node and tagged it as busy at the start of the test execution.

2 replies

saikrishna321 Aug 10, 2023
Maintainer

Your logs don't say that. node is unable to send devices to hub as well

2023-08-09 10:09:44:433 [device-farm] Updating remote android devices http://10.120.75.2:31337/device-farm/api/register
2023-08-09 10:09:44:484 uncaughtException: connect ECONNREFUSED 10.120.75.2:31337
Error: connect ECONNREFUSED 10.120.75.2:31337
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1574:16)

ShubhangiShingade Aug 14, 2023
Author

hmm, I might have to reach out to the net-ops team for the configuration.
Do you know if anyone else has created hub/node while connected to a VPN ?

ShubhangiShingade · 2023-09-12T14:54:02Z

ShubhangiShingade
Sep 12, 2023
Author

Hello @saikrishna321

How does device-farm form the host URL?
I have node and hub (connected to a VPN over Tunnelblick) on same subnet (10.1XX.XX.XX) (can ping each other). However the devices/simulators are shown to have a different device location (192,16X.XX.XX).

[device-farm] Updating remote android devices http://10.120.75.2:4723/device-farm/api/register
[device-farm] Pushed devices to hub [{"adbPort":5037,"systemPort":44661,"sdk":"12","realDevice":false,"name":"sdk_gphone64_x86_64","busy":false,"state":"device","udid":"emulator-5554","platform":"android","deviceType":"emulator","host":"http://192.16X.X.XX:4723","totalUtilizationTimeMilliSec":0,"sessionStartTime":0}]

Can this cause the failure? If so, is there a way to fix such configuration ?

Shubhangi

1 reply

saikrishna321 Sep 12, 2023
Maintainer

@ShubhangiShingade Host url is formed based on the host url provided in the configuration file.

ShubhangiShingade · 2023-09-13T07:27:35Z

ShubhangiShingade
Sep 13, 2023
Author

@saikrishna321 None of the config files (hub as well as node) mention the IP (192.XX.XX.XX)

{
    "server": {
      "port": 4723,
      "plugin": {
        "device-farm": {
          "platform": "android",
          "hub": "http://10.120.75.2:31337/"
        }
      }
    }
  }

{
  "server": {
    "port": 31337,
    "plugin": {
      "device-farm": {
        "platform": "android"
      }
    }
  }
}

0 replies

saikrishna321 · 2023-09-13T11:05:32Z

saikrishna321
Sep 13, 2023
Maintainer

102.x.x.x is the machine IP the device is connected. But we don't use that IP to send request. We only use the IP address from the hub config.

Can you share the recent logs ?

0 replies

ShubhangiShingade · 2023-09-13T14:42:25Z

ShubhangiShingade
Sep 13, 2023
Author

> appium server -ka 800 --use-plugins=device-farm --config ./node.json -pa /wd/hub --address=10.120.75.11                                                                                                                                            ~/livedrive/appium@kp-lt
[Appium] Attempting to load plugin device-farm...
[debug] [Appium] Requiring plugin at /home/kai/.appium/node_modules/appium-device-farm
[Appium] Welcome to Appium v2.1.3
[Appium] Non-default server args:
[Appium] {
[Appium]   address: '10.120.75.11',
[Appium]   basePath: '/wd/hub',
[Appium]   keepAliveTimeout: 800,
[Appium]   usePlugins: [
[Appium]     'device-farm'
[Appium]   ]
[Appium] }
[Appium] Attempting to load driver uiautomator2...
[debug] [Appium] Requiring driver at /home/kai/.appium/node_modules/appium-uiautomator2-driver
[device-farm] 📣📣📣 Device Farm Plugin will be served at 🔗 http://localhost:4723/device-farm
✔ Waiting for node server http://10.120.75.2:31337 to be up and running

[ADB] Found 0 'build-tools' folders under '/home/kai/android-studio' (newest first):
[ADB] Using 'adb' from '/home/kai/android-studio/platform-tools/adb'
[debug] [ADB] Running '/home/kai/android-studio/platform-tools/adb -P 5037 start-server'
[debug] [ADB] Getting connected devices
[debug] [ADB] Connected devices: [{"udid":"emulator-5554","state":"device"}]
[device-farm] Android Device details for emulator-5554 not available. So querying now.
[device-farm] skipChromeDownload server arg is set; skipping Chromedriver installation.
[device-farm] Android web/hybrid testing will not be possible without Chromedriver.
[debug] [ADB] Running '/home/kai/android-studio/platform-tools/adb -P 5037 -s emulator-5554 shell getprop ro.build.version.release'
[debug] [ADB] Running '/home/kai/android-studio/platform-tools/adb -P 5037 -s emulator-5554 shell getprop ro.build.characteristics'
[debug] [ADB] Running '/home/kai/android-studio/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys bluetooth_manager | grep name: | cut -c9-'
[device-farm] Updating remote android devices http://10.120.75.2:31337/device-farm/api/register
[device-farm] Pushed devices to hub [{"adbPort":5037,"systemPort":39573,"sdk":"12","realDevice":false,"name":"sdk_gphone64_x86_64","busy":false,"state":"device","udid":"emulator-5554","platform":"android","deviceType":"emulator","host":"http://192.168.0.27:4723","totalUtilizationTimeMilliSec":0,"sessionStartTime":0}]
[Appium] Appium REST http interface listener started on http://10.120.75.11:4723/wd/hub
[Appium] Available drivers:
[Appium]   - [email protected] (automationName 'UiAutomator2')
[Appium] Available plugins:
[Appium]   - [email protected] (ACTIVE)
[Appium]   - [email protected]
[HTTP] --> GET /wd/hub
[HTTP] {}
[debug] [HTTP] No route found for /wd/hub
[HTTP] <-- GET /wd/hub 404 33 ms - 211
[HTTP] 
[HTTP] --> GET /wd/hub
[HTTP] {}
[debug] [HTTP] No route found for /wd/hub
[HTTP] <-- GET /wd/hub 404 20 ms - 211
[HTTP]

6 replies

ShubhangiShingade Sep 14, 2023
Author

Thanks you @saikrishna321 ,
Is there any workaround, while its being fixed ?

Shubhangi

saikrishna321 Sep 14, 2023
Maintainer

@ShubhangiShingade Not in this case. We need to fix this problem. Will add a fix hopefully today.

saikrishna321 Sep 15, 2023
Maintainer

@ShubhangiShingade can you try with the latest version. Exposed a new config as 'proxyIP'

appium-device-farm/sample-config.json

Line 7 in 0b098c3

"proxyIP": "http://10.x.x.x:3333",

ShubhangiShingade Sep 15, 2023
Author

@saikrishna321
We tried updating the node-config to following and run the test without luck

{ "server": { "address": "10.120.75.11", "port": 4723, "plugin": { "device-farm": { "platform": "android", "proxyIP": "http://10.120.75.11:4723", "hub": "http://10.120.75.2:31337" } } } }

Error on hub

2023-09-15 17:02:08:623 [device-farm] 📱 Device UDID emulator-5554 unblocked. Reason: Remote Session failed to create 2023-09-15 17:02:08:623 [AppiumDriver@9b08] Command 'createSession' was *not* handled by the following behaviours or plugins, even though they were registered to handle it: ["default"]. The command *was* handled by these: ["device-farm","appium-dashboard"]. 2023-09-15 17:02:08:624 [AppiumDriver@9b08] Encountered internal error running command: Error: AxiosError: Request failed with status code 500, Please check the remote appium server log to know the reason for failure 2023-09-15 17:02:08:624 [AppiumDriver@9b08] at /Users/shubhangi/.appium/node_modules/appium-device-farm/lib/plugin.js:174:31 2023-09-15 17:02:08:624 [AppiumDriver@9b08] at Generator.next (<anonymous>) 2023-09-15 17:02:08:624 [AppiumDriver@9b08] at fulfilled (/Users/shubhangi/.appium/node_modules/appium-device-farm/lib/plugin.js:5:58) 2023-09-15 17:02:08:626 [AppiumDriver@9b08] at runMicrotasks (<anonymous>) 2023-09-15 17:02:08:626 [AppiumDriver@9b08] at processTicksAndRejections (node:internal/process/task_queues:96:5)

Error on node

[debug] [AppiumDriver@e183] Encountered internal error running command: Error: No device found for filters: {"platform":"android","name":"","udid":"emulator-5554","busy":false,"userBlocked":false} [debug] [AppiumDriver@e183] at /home/kai/.appium/node_modules/appium-device-farm/lib/device-utils.js:110:19 [debug] [AppiumDriver@e183] at Generator.throw (<anonymous>) [debug] [AppiumDriver@e183] at rejected (/home/kai/.appium/node_modules/appium-device-farm/lib/device-utils.js:6:65) [HTTP] <-- POST /wd/hub/session 500 180007 ms - 766 [HTTP] [device-farm] 📱 Device UDID emulator-5554 unblocked. Reason: Remote Session failed to create [AppiumDriver@e183] Command 'createSession' was *not* handled by the following behaviours or plugins, even though they were registered to handle it: ["default"]. The command *was* handled by these: ["device-farm"]. [debug] [AppiumDriver@e183] Encountered internal error running command: Error: An unknown server-side error occurred while processing the command. Original error: No device found for filters: {"platform":"android","name":"","udid":"emulator-5554","busy":false,"userBlocked":false}, Please check the remote appium server log to know the reason for failure [debug] [AppiumDriver@e183]

hub-log-15-sep.log
node-log-15sep.log

saikrishna321 Sep 16, 2023
Maintainer

@ShubhangiShingade Can you post the logs as gist and please comment on the issue created. #786

ShubhangiShingade · 2023-09-13T14:44:18Z

ShubhangiShingade
Sep 13, 2023
Author

@saikrishna321
Here is the hub log
hub.log

I see the device getting tagged 'Busy' for few seconds, before the create session call fails

0 replies

Uh oh!

Unable to create session on remote device (while it works on local device) #740

Uh oh!

Uh oh!

ShubhangiShingade Jul 10, 2023

Replies: 10 comments · 18 replies

Uh oh!

saikrishna321 Jul 10, 2023 Maintainer

Uh oh!

saikrishna321 Jul 12, 2023 Maintainer

Uh oh!

Uh oh!

ShubhangiShingade Jul 13, 2023 Author

Uh oh!

ShubhangiShingade Jul 13, 2023 Author

Uh oh!

saikrishna321 Jul 13, 2023 Maintainer

Uh oh!

ShubhangiShingade Jul 13, 2023 Author

Uh oh!

ShubhangiShingade Aug 9, 2023 Author

Uh oh!

saikrishna321 Aug 9, 2023 Maintainer

Uh oh!

Uh oh!

saikrishna321 Aug 9, 2023 Maintainer

Uh oh!

ShubhangiShingade Aug 10, 2023 Author

Uh oh!

saikrishna321 Aug 10, 2023 Maintainer

Uh oh!

ShubhangiShingade Aug 14, 2023 Author

Uh oh!

ShubhangiShingade Sep 12, 2023 Author

Uh oh!

saikrishna321 Sep 12, 2023 Maintainer

Uh oh!

ShubhangiShingade Sep 13, 2023 Author

Uh oh!

saikrishna321 Sep 13, 2023 Maintainer

Uh oh!

ShubhangiShingade Sep 13, 2023 Author

Uh oh!

ShubhangiShingade Sep 14, 2023 Author

Uh oh!

saikrishna321 Sep 14, 2023 Maintainer

Uh oh!

saikrishna321 Sep 15, 2023 Maintainer

Uh oh!

Uh oh!

ShubhangiShingade Sep 15, 2023 Author

Uh oh!

saikrishna321 Sep 16, 2023 Maintainer

Uh oh!

Uh oh!

ShubhangiShingade Sep 13, 2023 Author

ShubhangiShingade
Jul 10, 2023

Replies: 10 comments 18 replies

saikrishna321
Jul 10, 2023
Maintainer

saikrishna321 Jul 12, 2023
Maintainer

ShubhangiShingade Jul 13, 2023
Author

ShubhangiShingade Jul 13, 2023
Author

saikrishna321 Jul 13, 2023
Maintainer

ShubhangiShingade Jul 13, 2023
Author

ShubhangiShingade
Aug 9, 2023
Author

saikrishna321
Aug 9, 2023
Maintainer

saikrishna321
Aug 9, 2023
Maintainer

ShubhangiShingade
Aug 10, 2023
Author

saikrishna321 Aug 10, 2023
Maintainer

ShubhangiShingade Aug 14, 2023
Author

ShubhangiShingade
Sep 12, 2023
Author

saikrishna321 Sep 12, 2023
Maintainer

ShubhangiShingade
Sep 13, 2023
Author

saikrishna321
Sep 13, 2023
Maintainer

ShubhangiShingade
Sep 13, 2023
Author

ShubhangiShingade Sep 14, 2023
Author

saikrishna321 Sep 14, 2023
Maintainer

saikrishna321 Sep 15, 2023
Maintainer

ShubhangiShingade Sep 15, 2023
Author

saikrishna321 Sep 16, 2023
Maintainer

ShubhangiShingade
Sep 13, 2023
Author