[SERVER-14786] Mongodb installation on debian Created: 05/Aug/14 Updated: 01/Apr/15 Resolved: 20/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lochan Marwaha | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 1 |
| Labels: | build-later, build-needs-definition | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Hi, Installation for mongodb on debian is not smoooth. Also it doesn't work correctly. I followed the below link provided by mongodb, but still it fails http://docs.mongodb.org/manual/tutorial/install-mongodb-on-debian/ So after downloading the packages, it throws the error Get:1 http://downloads-distro.mongodb.org/repo/debian-sysvinit/ dist/10gen mongodb-org-shell amd64 2.6.3 [4,451 kB] So in configuration files you need to change the dbpath or different variables and owner of different location to work it out. Also as suggested by mongodb to have a dedicated OS user for mongodb will not work because pid is not configurable till 2.6 release. So you always have to do sudo to start the mongo database. I believe we need to fix this and have smooth installation and run in Debian. Any suggestions please. |
| Comments |
| Comment by Ernie Hershey [ 28/Feb/15 ] | |||||||||||||||||
|
lochanmarwaha@gmail.com - The installation got to the end but couldn't start the database. Do you have anything in /var/log/mongodb/mongod.log after the failed installation? One common reason that the server fails to start is not having enough space on the filesystem containing data files, in this case, /var/lib/mongodb. Is the filesystem that directory is on very small? | |||||||||||||||||
| Comment by Laurent Roger [ 01/Oct/14 ] | |||||||||||||||||
|
I was able to fix this issue with the following steps :
| |||||||||||||||||
| Comment by Daryl Tucker [ 30/Sep/14 ] | |||||||||||||||||
|
I used an older method of installing MongoDB, where the packages had the *-10gen* suffix. I've been able to upgrade a few times without any issues, but today I experienced this issue. I made sure to remove the older *-10gen sources and made sure I had the new *-org sources. I tried removing mongo-*, as well as installing specific versions of every package (ie: -server -console), which didn't work. Finally, I manually killed the mongo server (`ps aux | grep mongo`), and just ran a normal upgrade, which worked. It seems there was an issue with killing the older version to 'configure' the newer one. |