[UPDATE: 26 August 2017 – The binaries referenced in this post only work with Raspbian Jessie! If you have upgraded to Raspbian Stretch on a R-Pi 3 or R-Pi 3B+, get the newer binaries]
The mongoDB documentation at mongodb.com states that 32-bit binaries are deprecated with release 3.2 and will be unavailable in future releases. The latest version with 32-bit support (i.e. R-Pi with Raspbian) is 3.0.14 as of March, 2017. I have compiled MongoDB 3.0.14 for Raspberry Pi 2 and 3. I needed a few tweaks to the build process I used to compile 3.0.9 and associated tools. Use the installation instruction in my previous blog post to install and run MongoDB 3.0.14 on R-Pi. The only change is to download newer files. I have compiled MongoDB and Tools with the SSL flag — so the SSL option is available.
You can download a gzip file of the MongoDB core binaries v3.0.14 from here.
md5sum: 46bf23049406f02f5379d1d286a5e4f3 core_mongodb_3_0_14.tar.gz
You can download a gzip file of the MongoDB tools v3.0.14 from here.
md5sum: bc1ca8c3346758e338e0490548c6567e tools_mongodb_3_0_14.tar.gz
Installation and use instructions can be found in my previous blog entry: MongoDB 3.0.9 binaries for Raspberry Pi
[…] (18 Mar 2017) I have compiled version 3.0.14 and created binaries for the R-Pi 2 & 3. I have confirmed that the instructions in this blog entry work with the new […]
Thank you very very much, Andy.
It was very kind of you to compile it for us.
Hello Andy, would you recommend to run mongodb with node.js to act as an HMI (small Industrial process display) to capture and display in realtime some monitoring points? Wandering about the load of MongoDB on the Pi3.
Thanks you 🙂
Stephane, the quick answers is, “sure!” The longer answer is, “maybe.” an R-Pi 3 certainly can run MongoDB and node.js — and fairly efficiently. I don’t think I would run both AND use a browser to view, on the same R-Pi. I would run Raspbian-Lite on the R-Pi in headless mode, maybe reduce Graphics RAM allocation and use an external USB drive for storage. I would view the node.js “output” in a browser on another computer. The input method of data and number/rate of transactions might also determine suitability of using an R-Pi. One of the cool (& useful) things you could do is have replication failover for your MongoDB DBs to other R-Pis. This is the configuration I run.
LMKif you have more specific questions.
Thanks alot Andy this was very helpful, i copied these binaries over in the directory on my DS215J synology NAS and it seems to be running as it should 🙂
Thanks for this post.
I have used this in my last project. However now I am working on latest RASPBIAN STRETCH OS.
Any chances of you updating this post for RASPBIAN STRETCH in near future?
I tried the existing instructions but no luck.
I’ll fire-up Raspbian Stretch and see what the issues are — and what I can do to address 😉
Eagerly waiting for it.
Check out: http://andyfelong.com/2017/08/mongodb-3-0-14-for-raspbian-stretch/ for Stretch compatible binaries
When I try run manual with this command: sudo -u mongodb mongod –rest –fork –config /etc/mongodb.conf
That error is show to me:
mongod: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
can you help me?
I have a raspberry pi 3 B with raspian
Thiago, seems like you are running Raspbian Stretch (or possibly an updated Jessie) which has different SSL libraries that are incompatible with the MongoDB binaries you are trying to use. Download my new binaries that have beem compiled for Raspbian Stretch – check out this blog entry: http://andyfelong.com/2017/08/mongodb-3-0-14-for-raspbian-stretch/ LMK how it goes!
Hi Andy, thank you for yout attention.
Now installed the version stretch and the another error shows to me.
root@raspberrypi:/tmp/tools# service mongodb status
● mongodb.service – An object/document-oriented database
Loaded: loaded (/lib/systemd/system/mongodb.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2017-10-22 15:57:47 -02; 2s ago
Process: 17831 ExecStart=/usr/bin/mongod –config /etc/mongodb.conf (code=exited, status=1/FAILURE)
Main PID: 17831 (code=exited, status=1/FAILURE)
out 22 15:57:47 raspberrypi systemd: Started An object/document-oriented database.
out 22 15:57:47 raspberrypi systemd: mongodb.service: Main process exited, code=exited, status=1/FAILURE
out 22 15:57:47 raspberrypi systemd: mongodb.service: Unit entered failed state.
out 22 15:57:47 raspberrypi systemd: mongodb.service: Failed with result ‘exit-code’.
If you can help me, I am so thank you.
apparently when I run mongod it works ok.
I don`t know why, but, when I try to execute mongod with mongd user, there is show an exception .
when I run direct from root, it works
check all files – owner & permissions:
sudo chown mongodb:nogroup /var/log/mongodb
sudo chown mongodb:root /var/lib/mongodb
sudo chmod 775 /var/lib/mongodb
– You might also have exisiting files with bad owner/permissions in /var/lib/mongodb. You might want to delete and recreate… Look at this blog entry: http://andyfelong.com/2016/01/mongodb-3-0-9-binaries-for-raspberry-pi-2-jessie/
I really thank you so much!
Now, everything look good here, after I reinstalling and reviewing all permissons
Thank you so much Andy, your work is so much appreciated !
Hi, thanks for providing the binaries!
I have a question for you though. I’m a stuck with a 32-bit pi, and I was wondering if there was a way to overcome the 2GB limitation.
In my understanding, the new storage engine introduced by MongoDB 3.0, WiredTiger (see https://docs.mongodb.com/manual/release-notes/3.0/), should not be subject to this limitation (see https://docs.mongodb.com/manual/reference/limits/#Data-Size), though not being the default engine until version 3.2.
Have you ever given it a try?
Sorry but WiredTiger 2.5.3 for MongoDB 3.0 requires a 64-bit OS — per WiredTiger Reference Guide: http://source.wiredtiger.com/2.5.3/
Thanks for putting this together..I’ve been struggling for a couple of days getting an older version to run on my pi, but was newer than the 2.4.14 that is downloading from the repos on the pi. I’m running in to this error when I run ‘sudo service mongodb status’ after i ‘start’ .. Does anyone have an idea?
● mongodb.service – High-performance, schema-free document-oriented database
Loaded: loaded (/lib/systemd/system/mongodb.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2018-10-18 00:35:37 CDT; 2s ago
Process: 1371 ExecStart=/usr/bin/mongod –quiet –config /etc/mongodb.conf (code=exited, status=127)
Main PID: 1371 (code=exited, status=127)
Oct 18 00:35:37 WebPi systemd: Started High-performance, schema-free document-oriented database.
Oct 18 00:35:37 WebPi systemd: mongodb.service: Main process exited, code=exited, status=127/n/a
Oct 18 00:35:37 WebPi systemd: mongodb.service: Unit entered failed state.
Oct 18 00:35:37 WebPi systemd: mongodb.service: Failed with result ‘exit-code’.
I believe you have found the issue – i.e. different Raspbian version. Using the build for Stretch should work 🙂
[…] I have compiled version 3.0.14 and created binaries for Raspbian Jessie for the R-Pi 2 & 3. NEW: I have also created 3.0.14 binaries for the R-Pi 3 running Raspbian Stretch that […]