We had a user today who has some exception happening early on during pulp-manage-db. We aren't sure what the exception is because it happens before pulp-manage-db sets up logging. This led to this error message on stderr: No handler could be found for logger "pulp.server.db.connection" Here are steps to reproduce: 1) Stop mongod (service mongod stop) 2) Run pulp-manage-db 3) Observe that pulp-manage-db seems to hang forever, and prints this message to the screen: 'No handler could be found for logger "pulp.server.db.connection"' We should fix it so that the user is given an informative message that Mongo can't be reached, and pulp-manage-db should exit. To verify that this bug is fixed: 1) Stop mongod (service mongod stop) 2) Run pulp-manage-db 3) Observe the pulp-manage-db exits, and prints a useful error message.
This has been fixed by several commits over the last couple of months which will be included in 2.6.
fixed in pulp 2.6.0-0.2.beta
>> rpm -qa | grep pulp-server pulp-server-2.6.0-0.2.beta.el6.noarch >> service mongod stop Stopping mongod: [ OK ] >> sudo -u apache pulp-manage-db Could not connect to MongoDB at localhost:27017: Cannot connect to database default : could not connect to localhost:27017: [Errno 111] Connection refused ... Waiting 1 seconds and trying again. Could not connect to MongoDB at localhost:27017: Cannot connect to database default : could not connect to localhost:27017: [Errno 111] Connection refused ... Waiting 1 seconds and trying again. Could not connect to MongoDB at localhost:27017: Cannot connect to database default : could not connect to localhost:27017: [Errno 111] Connection refused ... Waiting 1 seconds and trying again. >> service mongod start Starting mongod: [ OK ] >>sudo -u apache pulp-manage-db Mongo database for connection is version 2.4.12 Loading content types. .... Database migrations complete.
Moved to https://pulp.plan.io/issues/483