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.

Sign up for GitHub

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

Jump to bottom

add hostname or IP to error message from RPC nodes #914

Closed
cipig opened this issue Apr 20, 2021 · 4 comments · Fixed by #1119
Closed

add hostname or IP to error message from RPC nodes #914

cipig opened this issue Apr 20, 2021 · 4 comments · Fixed by #1119
Assignees
@sergeyboyko0791

Comments

@cipig
Copy link
Member

cipig commented Apr 20, 2021 •
edited
Loading

i started to get "403 Forbidden" errors from some BEP20 RPC nodes, but i can't see from which one, the error message on mm2 does not contain the hostname or IP:

20 13:27:28, rpc:300] ERROR RPC error response: rpc:253] lp_ordermatch:3202] eth:2557] eth:291] Transport error: request MethodCall(MethodCall { jsonrpc: Some(V2), method: "eth_gasPrice", params: Some(Array([])), id: Num(1807) }) failed: web3_transport:147] !200: 403 Forbidden, <html>..<head><title>403 Forbidden</title></head>..<body>..<center><h1>403 Forbidden</h1></center>..</body>..</html>..; web3_transport:147] !200: 403 Forbidden, <html>..<head><title>403 Forbidden</title></head>..<body>..<center><h1>403 Forbidden</h1></center>..</body>..</html>..; web3_transport:147] !200: 403 Forbidden, <html>..<head><title>403 Forbidden</title></head>..<body>..<center><h1>403 Forbidden</h1></center>..</body>..</html>..

can it be added to the error message, so i can replace the "faulty" server?

i use \"urls\":[\"https://bsc-dataseed.binance.org\",\"https://bsc-dataseed1.defibit.io\",\"https://bsc-dataseed1.ninicoin.io\"]
@cipig cipig changed the title add hostname or IP to error message from BEP20 nodes add hostname or IP to error message from BEP20 nodes and make mm2 try all available ones in case of error Apr 20, 2021
@cipig
Copy link
Member Author

cipig commented Apr 20, 2021

collected more possible errors from BEP20 RPC nodes:

20 14:38:39, rpc:300] ERROR RPC error response: rpc:253] lp_ordermatch:3216] maker_swap:1586] eth:2522] eth:1485] RPC error: Error { code: InternalError, message: "handle request error", data: None }
20 14:38:40, rpc:300] ERROR RPC error response: rpc:253] lp_ordermatch:3202] eth:2557] eth:291] RPC error: Error { code: InternalError, message: "handle request error", data: None }
20 14:38:45, rpc:300] ERROR RPC error response: rpc:253] lp_ordermatch:3216] maker_swap:1586] eth:2509] eth:291] RPC error: Error { code: InternalError, message: "handle request error", data: None }
20 14:38:48, rpc:300] ERROR RPC error response: rpc:253] lp_ordermatch:3209] lp_swap:461] eth:1463] RPC error: Error { code: InternalError, message: "handle request error", data: None }
20 14:38:56, rpc:300] ERROR RPC error response: rpc:253] lp_ordermatch:3193] eth:1485] RPC error: Error { code: InternalError, message: "handle request error", data: None }

20 14:40:39, common:701] drive03 receiver is dropped
20 14:40:40, common:701] drive03 receiver is dropped
20 14:40:40, common:701] drive03 receiver is dropped
20 14:40:41, common:701] drive03 receiver is dropped
20 14:40:41, common:701] drive03 receiver is dropped
20 14:40:41, common:701] drive03 receiver is dropped
20 14:40:42, common:701] drive03 receiver is dropped
20 14:40:42, common:701] drive03 receiver is dropped

@cipig
Copy link
Member Author

cipig commented Apr 20, 2021

found this: https://community.binance.org/topic/4556/change-the-public-node-if-you-meet-issues-of-accessing-bsc
some nodes are overloaded as of Binance 15 minutes ago

@cipig cipig mentioned this issue May 24, 2021
Closed
@cipig cipig changed the title add hostname or IP to error message from BEP20 nodes and make mm2 try all available ones in case of error add hostname or IP to error message from BEP20 nodes May 24, 2021
@cipig
Copy link
Member Author

cipig commented Oct 21, 2021

we have the problem again with slow public RPC nodes, this time on Polygon
i would like to try different ones, but mm2 does not show me which of the configured nodes has the problem, i only see this in console
21 04:15:24, common:734] drive03 receiver is dropped
but it's clearly a timeout on my_balance call
can we please add the hostnames to error message, so i can identify the slow nodes and replace them with better ones?

@cipig cipig changed the title add hostname or IP to error message from BEP20 nodes add hostname or IP to error message from RPC nodes Oct 21, 2021
@sergeyboyko0791
Copy link

I'll try to add the URL to as many places as possible today.

@sergeyboyko0791 sergeyboyko0791 self-assigned this Oct 26, 2021
@sergeyboyko0791 sergeyboyko0791 linked a pull request Oct 27, 2021 that will close this issue
Slurp refactoring #914 #1119
Merged
artemii235 pushed a commit that referenced this issue Nov 1, 2021
@sergeyboyko0791
Slurp refactoring #914 (#1119)
05e80b1 
* Refactor common crate
* Add SlurpError
* Refactor slurp_req, slurp_url so they return SlurpResult
* Replace slurp functions into native/wasm common::transport
* Replace native executor mod into native_executor.rs
* Rename executor.rs into wasm_executor.rs
* Replace wio mod from common.rs into wio.rs

* Sync changes with 'telegram_bot_notification'
* Return fetch_json, post_json to transport.rs
* Add slurp_post_json in WASM and native

* Log warning if a Web3 request timed out

* Add an RPC url to a Web3 transport parsing error
@cipig cipig closed this as completed Mar 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sergeyboyko0791 sergeyboyko0791

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Slurp refactoring #914 KomodoPlatform/komodo-defi-framework
2 participants
@cipig @sergeyboyko0791