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

out of memory #1240

Closed
me639276639936 opened this issue May 23, 2023 · 4 comments
Closed

out of memory #1240

me639276639936 opened this issue May 23, 2023 · 4 comments

Comments

@me639276639936
Copy link

me639276639936 commented May 23, 2023

Describe the issue:
Sync fails with "out of memory" error, even though task manager on RPI shows sync was only using half of available RAM.

What behavior did you expect? To sync the Liquid Chain successfully.

To reproduce issue: Run elementsd

What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? Bitcoin Core v22.0.0, from Bitcoin Core website

What type of machine are you observing the error on (OS/CPU and disk type)? RPI4, 8GB Ram, 128 GB SD

GUI-related issue? What is your operating system and its version? If Linux, what is your desktop environment and graphical shell? Raspian

Any extra information that might be useful in the debugging process:

bitcoin.conf settings
server=1
daemon=1
rpcuser=....my user
rpcpassword=...my password
datadir=/home/usr/.bitcoin
prune=1000
dbcache=100
maxmempool=200
maxconnections=30
par=1

elements.conf settings
mainchainrpcuser=....my user
mainchainrpcpassword=...my password
mainchaindatadir=/home/usr/.bitcoin
prune=1000
dbcache=100
maxmempool=200
maxconnections=30
par=1
chain=liquidv1

@psgreco
Copy link
Contributor

psgreco commented May 23, 2023

which version of elements are you using?
in low memory environments, it's recommended to use the experimental setting trim_headers=1.

Also, you might have to remove the chain and sync from scratch when you go from non trim_headers to trim_headers, you can change it back and forth after it is synced

@me639276639936
Copy link
Author

me639276639936 commented May 23, 2023 via email

@me639276639936
Copy link
Author

me639276639936 commented May 25, 2023 via email

@psgreco
Copy link
Contributor

psgreco commented May 25, 2023

Thanks for letting us know, closing..,

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

2 participants