Author

Topic: Bitcoind / litecoind error: db11exception cannot allocate memory (3 LTC Reward) (Read 1785 times)

legendary
Activity: 1512
Merit: 1000
By using lsof and sysctl you can check if it's an file limit issue. You can find some good examples here:
http://www.cyberciti.biz/tips/linux-procfs-file-descriptors.html

If it's a limit problem you can change that permanently:
http://oschgan.com/drupal/node/57

You can find some ideas here too:
https://bitcointalksearch.org/topic/exception-11dbexception-dbopen-invalid-argument-bitcoin-in-run-89639
sr. member
Activity: 644
Merit: 250
I'm using an ext3 filesystem that should support large enough file sizes.

Also, I'm not running it on a VM.
kjj
legendary
Activity: 1302
Merit: 1025
This message usually means that you are running on a VM.
legendary
Activity: 1540
Merit: 1002
strange but cant see it being file size issues as the database gets split at 2GB, i cant really help with linux i cry when i try to use it XD maybe try changing the disk type to something else...
sr. member
Activity: 644
Merit: 250
I also tried the pre-compiled binary and got the same error message.
sr. member
Activity: 644
Merit: 250
Here's the exact error message.  It just keeps repeating.

*************************
EXCEPTION: 11DbException
DbEnv::txn_begin: Cannot allocate memory
litecoin in ProcessMessages()
sr. member
Activity: 644
Merit: 250
Apparently, Ubuntu users don't have this problem.  Spent all night googling this.  I can't believe other users haven't experienced this same problem, because Debian is so popular.

Any help would be appreciated.  Thanks
sr. member
Activity: 644
Merit: 250
Update: I'm now offering a 3 Ltc Reward to anyone who can fix this issue for me.

I'm running debian amd64 stable and sid on multiple machines.  Every time I try to download the blockchain for bitcoin or litecoin using bitcoind or litecoind, I can only download so many blocks and then I get a repeating error stating, "db11exception::txn: cannot allocate memory"

I'm not running out of physical memory.  I think this may have to do with a file/size limit set on debian.  I tried the command "ulimit -n 2048" but that didn't work.

Anybody have the same problem or know how to fix it?
Jump to: