Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Error while creating session: undefined #1444

Open
Jitu1888 opened this issue Nov 13, 2024 · 6 comments
Open

Error while creating session: undefined #1444

Jitu1888 opened this issue Nov 13, 2024 · 6 comments

Comments

@Jitu1888
Copy link

Describe the bug
2024-11-13 03:46:03:097 [Appium] Welcome to Appium v2.11.5 (REV bab86d5de571015b63fd8fc30b47bbe072a1290e)

2024-11-13 03:46:12:941 [Appium] Appium REST http interface listener started on http://127.0.0.1:12633/wd/hub
2024-11-13 03:46:12:943 [Appium] Available drivers:
2024-11-13 03:46:12:943 [Appium] - uiautomator2@3.8.0 (automationName 'UiAutomator2')
2024-11-13 03:46:12:945 [Appium] Available plugins:
2024-11-13 03:46:12:946 [Appium] - device-farm@9.4.0 (ACTIVE)
2024-11-13 03:46:12:946 [Appium] - gestures@4.0.0 (ACTIVE)
2024-11-13 03:46:12:946 [Appium] - images@3.0.19
2024-11-13 03:46:12:947 [Appium] - element-wait@3.0.2
2024-11-13 03:46:12:948 [Appium] - execute-driver@3.0.35
2024-11-13 03:46:12:971 [HTTP] --> GET /wd/hub/status {}

@saikrishna321 We are getting the error during execution .
https://gist.github.com/Jitu1888/51517b7afa29c58137ae9aba04c8c22d

@Jitu1888
Copy link
Author

2024-11-13 04:09:49:501 [AppiumDriver@c47b] 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"].
2024-11-13 04:09:49:501 [AppiumDriver@c47b] Encountered internal error running command: Error: Unknown error while creating session
at bs.generator (/home/jenkins/.appium/node_modules/appium-device-farm/lib/webpack:/appium-device-farm/lib/src/plugin.js:446:24)
at Generator.throw ()

@Jitu1888
Copy link
Author

@saikrishna321 search for ""message":"timeout of 60000ms exceeded","name":"AxiosError"" in gist

@Jitu1888
Copy link
Author

Its really urgent , we are stuck because of this issue @saikrishna321

@sudharsan-selvaraj
Copy link
Member

@Jitu1888 It looks like http://devicelab4.games24x7.com:4723/wd/hub/session is not responding within 60seconds. Can you confirm if the above URL works fine when running tests in parallel?

@Jitu1888
Copy link
Author

its working fine only http://devicelab4.games24x7.com:4723/wd/hub/session

@Jitu1888
Copy link
Author

Jitu1888 commented Nov 14, 2024

2024-11-14 19:48:35:213 - [device-farm-/Users/jenkins-lab5/.appium] Creating new proxy streaming session for device 0G03106R300004AF
Unable to connect to remote streaming socket
ErrorEvent {
[Symbol(kTarget)]: WebSocket {
_events: [Object: null prototype] {
message: [Function],
open: [Function],
error: [Function]
},
_eventsCount: 3,
_maxListeners: undefined,
_binaryType: 'nodebuffer',
_closeCode: 1006,
_closeFrameReceived: false,
_closeFrameSent: false,
_closeMessage: ,
_closeTimer: null,
_errorEmitted: true,
_extensions: {},
_paused: false,
_protocol: '',
_readyState: 3,
_receiver: null,
_sender: null,
_socket: null,
_bufferedAmount: 0,
_isServer: false,
_redirects: 0,
_autoPong: true,
_url: 'ws://127.0.0.1:53542/',
_req: null,
[Symbol(shapeMode)]: false,
[Symbol(kCapture)]: false
},
[Symbol(kType)]: 'error',
[Symbol(kError)]: Error: socket hang up
at Socket.socketOnEnd (node:_http_client:519:23)
at Socket.emit (node:events:531:35)
at endReadableNT (node:internal/streams/readable:1696:12)
at processTicksAndRejections (node:internal/process/task_queues:82:21) {
code: 'ECONNRESET'
},
[Symbol(kMessage)]: 'socket hang up'
}
2024-11-14 19:48:39:202 - [HTTP] --> POST /device-farm/api/unblock {"platform":"android","udid":"10BD1Y0EJE004BA","busy":true}
2024-11-14 19:48:39:202 - [device-farm-/Users/jenkins-lab5/.appium] Received non-webdriver request with url /device-farm/api/unblock. So, not proxying it to downstream.
2024-11-14 19:48:39:203 - [device-farm-/ @sudharsan-selvaraj How to handle above issue if it coming in mid of execution?

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

No branches or pull requests

2 participants