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

p2p: stream scope not attached to a protocol errors #2259

Closed
dB2510 opened this issue May 31, 2023 · 1 comment
Closed

p2p: stream scope not attached to a protocol errors #2259

dB2510 opened this issue May 31, 2023 · 1 comment
Assignees
@dB2510
Labels
bug Something isn't working protocol Protocol Team tickets

Comments

@dB2510
Copy link
Contributor

dB2510 commented May 31, 2023 •
edited
Loading

🐞 Bug Report

Description

We are seeing ping errors in our core team cluster as stream scope not attached to a protocol. Because of these errors we are seeing ping connections and disconnections frequently.

🔬 Minimal Reproduction

This issue was observed in charon run with tag 0229636 in Obol Core Team 3 of 4 cluster.

🔥 Error


2023-05-31 16:14:25.683 | INFO ping       Peer connected                           {"peer": "outrageous-taxi", "rtt": "409.06674ms"}
2023-05-31 16:13:58.606 | WARN ping       Peer ping failing                        {"peer": "outrageous-taxi", "error": "stream scope not attached to a protocol"}

🌍 Your Environment

Operating System:

  
Ubuntu 22.04 LTS

What version of Charon are you running? (Which release/git commit)

  
0229636

Anything else relevant (validator index / public key)?
Cluster name: Obol Core Team 3 of 4
@dB2510 dB2510 added the bug Something isn't working label May 31, 2023
@github-actions github-actions bot added the protocol Protocol Team tickets label May 31, 2023
@dB2510 dB2510 changed the title Stream scope ping errors p2p: stream scope not attached to a protocol errors May 31, 2023
@dB2510 dB2510 mentioned this issue May 31, 2023
Merged
obol-bulldozer bot pushed a commit that referenced this issue Jun 1, 2023
@dB2510
p2p: close existing ping streams (#2260)
22b4d31 
Close existing streams after each ping. This solves the errors from ping service `stream scope not attached to a protocol` which was caused by creating new streams for each ping and NOT closing them.

Note: We need to test this on our core team cluster.

category: bug
ticket: #2259
@dB2510 dB2510 self-assigned this Jun 2, 2023
@dB2510
Copy link
Contributor Author

dB2510 commented Jun 2, 2023

Closed by #2260

@dB2510 dB2510 closed this as completed Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dB2510 dB2510

Labels
bug Something isn't working protocol Protocol Team tickets
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dB2510