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

blockbook-zcash service fails to start #299

Closed
f4GGT opened this issue Oct 3, 2019 · 1 comment
Closed

blockbook-zcash service fails to start #299

f4GGT opened this issue Oct 3, 2019 · 1 comment

Comments

@f4GGT
Copy link
Contributor

f4GGT commented Oct 3, 2019

1- Checked the backend-zcash service and its in full sync and working
2- When I checked blockbook-zcash service this was the output

Oct 03 05:25:22 ns3142437 systemd[1]: blockbook-zcash.service: Failed with result 'exit-code'.
Oct 03 05:25:22 ns3142437 systemd[1]: blockbook-zcash.service: Service hold-off time over, scheduling restart.
Oct 03 05:25:22 ns3142437 systemd[1]: Stopped Blockbook daemon (Zcash).
Oct 03 05:25:22 ns3142437 systemd[1]: blockbook-zcash.service: Start request repeated too quickly.
Oct 03 05:25:22 ns3142437 systemd[1]: Failed to start Blockbook daemon (Zcash).
Oct 03 05:25:22 ns3142437 systemd[1]: blockbook-zcash.service: Unit entered failed state.
Oct 03 05:25:22 ns3142437 systemd[1]: blockbook-zcash.service: Failed with result 'exit-code'.
  1. last log on blockbook/zcash/logs/
Log file created at: 2019/10/03 05:25:22
Running on machine: ns3142437
Binary: Built with gc go1.12.4 for linux/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
E1003 05:25:22.225649   21536 blockbook.go:185] internalState: database is in inconsistent state and cannot be used
  1. Memory
              total        used        free      shared  buff/cache   available
Mem:             65          34           3           0          27          32
Swap:             3           1           2

  1. BTC & BCASH fullnode + rocksdb are in full sync

Please advice on how to debug this ?

@martinboehm
Copy link
Contributor

Hi, here is a copy from our main README file:

Error internalState: database is in inconsistent state and cannot be used

Blockbook was killed during the initial import, most commonly by OOM killer. By default, Blockbook performs the initial import in bulk import mode, which for performance reasons does not store all the data immediately to the database. If Blockbook is killed during this phase, the database is left in an inconsistent state.

See above how to reduce the memory footprint, delete the database files and run the import again.

Check this or this issue for more info.

@f4GGT f4GGT closed this as completed Oct 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@martinboehm @f4GGT and others