-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Description
Celestia Node version
v0.28.4
OS
Ubuntu 22.04.5 LTS
Install tools
No response
Others
No response
Steps to reproduce it
After the celestia-app upgrade, we restarted our bridge node.
Expected result
no error logs
Actual result
A lot of warnings and errors.
2025-12-10T14:54:11.282Z WARN core core/fetcher.go:196 fetcher: error receiving signed block {"height": 9166063, "err": "rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
2025-12-10T14:54:21.282Z WARN core core/fetcher.go:196 fetcher: error receiving signed block {"height": 9166064, "err": "rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
2025-12-10T14:54:27.099Z ERROR core core/listener.go:161 underlying subscription is stuck
Relevant log output
2025-12-10T14:54:09.600Z INFO share/discovery discovery/discovery.go:201 successfully advertised to topic /full/v0.1.0
2025-12-10T14:54:11.282Z WARN core core/fetcher.go:196 fetcher: error receiving signed block {"height": 9166063, "err": "rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
2025-12-10T14:54:21.282Z WARN core core/fetcher.go:196 fetcher: error receiving signed block {"height": 9166064, "err": "rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
2025-12-10T14:54:27.099Z ERROR core core/listener.go:161 underlying subscription is stuck
2025-12-10T14:54:29.201Z INFO pruner/service pruner/service.go:170 pruning round finished {"done": 0, "failed": 0, "took": 0.000014757}
2025-12-10T14:54:31.283Z WARN core core/fetcher.go:196 fetcher: error receiving signed block {"height": 9166065, "err": "rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
2025-12-10T14:54:41.284Z WARN core core/fetcher.go:196 fetcher: error receiving signed block {"height": 9166066, "err": "rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
2025-12-10T14:54:51.284Z WARN core core/fetcher.go:196 fetcher: error receiving signed block {"height": 9166067, "err": "rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
2025-12-10T14:54:57.099Z ERROR core core/listener.go:161 underlying subscription is stuck
2025-12-10T14:54:59.201Z INFO pruner/service pruner/service.go:170 pruning round finished {"done": 0, "failed": 0, "took": 0.000017042}
2025-12-10T14:55:01.285Z WARN core core/fetcher.go:196 fetcher: error receiving signed block {"height": 9166068, "err": "rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
2025-12-10T14:55:11.285Z WARN core core/fetcher.go:196 fetcher: error receiving signed block {"height": 9166069, "err": "rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
2025-12-10T14:55:21.285Z WARN core core/fetcher.go:196 fetcher: error receiving signed block {"height": 9166070, "err": "rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
2025-12-10T14:55:27.099Z ERROR core core/listener.go:161 underlying subscription is stuckIs the node "stuck"? Has it stopped syncing?
not syncing
Notes
Our full node is working normally, but our bridge node has been unable to sync for a while. We are consistently seeing these error logs on the bridge node.