When the plan executor fails for some commands, starting from SERVER-41996 an error message is logged before propagating the exception (e.g. in those snippets for distinct and find).

While upon some failures it's easy to trace back which command caused the exception, tests with no sufficient logging or concurrent commands are making it difficult to map specific commands to errors.

Logging the original command together with the error message would allow to identify problems in a fast and effective way