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.

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

Lotus daemon --import-chain errors out #11802

Open
5 of 11 tasks
rjan90 opened this issue Apr 2, 2024 · 1 comment
Open
5 of 11 tasks

Lotus daemon --import-chain errors out #11802

rjan90 opened this issue Apr 2, 2024 · 1 comment
Assignees
Labels
kind/bug Kind: Bug

Comments

@rjan90
Copy link
Contributor

rjan90 commented Apr 2, 2024

Checklist

  • 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 v1.26.0

Repro Steps

  1. Run lotus daemon --import-chain=/xxxx/xxxxx/xxxx.car.zst --halt-after-import
  2. Wait while its importing
  3. 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	v2@v2.2007.4/db.go:1027	Storing value log head: {Fid:115 Len:33 Offset:107228516}
---------
2024-04-02T11:26:30.040+0200	INFO	badgerbs	v2@v2.2007.4/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	v2@v2.2007.4/db.go:1027	Storing value log head: {Fid:115 Len:33 Offset:107228516}
---------
2024-04-02T11:26:30.040+0200	INFO	badgerbs	v2@v2.2007.4/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 rjan90 added the kind/bug Kind: Bug label Apr 2, 2024
@rjan90
Copy link
Contributor Author

rjan90 commented Apr 23, 2024

@rjan90 To follow up with testing importing a Lotus exported snapshot

@rjan90 rjan90 self-assigned this May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Kind: Bug
Projects
None yet
Development

No branches or pull requests

1 participant