You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not a security-related bug/issue. If it is, please follow please follow the security policy.
I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
I am running the Latest release, the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
I did not make any code changes to lotus.
Lotus component
lotus daemon - chain sync
lotus fvm/fevm - Lotus FVM and FEVM interactions
lotus miner/worker - sealing
lotus miner - proving(WindowPoSt/WinningPoSt)
lotus JSON-RPC API
lotus message management (mpool)
Other
Lotus Version
lotus version
Daemon: 1.26.0+mainnet+git.5f86ff9a6+api1.5.0
Local: lotus version 1.26.0+mainnet+git.5f86ff9a6
lotus-miner version
Daemon: 1.26.0+mainnet+git.5f86ff9a6+api1.5.0
Local: lotus-miner version 1.26.0+mainnet+git.5f86ff9a6
Repro Steps
No response
Describe the Bug
After executing the command lotus-miner storage detach /path/to/storage, the path was indeed removed. However, the miner's log continuously reports an error: error in RPC call to 'Filecoin.StorageReportHealth': health report for unknown storage: 1931939e-0af0-430c-9ae5-8d887dc94004 and similar errors. What could be the reason for this, and how should it be resolved?
Logging Information
2024-04-05T13:43:42.833+0800 WARN rpc go-jsonrpc@v0.3.1/handler.go:444 error in RPC call to 'Filecoin.StorageReportHealth': health report for unknown storage: 67a1352d-a507-434e-890e-c151553a42bc:
github.com/filecoin-project/lotus/storage/paths.(*MemIndex).StorageReportHealth
/root/go/src/lotus/storage/paths/index.go:316
2024-04-05T13:43:42.834+0800 WARN rpc go-jsonrpc@v0.3.1/handler.go:444 error in RPC call to 'Filecoin.StorageReportHealth': health report for unknown storage: 1931939e-0af0-430c-9ae5-8d887dc94004:
github.com/filecoin-project/lotus/storage/paths.(*MemIndex).StorageReportHealth
/root/go/src/lotus/storage/paths/index.go:316
2024-04-05T13:43:53.050+0800 WARN rpc go-jsonrpc@v0.3.1/handler.go:444 error in RPC call to 'Filecoin.StorageReportHealth': health report for unknown storage: 1931939e-0af0-430c-9ae5-8d887dc94004:
github.com/filecoin-project/lotus/storage/paths.(*MemIndex).StorageReportHealth
/root/go/src/lotus/storage/paths/index.go:316
2024-04-05T13:43:53.051+0800 WARN rpc go-jsonrpc@v0.3.1/handler.go:444 error in RPC call to 'Filecoin.StorageReportHealth': health report for unknown storage: 67a1352d-a507-434e-890e-c151553a42bc:
github.com/filecoin-project/lotus/storage/paths.(*MemIndex).StorageReportHealth
/root/go/src/lotus/storage/paths/index.go:316
2024-04-05T13:44:03.271+0800 WARN rpc go-jsonrpc@v0.3.1/handler.go:444 error in RPC call to 'Filecoin.StorageReportHealth': health report for unknown storage: 67a1352d-a507-434e-890e-c151553a42bc:
github.com/filecoin-project/lotus/storage/paths.(*MemIndex).StorageReportHealth
/root/go/src/lotus/storage/paths/index.go:316
2024-04-05T13:44:03.271+0800 WARN rpc go-jsonrpc@v0.3.1/handler.go:444 error in RPC call to 'Filecoin.StorageReportHealth': health report for unknown storage: 1931939e-0af0-430c-9ae5-8d887dc94004:
github.com/filecoin-project/lotus/storage/paths.(*MemIndex).StorageReportHealth
The text was updated successfully, but these errors were encountered:
Checklist
Latest release
, the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.Lotus component
Lotus Version
Repro Steps
No response
Describe the Bug
After executing the command lotus-miner storage detach /path/to/storage, the path was indeed removed. However, the miner's log continuously reports an error: error in RPC call to 'Filecoin.StorageReportHealth': health report for unknown storage: 1931939e-0af0-430c-9ae5-8d887dc94004 and similar errors. What could be the reason for this, and how should it be resolved?
Logging Information
The text was updated successfully, but these errors were encountered: