Issue #483
closed
pulp-manage-db doesn't set up logging early enough
Description
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 bug was cloned from Bugzilla Bug #1127846 +
.