Log exception messages in several locations

[drlongle]

High Level Overview of Change

This PR resolves #3213 and logs exception messages at several locations.

Context of Change

At several locations in the code base, we catch an exception but do not log the exception messages. This PR adds code that logs the exception messages. This can be useful for analysis or debugging. The additional logging can have a (small) negative performance impact.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking change that only restructures code)
• Tests (You added tests for code that already exists, or your new feature included in this PR)
• Documentation Updates
• Release

[intelliot]

This is Testable because we can try to trigger some of the exceptions and confirm that they are logged as expected

[mtrippled]

+1 LGTM

[HowardHinnant]

Good catch.

[intelliot]

@drlongle at your convenience, please do the following:

1. resolve the merge conflicts
2. write a proposed commit message (for the entire squashed PR)
3. comment here with that commit message, and confirm that you believe this PR is ready to merge

[drlongle]

I have resolved the conflicts and squashed the commits. The PR is ready to merge.

[intelliot]

Suggested commit message:

Add logging for exceptions: (#4400)

Log exception messages at several locations.

Previously, these were locations where an exception was caught, but the
exception message was not logged. Logging the exception messages can be
useful for analysis or debugging. The additional logging can have a
small negative performance impact.

Fix #3213.

@drlongle please confirm this looks good, or suggest an alternative.

[drlongle]

@intelliot Looks good. Thanks!