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

Chopsticks XCM Error After Recent Update #708

Closed
wuzhong-papermoon opened this issue Mar 25, 2024 · 1 comment · Fixed by #709
Closed

Chopsticks XCM Error After Recent Update #708

wuzhong-papermoon opened this issue Mar 25, 2024 · 1 comment · Fixed by #709

Comments

@wuzhong-papermoon
Copy link

Hi Chopsticks Team,

I'm writing to report an issue I've encountered after the recent update. When I run xcm commands using Chopsticks, I receive the following error message:
Error: server.handleUpgrade() was called more than once with the same socket, possibly due to a misconfiguration

I think the relayer chain might be attempting to open a duplicate port(suspecting port 8000/8001). I've verified that ports 8000 to 8005 are all available before execution.

Here's the command I used:

npx @acala-network/chopsticks@latest xcm \
--r="configs/polkadot.yml" \
--p="configs/moonbeam.yml" \
--p="configs/polkadot-asset-hub.yml"

Below is the complete error prompted:

Error: server.handleUpgrade() was called more than once with the same socket, possibly due to a misconfiguration
    at WebSocketServer.completeUpgrade (/Users/abc/.npm/_npx/81ad9c881cb83600/node_modules/ws/lib/websocket-server.js:366:13)
    at WebSocketServer.handleUpgrade (/Users/abc/.npm/_npx/81ad9c881cb83600/node_modules/ws/lib/websocket-server.js:343:10)
    at Server.upgrade (/Users/abc/.npm/_npx/81ad9c881cb83600/node_modules/ws/lib/websocket-server.js:119:16)
    at Server.emit (node:events:526:35)
    at Server.emit (node:domain:489:12)
    at onParserExecuteCommon (node:_http_server:915:14)
    at onParserExecute (node:_http_server:809:3)

Please let me know if you require any additional information to help troubleshoot this issue.
Hope this issue will be resolved soon. Cheers!

@ermalkaleci
Copy link
Collaborator

I've identified the issue. The workaround for now is to start each chain to a specified port

@ermalkaleci ermalkaleci linked a pull request Mar 25, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants