Topic: ArmoryDB on Raspberry Pi 3 (Read 221 times)
Thanks for your your helpfull guidance!!
Oh, I understand. So then I only would be able to build it in rPi if I had installed a 64bit linux on my Pi, which I haven't...
You could theoretically build the BARE db on a Pi assuming you use the lowest ram-usage setting. That DB is small enough that you won't run into LMDB issues, but you also have to consider total process RAM, which could exceed the addressable memory as a whole.
The issue isn't the amount of memory, it's addressable space. LMDB maps all on disk data into memory. If that value exceeds the process addressable memory, you will get a critical failure. On 32 bit systems, process addressable memory maxes out around 2~3GB. Therefor, any file LMDB uses that exceeds 2GB in size cannot be created nor used on a 32bit system. This is a long winded way to saying please don't try this.
Oh, I understand. So then I only would be able to build it in rPi if I had installed a 64bit linux on my Pi, which I haven't...
The issue isn't the amount of memory, it's addressable space. LMDB maps all on disk data into memory. If that value exceeds the process addressable memory, you will get a critical failure. On 32 bit systems, process addressable memory maxes out around 2~3GB. Therefor, any file LMDB uses that exceeds 2GB in size cannot be created nor used on a 32bit system. This is a long winded way to saying please don't try this.
If you insist on attempting this setup, you should do it the smart way: create a 32bit VM of some Debian flavored distro, the closest you can to the target Raspbian version. Give this VM a copy of the blockchain, then build the smallest existing Armory DB on that VM (db-type=DB_BARE). This will give you a ~200MB database. Then take this DB with the relevant copy of the chain your Pi and cross your fingers.
If you insist on attempting this setup, you should do it the smart way: create a 32bit VM of some Debian flavored distro, the closest you can to the target Raspbian version. Give this VM a copy of the blockchain, then build the smallest existing Armory DB on that VM (db-type=DB_BARE). This will give you a ~200MB database. Then take this DB with the relevant copy of the chain your Pi and cross your fingers.
Do you think that using some swap space in my Pi would do the trick? In this way I would have enough memory to create the DB directly on the Pi.
Yup! I saw that it complains about some .lmdb files are not LMDB format...
Also I don't think the meta entries for LMDB are even the same going from 64 to 32 bits. It's typically bound to the pointer size, which naturally differs between 64 and 32 bits.
Yup! I saw that it complains about some .lmdb files are not LMDB format...
DB is tied to the ondisk blockchain. You can't move a DB around to a different copy of the chain. Also I don't think the meta entries for LMDB are even the same going from 64 to 32 bits. It's typically bound to the pointer size, which naturally differs between 64 and 32 bits.
I'm not running ArmoryQt on Pi3. Only ArmoryDB :-)
I compiled it directly on Pi. I think you can use make server as it doesn't need any dependencies, I think. Try it.
I tried to create a new databases build from scratch in my desktop PC, moved ".armory" to my pi and ArmoryDB is stuck at the same point commented above...
I compiled it directly on Pi. I think you can use make server as it doesn't need any dependencies, I think. Try it.
I tried to create a new databases build from scratch in my desktop PC, moved ".armory" to my pi and ArmoryDB is stuck at the same point commented above...
I see a .cookie_ file in .armory directory. I think this is new. Could it be related to this behavior?
.cookie_ is generated whenever Armory kicks off ArmoryDB. I don't think it'll cause any issues. To be safe, if Armory and ArmoryDB aren't running, delete the cookie and try again. If it still doesn't work, I don't know what's happening. I finally broke down and bought an RPi3 but it'll be awhile before I get around to playing with cross-compiling and running Armory on it. Don't wait on me.
It's still running and stuck. It does nothing at all.
The only thing I did was to copy .armory/databases from my desktop computer to my pi.
Anything else I should know? I've been googling with no luck...
I see a .cookie_ file in .armory directory. I think this is new. Could it be related to this behavior?
The only thing I did was to copy .armory/databases from my desktop computer to my pi.
Anything else I should know? I've been googling with no luck...
I see a .cookie_ file in .armory directory. I think this is new. Could it be related to this behavior?
I copied databases directory and now it got stuck:
Code:
$ ./ArmoryDB --ram-usage=1
/home/pi
/home/pi
logging in /home/pi/.armory/dbLog.txt
-INFO - 22:14:10: (main.cpp:32) Running on 4 threads
-INFO - 22:14:10: (main.cpp:33) Ram usage level: 1
-INFO - 22:14:10: (BlockUtils.cpp:915) blkfile dir: /home/pi/.bitcoin/blocks
-INFO - 22:14:10: (BlockUtils.cpp:916) lmdb dir: /home/pi/.armory/databases
-INFO - 22:14:10: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 22:14:10: (BDM_Server.h:263) Listening on port 9001
/home/pi
/home/pi
logging in /home/pi/.armory/dbLog.txt
-INFO - 22:14:10: (main.cpp:32) Running on 4 threads
-INFO - 22:14:10: (main.cpp:33) Ram usage level: 1
-INFO - 22:14:10: (BlockUtils.cpp:915) blkfile dir: /home/pi/.bitcoin/blocks
-INFO - 22:14:10: (BlockUtils.cpp:916) lmdb dir: /home/pi/.armory/databases
-INFO - 22:14:10: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 22:14:10: (BDM_Server.h:263) Listening on port 9001
haha! great!
I think I only need to copy .armory/databases. Am I right?
thanks!!
I think I only need to copy .armory/databases. Am I right?
thanks!!
Don't build the db on a Pi
I'm running ArmoryDB --ram-usage=1 on a RPI3 but it always fails with this message after a while:
This is the first time running it, so it is building the DB.
Code:
mdb_enlarge_map failed with error: "Cannot allocate memory", id: 12
ran out of new map indexes
ran out of new map indexes
This is the first time running it, so it is building the DB.
Jump to: