[Pulp-list] Problem starting pulp-server - think it's relating to mongodb...

[Dunkley, Stephen]

When I try to start pulp-server it for the first time, I get the
following...

# service pulp-server start
Pulp database not initialized, please run: /etc/init.d/pulp-server init

...so I start it with the init parameter...

# service pulp-server init
Starting mongod: [ OK ]
Traceback (most recent call last):
File <http://www.linuxforums.org/forum/>  "/usr/bin/pulp-migrate", line
19, in ?
from pulp.server.db.migrate import script
File
"/usr/lib/python2.4/site-packages/pulp/server/db/migrate/script.py",
line 27, in ?
connection.initialize()
File "/usr/lib/python2.4/site-packages/pulp/server/db/connection.py",
line 42, in initialize
_connection = pymongo.Connection(seeds)
File "/usr/lib64/python2.4/site-packages/pymongo/connection.py", line
184, in __init__
self.__find_master()
File "/usr/lib64/python2.4/site-packages/pymongo/connection.py", line
456, in __find_master
raise AutoReconnect("could not find master")
pymongo.errors.AutoReconnect: could not find master

...I suspect this is because pulp uses mongodb, and mongodb doesn't look
to be starting properly. When I start it manually, I get the
following...

# service mongod start
Starting mongod: [ OK ]

...which looks OK, but the log file reports...

Tue Jan 25 13:01:11 MongoDB starting : pid=13069 port=27017
dbpath=/var/lib/mongodb 64-bit
Tue Jan 25 13:01:11 db version v1.6.4, pdfile version 4.5
Tue Jan 25 13:01:11 git version: nogitversion
Tue Jan 25 13:01:11 sys info: Linux x86-11.phx2.fedoraproject.org
2.6.32-71.el6.x86_64 #1 SMP Wed Sep 1 01:33:01 EDT 2010 x86_64
BOOST_LIB_VERSION=1_33_1
Tue Jan 25 13:01:11 [initandlisten] Accessing: local for the first time
Tue Jan 25 13:01:11 [initandlisten] query local.system.namespaces
reslen:36 nreturned:0 1ms
Tue Jan 25 13:01:11 Got signal: 11 (Segmentation fault).

Tue Jan 25 13:01:11 Backtrace:
0x7b5b14 0x36736302d0
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x384) [0x7b5b14]
/lib64/libc.so.6 [0x36736302d0]

Tue Jan 25 13:01:11 dbexit:

Tue Jan 25 13:01:11 [initandlisten] shutdown: going to close listening
sockets...
Tue Jan 25 13:01:11 [initandlisten] shutdown: going to flush oplog...
Tue Jan 25 13:01:11 [initandlisten] shutdown: going to close sockets...
Tue Jan 25 13:01:11 [initandlisten] shutdown: waiting for fs
preallocator...
Tue Jan 25 13:01:11 [initandlisten] shutdown: closing all files...
Tue Jan 25 13:01:11 closeAllFiles() finished

Tue Jan 25 13:01:11 [initandlisten] shutdown: removing fs lock...
Tue Jan 25 13:01:11 dbexit: really exiting now

...so it looks like it tries to start, and then gets a segmentation
fault and shuts down.

Any ideas as to the cause of the problem?

 

Stephen Dunkley


This e-mail may contain information which is confidential, legally privileged and/or copyright protected. This e-mail is intended for the addressee only. If you receive this in error, please contact the sender and delete the material from your computer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20110125/497801cd/attachment.htm>