-
Notifications
You must be signed in to change notification settings - Fork 879
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
Bridge nodes listener gets stuck until resub #3339
Comments
hey @walldiss so i will put here information that seems relevant to the issue. hope that will help. so today we had the issue for around 20 min issue was resolved with a manual restart here are the logs captured just before the issue and after
|
Based on the logs, it is clear that resubscribing does not help resolve the issue, which I did not observe in other bridge nodes I checked earlier today. |
hey @walldiss we only run one, but we utilize our public rpc for it which is in the docs. But this hasnt been a problem at all since these latest versions (dont have exact timing but we didnt see this problem like a month ago or 2 months max). Also ive got another report with same problem and a private rpc used just for 1 bridge node. As for often, its not that often, i think i know of about 4-5 incidents so far between mainnet and testnet |
Implementation ideas
Initially reported by the P-OPS team, this issue was noted when bridge nodes occasionally fell behind consensus nodes. The issue is consistently marked by the following log line:
Upon further investigation across other bridge nodes, similar occurrences were noted a few times each week. These issues are generally resolved automatically by the node's internal logic, which triggers a resubscription in response to such events.
Notably, these events affect multiple nodes simultaneously, which suggests potential connectivity issues at the time of the incident or a problem with the core node RPC becoming stuck.
The text was updated successfully, but these errors were encountered: