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

Log is spammed with "stream handler: handshake: handle failed", but the node is doing fine #4927

Open
Cafe137 opened this issue Dec 10, 2024 · 2 comments
Labels
needs-triaging new issues that need triaging

Comments

@Cafe137
Copy link

Cafe137 commented Dec 10, 2024

Context

Bee 2.3.0 mainnet, full, staking

Summary

I am running a full node with staking enabled. The node logs are flooded with seemingly harmless errors, potentially hiding real errors.

Culprit:

"time"="2024-12-10 21:28:57.432306" "level"="error" "logger"="node/libp2p" "msg"="stream handler: handshake: handle failed" "peer_id"="QmP4CY2wMyoCMXwoBzB99LXZZCvTUdVJy1dpy6ABVmgj5H"

My node otherwise seems healthy, is able to upload and retrieve, and participates in the storage incentives.

Expected behavior

With default logger settings, the logs should be useful. When my entire screen is filled with errors of the same kind, I expect it to be a serious problem, but apparently this is normal behaviour.

Actual behavior

bee-logs.mp4

Steps to reproduce

Bee 2.3.0 mainnet, full (optional?), staking (optional?)

@Cafe137 Cafe137 added the needs-triaging new issues that need triaging label Dec 10, 2024
@istae
Copy link
Member

istae commented Dec 11, 2024

has this been resolved? could it be due to the network migration to 2.3.0?

@Cafe137
Copy link
Author

Cafe137 commented Dec 11, 2024

Checked just now - seems to be the same.

Screenshot 2024-12-11 at 10 45 48

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triaging new issues that need triaging
Projects
None yet
Development

No branches or pull requests

2 participants