-
Notifications
You must be signed in to change notification settings - Fork 130
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
Rococo <> Wococo bridge hub relay disconnects from our RBH node #1785
Comments
Seems like
Is that the RPC connection (the "Accepting new connection 8/100" comes from Trying to reproduce locally |
When it's all started (relay logs):
|
The issue is gone - it should have been fixed in one of referenced PRs. Still - I'm not sure if issue that I've originally described (i.e. when we are actually unable to reconnect) exist and whether it can be reproduced. |
Locally I'm getting a more specific error:
So maybe the |
@serban300 No, that isn't what I see in logs. Are you sure you're using the same accounts (locally) as our relayer does? I can see the balances are not zero there: https://grafana.parity-mgmt.parity.io/d/UFsgbJtVz/bridgehubrococo-bridgehubwococo-maintenance-00000001?orgId=1 |
You might be right. Checking. I don't remember where I took these accounts from. I had this debugging env setup some time ago when investigating another issue |
Yes, sorry, I was using a different account. When running the relayer locally, it just works |
So "important" lines from tonight log: Relay first aborts:
Starting final relay (relay instance that is running now):
First final relay error (Rococo RPC node):
Rococo reconnect:
And then reconnects again (by other relay - this isn't good, but not critical???):
First WococoBridgeNode error and reconnect:
After that ^^^ the relay always restarts when
More specific, it fails in |
Apparently the fix isn't working |
Tonight log:
|
Have been able to reproduce it locally (I mean - to run relay locally, but connect to our regular nodes, with #1930 included) and it seems that the failure is for Rococo and the
So it is not related to the requrest/response size |
Some logs:
The text was updated successfully, but these errors were encountered: