lotus
lotus copied to clipboard
`Lotus daemon --import-chain` errors out
Checklist
- [X] This is not a security-related bug/issue. If it is, please follow please follow the security policy.
- [X] I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
- [X] 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. - [X] I did not make any code changes to lotus.
Lotus component
- [X] 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 v1.26.0
Repro Steps
- Run
lotus daemon --import-chain=/xxxx/xxxxx/xxxx.car.zst --halt-after-import
- Wait while its importing
- Get the error:
2024-04-02T11:26:27.456+0200 INFO main lotus/daemon.go:599 setting genesis
2024-04-02T11:26:27.457+0200 INFO chainstore store/store.go:683 New heaviest tipset! [bafy2bzacecnamqgqmifpluoeldx7zzglxcljo6oja4vrmtj7432rphldpdmm2] (height=0)
2024-04-02T11:26:27.458+0200 WARN chainstore store/store.go:711 no previous heaviest tipset found, using [bafy2bzacecnamqgqmifpluoeldx7zzglxcljo6oja4vrmtj7432rphldpdmm2]
2024-04-02T11:26:27.460+0200 INFO drand drand/drand.go:114 drand beacon without pubsub
2024-04-02T11:26:27.460+0200 WARN chainstore store/store.go:668 reorgWorker quit
2024-04-02T11:26:27.483+0200 INFO badgerbs [email protected]/db.go:1027 Storing value log head: {Fid:115 Len:33 Offset:107228516}
---------
2024-04-02T11:26:30.040+0200 INFO badgerbs [email protected]/db.go:550 Force compaction on level 0 done
ERROR: failed to construct beacon schedule: creating drand beacon: creating drand client: no points of contact specified
Describe the Bug
The lotus daemon --import-chain
cmd currently fails with:
2024-04-02T11:26:27.456+0200 INFO main lotus/daemon.go:599 setting genesis
2024-04-02T11:26:27.457+0200 INFO chainstore store/store.go:683 New heaviest tipset! [bafy2bzacecnamqgqmifpluoeldx7zzglxcljo6oja4vrmtj7432rphldpdmm2] (height=0)
2024-04-02T11:26:27.458+0200 WARN chainstore store/store.go:711 no previous heaviest tipset found, using [bafy2bzacecnamqgqmifpluoeldx7zzglxcljo6oja4vrmtj7432rphldpdmm2]
2024-04-02T11:26:27.460+0200 INFO drand drand/drand.go:114 drand beacon without pubsub
2024-04-02T11:26:27.460+0200 WARN chainstore store/store.go:668 reorgWorker quit
2024-04-02T11:26:27.483+0200 INFO badgerbs [email protected]/db.go:1027 Storing value log head: {Fid:115 Len:33 Offset:107228516}
---------
2024-04-02T11:26:30.040+0200 INFO badgerbs [email protected]/db.go:550 Force compaction on level 0 done
ERROR: failed to construct beacon schedule: creating drand beacon: creating drand client: no points of contact specified
This error is unrelated to the drand quicknet change, and is pointing towards that the cmd is currently broken. The issue was discovered during nv22-testing, where I wrongly used the --import-chain
cmd, when I wanted to actually use the --import-snapshot
cmd.
Logging Information
N/A
@rjan90 To follow up with testing importing a Lotus exported snapshot