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

[BUG] LOTUS_ENABLE_CHAINSTORE_FALLBACK=1 invalid #6055

Open
rickiey opened this issue Apr 16, 2021 · 6 comments
Open

[BUG] LOTUS_ENABLE_CHAINSTORE_FALLBACK=1 invalid #6055

rickiey opened this issue Apr 16, 2021 · 6 comments
Labels
need/analysis Hint: Needs Analysis

Comments

@rickiey
Copy link

rickiey commented Apr 16, 2021

When I set LOTUS_ENABLE_CHAINSTORE_FALLBACK=1 and then start lotus daemon:

$ lotus daemon --halt-after-import --import-snapshot complete_chain_with_finality_stateroots_latest.car            

$ cat /etc/systemd/system/lotus-daemon.service
[Unit]
Description=Lotus Daemon
After=network-online.target
Requires=network-online.target

[Service]
Environment=GOLOG_FILE="/var/log/lotus/daemon.log"
Environment=GOLOG_LOG_FMT="json"
Environment=LOTUS_ENABLE_CHAINSTORE_FALLBACK=1
ExecStart=/usr/local/bin/lotus daemon
Restart=always
RestartSec=2

#MemoryAccounting=true
MemoryHigh=80G
MemoryMax=100G
LimitNOFILE=8192:50240

[Install]
WantedBy=multi-user.target


$ systemctl start lotus-daemon.service

An error occurred when I query some historical data:
{\"code\": 1, \"msg\"\": load state tree: failed to load state tree: failed to load hamt node: blockstore: block not found}"}

@rickiey
Copy link
Author

rickiey commented Apr 16, 2021

After magik6k Fix fallback chainstore #6003

@rickiey
Copy link
Author

rickiey commented Apr 16, 2021

lotus version 1.7.0-dev+mainnet+git.b54b1303f

@jennijuju
Copy link
Member

jennijuju commented Apr 16, 2021

After magik6k Fix fallback chainstore #6003

The error is suggesting you dont have the state.
Are you reimporting a snapshot on a clear datastore? If not - you need to make sure that the epoch of the last block is no later than the epoch of the first block the snapshot contains.Or if there isn't much historic state accesses, LOTUS_ENABLE_CHAINSTORE_FALLBACK=1 should work

@jennijuju jennijuju added need/author-input Hint: Needs Author Input and removed hint/needs-triaging kind/bug Kind: Bug labels Apr 16, 2021
@rickiey
Copy link
Author

rickiey commented Apr 19, 2021

I have removed datastore/chain, and reimporting https://fil-chain-snapshots-fallback.s3.amazonaws.com/mainnet/complete_chain_with_finality_stateroots_latest.car;
It is normal in v1.5.3, An error occurred in v1.6.0: #5975, magik6k fixed it: #6003, Then when I re-imported an error occurred: block not found

@jennijuju jennijuju added need/analysis Hint: Needs Analysis and removed need/author-input Hint: Needs Author Input labels Apr 19, 2021
@donnol
Copy link

donnol commented May 8, 2021

I use v1.9.0rc1 to build lotus, and start with LOTUS_ENABLE_CHAINSTORE_FALLBACK=1 env. I got 'block not found' error too. I want to know if the lotus node will pull missing state/receipts from the network with that env. And if true, why it doesn't work?

@rickiey
Copy link
Author

rickiey commented Jul 7, 2021

v1.10.1 Still fail

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/analysis Hint: Needs Analysis
Projects
None yet
Development

No branches or pull requests

5 participants