Open nugaon opened 1 month ago
The linked PR fixes the blocklist issue but the "unexpected request while in light mode"
error is expected.
The queen
node is bootnode mode
.
bee printconfig
from the docker container returns
# cause the node to always accept incoming connections
bootnode-mode: "true"
When in bootnode mode (or light mode), bee will replace the p2p stream handlers with an always erroring handler. (error above) https://github.com/ethersphere/bee/blob/0e42d83eecfbeaa764ee8004ea402b78b8293147/pkg/node/node.go#L974-L984 You can also see this from the logs
"level"="info" "logger"="node" "msg"="starting in light mode"
⚠️ Support requests in an issue-format will be closed immediately. For support, go to Swarm's Discord.
Context
I'm testing out GSOC functionality which uses fdp-play for environment (5 nodes network).
Related logs
also at pull sync
Summary
Even though
swarm-cli status
gives backMode: full
- as expected based on the Bee configuration as well -, libp2p assumes it as a light node.It tries to blocklist peers but it cannot and refers to some network availability issue.
Eventually, the chunks push seems successful since the API request returns with 201.
Expected behavior
Bee does blocklist when it wants to.
Actual behavior
It fails blocklisting.
Steps to reproduce
Run FDP Play and push chunks.
Possible solution