pulp-manage-db does not handle missing /dev/log gracefully
Description of problem:
If pulp-manage-db is run on a machine that does not have /dev/log, the user will see error messages that they do not understand (similar to "Nonetype has no attribute critical"). It would be better if we printed an informative error to stderr and exited with a non-zero exit code.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Take some action to remove /dev/log (stopping rsyslogd might do the trick)
2. Run pulp-manage-db
You will get difficult-to-understand error messages on the console (and obviously, no log messages).
You should get a meaningful error message on the console and a non-zero exit code. Obviously, still nothing should/could be logged.
+ This bug was cloned from Bugzilla Bug #1173310 +