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

Question about Bitswap Client ReceiveError: Application error 0x0 (local) #3426

Closed
rootulp opened this issue May 22, 2024 · 1 comment · Fixed by #3434
Closed

Question about Bitswap Client ReceiveError: Application error 0x0 (local) #3426

rootulp opened this issue May 22, 2024 · 1 comment · Fixed by #3434
Labels
external Issues created by non node team members question Further information is requested

Comments

@rootulp
Copy link
Collaborator

rootulp commented May 22, 2024

Context

I just started a v0.13.5 light node on mainnet via:

celestia light start --core.ip rpc.celestia.pops.one

The node appears to be sampling headers from genesis to the tip of the chain successfully. However, I'm observing several instances of logs like this:

2024-05-22T16:29:18.212Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.212Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.213Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.214Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.214Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.216Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.216Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.216Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.216Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.216Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.216Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.216Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.216Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.217Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.217Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.217Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.218Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)
2024-05-22T16:29:18.218Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: stream reset
2024-05-22T16:29:18.219Z	INFO	bitswap-server	server/server.go:547	Bitswap Client ReceiveError: Application error 0x0 (local)

Question

Should I be concerned? Why does it keep happening?
@rootulp rootulp added the question Further information is requested label May 22, 2024
@github-actions github-actions bot added the external Issues created by non node team members label May 22, 2024
@Wondertan
Copy link
Member

It happens when QUIC streams are reset. I don't know precisely why they are being reset, but my guess is that this log started to emerge after one of the Boxo(library containing bitswap) updates.

@Wondertan Wondertan mentioned this issue May 24, 2024
Merged
Wondertan added a commit that referenced this issue May 27, 2024
@Wondertan
chore(logs): lower bitswap-server verbosity (#3434)
81bd874 
```
May 24 04:10:51 celestia[1806932]: 2024-05-24T04:10:51.439Z        INFO        bitswap-server        server/server.go:547        Bitswap Client ReceiveError: Application error 0x0 (local)
May 24 04:10:51 celestia[1806932]: 2024-05-24T04:10:51.440Z        INFO        bitswap-server        server/server.go:547        Bitswap Client ReceiveError: stream reset
May 24 04:10:51 celestia[1806932]: 2024-05-24T04:10:51.443Z        INFO        bitswap-server        server/server.go:547        Bitswap Client ReceiveError: Application error 0x0 (local)
May 24 04:10:51 celestia[1806932]: 2024-05-24T04:10:51.443Z        INFO        bitswap-server        server/server.go:547        Bitswap Client ReceiveError: Application error 0x0 (local)
May 24 04:10:51 celestia[1806932]: 2024-05-24T04:10:51.443Z        INFO        bitswap-server        server/server.go:547        Bitswap Client ReceiveError: Application error 0x0 (local)
May 24 04:10:51 celestia[1806932]: 2024-05-24T04:10:51.443Z        INFO        bitswap-server        server/server.go:547        Bitswap Client ReceiveError: Application error 0x0 (local)
May 24 04:10:51 celestia[1806932]: 2024-05-24T04:10:51.443Z        INFO        bitswap-server        server/server.go:547        Bitswap Client ReceiveError: Application error 0x0 (local)

```
These logs are pretty annoying, and this PR jams them.

However, the amount of those logs coming from stream resets is a bit concerning, and a quick look through the code path does not give me an idea of what could go wrong. I propose to shut them for now and observe if something goes wrong because currently, things are running well 

Fixes #3426
ramin pushed a commit that referenced this issue Jun 6, 2024
@Wondertan @ramin
chore(logs): lower bitswap-server verbosity (#3434)
e23134c 
```
May 24 04:10:51 celestia[1806932]: 2024-05-24T04:10:51.439Z        INFO        bitswap-server        server/server.go:547        Bitswap Client ReceiveError: Application error 0x0 (local)
May 24 04:10:51 celestia[1806932]: 2024-05-24T04:10:51.440Z        INFO        bitswap-server        server/server.go:547        Bitswap Client ReceiveError: stream reset
May 24 04:10:51 celestia[1806932]: 2024-05-24T04:10:51.443Z        INFO        bitswap-server        server/server.go:547        Bitswap Client ReceiveError: Application error 0x0 (local)
May 24 04:10:51 celestia[1806932]: 2024-05-24T04:10:51.443Z        INFO        bitswap-server        server/server.go:547        Bitswap Client ReceiveError: Application error 0x0 (local)
May 24 04:10:51 celestia[1806932]: 2024-05-24T04:10:51.443Z        INFO        bitswap-server        server/server.go:547        Bitswap Client ReceiveError: Application error 0x0 (local)
May 24 04:10:51 celestia[1806932]: 2024-05-24T04:10:51.443Z        INFO        bitswap-server        server/server.go:547        Bitswap Client ReceiveError: Application error 0x0 (local)
May 24 04:10:51 celestia[1806932]: 2024-05-24T04:10:51.443Z        INFO        bitswap-server        server/server.go:547        Bitswap Client ReceiveError: Application error 0x0 (local)

```
These logs are pretty annoying, and this PR jams them.

However, the amount of those logs coming from stream resets is a bit concerning, and a quick look through the code path does not give me an idea of what could go wrong. I propose to shut them for now and observe if something goes wrong because currently, things are running well 

Fixes #3426
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
external Issues created by non node team members question Further information is requested
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore(logs): lower bitswap-server verbosity celestiaorg/celestia-node
2 participants
@rootulp @Wondertan