bee icon indicating copy to clipboard operation
bee copied to clipboard

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

Open Cafe137 opened this issue 1 year ago • 2 comments

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

https://github.com/user-attachments/assets/29c9b9e9-9be9-42f0-a5f1-45a9114524ac

Steps to reproduce

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

Cafe137 avatar Dec 10 '24 21:12 Cafe137

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

istae avatar Dec 11 '24 02:12 istae

Checked just now - seems to be the same.

Screenshot 2024-12-11 at 10 45 48

Cafe137 avatar Dec 11 '24 09:12 Cafe137