MongoDB 2.6 Update Error on CentOS using yum

[Juan Carlos Farah]

Hi All,

I'm trying to update MongoDB 2.4 to 2.6 on my 64-bit CentOS machine. I have removed the old 10gen repository package and created the /etc/yum.repos.d/mongodb.repo file with the new configuration as explained in the docs.

However, when I run sudo yum install mongodb-org, I get the following error:

Error: mongodb-org conflicts with mongodb-org-server

This is the output in the shell:

Setting up Install Process

Resolving Dependencies

--> Running transaction check

---> Package mongodb-org.x86_64 0:2.6.1-0.1.rc0 will be installed

--> Processing Dependency: mongodb-org-server = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64

--> Processing Dependency: mongodb-org-shell = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64

--> Processing Dependency: mongodb-org-mongos = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64

--> Processing Dependency: mongodb-org-tools = 2.6.1 for package: mongodb-org-2.6.1-0.1.rc0.x86_64

--> Running transaction check

---> Package mongodb-org-mongos.x86_64 0:2.6.1-0.1.rc0 will be installed

---> Package mongodb-org-server.x86_64 0:2.6.1-0.1.rc0 will be installed

---> Package mongodb-org-shell.x86_64 0:2.6.1-0.1.rc0 will be installed

---> Package mongodb-org-tools.x86_64 0:2.6.1-0.1.rc0 will be installed

--> Processing Conflict: mongodb-org-2.6.1-0.1.rc0.x86_64 conflicts mongo-10gen-server

--> Finished Dependency Resolution

Error: mongodb-org conflicts with mongodb-org-server

 You could try using --skip-broken to work around the problem

 You could try running: rpm -Va --nofiles --nodigest

Has anyone else encountered anything similar? What is the best course of action here? Should I try using the --skip-broken option? I did a fresh installation in a new box a couple of days ago and did not encounter any problems.

I have posted a question on Stack Overflow as well, if you would prefer to answer there:

http://stackoverflow.com/questions/23231716/mongodb-2-6-update-error-on-centos-using-yum

Thanks for your help with this.

Juan-Carlos

[Ernie Hershey]

Hi Juan,

I think the error you're seeing was the result of a bug in how MongoDB RC packages are generated and has been corrected in new packages in the same repo. If you run "yum makecache" to update your repo metadata and run the same commands again, it should work.

Ernie

--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
 
For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user...@googlegroups.com.
To post to this group, send email to mongod...@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/13a71cea-ca4c-470a-8ee1-cd4d74c1a57b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Juan Carlos Farah]

Hi Ernie,

Thanks for this. Running "yum makecache" indeed got it to work. However, just one question about the version that was installed when I ran "yum install mongodb-org":

# mongod --version

db version v2.6.1-rc0

Should it be installing the rc?

Thanks again,

Juan Carlos

[Eduar Tua]

Guys I'm using the Ubuntu's last version, I'm joining now to the MongoDB world.

Following the Install On Linux notes from documentation I've got some error when I try to start the server:

Steps that I've followed:

1) Import the public key used by the package management system

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 7F0CEB10

2) Create a list file for MongoDB

echo 'deb http://downloads-distro.mongodb.org/repo/ubuntu-upstart dist 10gen' | sudo tee /etc/apt/sources.list.d/mongodb.list

3) Reload Local Package database

sudo aptitude update

4) Install the Mongo Package Database

4.1 Install the last version 

sudo aptitude install mongodb-org

4.2 Install a Specific Version of MongoDB (chosen)

aptitude install mongodb-org=2.6.1 mongodb-org-server=2.6.1 mongodb-org-shell=2.6.1 mongodb-org-mongos=2.6.1 mongodb-org-tools=2.6.1

Pin a Specific version

echo "mongodb-org hold" | sudo dpkg --set-selections
echo "mongodb-org-server hold" | sudo dpkg --set-selections
echo "mongodb-org-shell hold" | sudo dpkg --set-selections
echo "mongodb-org-mongos hold" | sudo dpkg --set-selections
echo "mongodb-org-tools hold" | sudo dpkg --set-selections

Now for start MongoDB

sudo /etc/init.d/mongod start

And I got from Console this:

Rather than invoking init scripts through /etc/init.d, use the service(8)

utility, e.g. service mongod start

Since the script you are attempting to invoke has been converted to an

Upstart job, you may also use the start(8) utility, e.g. start mongod

I'm Using the last version of Ubuntu 14.04.

[Eduar Tua]

I've found this in the log file

2014-05-07T22:13:13.944-0400 [initandlisten] MongoDB starting : pid=23284 port=27017 dbpath=/var/lib/mongodb 64-bit host=eduar-Dell-System-XPS-L502X

2014-05-07T22:13:13.944-0400 [initandlisten] db version v2.6.1

2014-05-07T22:13:13.944-0400 [initandlisten] git version: 4b95b086d2374bdcfcdf2249272fb552c9c726e8

2014-05-07T22:13:13.944-0400 [initandlisten] build info: Linux build14.nj1.10gen.cc 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49

2014-05-07T22:13:13.944-0400 [initandlisten] allocator: tcmalloc

2014-05-07T22:13:13.944-0400 [initandlisten] options: { config: "/etc/mongod.conf", net: { bindIp: "127.0.0.1" }, storage: { dbPath: "/var/lib/mongodb" }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongod.log" } }

2014-05-07T22:13:14.018-0400 [initandlisten] journal dir=/var/lib/mongodb/journal

2014-05-07T22:13:14.018-0400 [initandlisten] recover : no journal files present, no recovery needed

2014-05-07T22:13:14.125-0400 [initandlisten] waiting for connections on port 27017

2014-05-07T22:14:14.127-0400 [clientcursormon] mem (MB) res:35 virt:349

2014-05-07T22:14:14.127-0400 [clientcursormon]  mapped (incl journal view):160

2014-05-07T22:14:14.127-0400 [clientcursormon]  connections:0

2014-05-07T22:19:14.142-0400 [clientcursormon] mem (MB) res:36 virt:350

2014-05-07T22:19:14.142-0400 [clientcursormon]  mapped (incl journal view):160

2014-05-07T22:19:14.142-0400 [clientcursormon]  connections:0

2014-05-07T22:24:14.158-0400 [clientcursormon] mem (MB) res:36 virt:350

2014-05-07T22:24:14.158-0400 [clientcursormon]  mapped (incl journal view):160

2014-05-07T22:24:14.158-0400 [clientcursormon]  connections:0

2014-05-07T22:29:14.173-0400 [clientcursormon] mem (MB) res:36 virt:350

2014-05-07T22:29:14.174-0400 [clientcursormon]  mapped (incl journal view):160

2014-05-07T22:29:14.174-0400 [clientcursormon]  connections:0

On Tuesday, April 22, 2014 8:27:09 PM UTC-4, Ernie Hershey wrote:

[Ernie Hershey]

Hi Eduar,

The message you're seeing about upstart is a warning and won't prevent the command from functioning. Based on the output you posted, mongod is already running, so you shouldn't need to start it. Your installation was successful. 

Ernie