-
Type: Bug
-
Resolution: Fixed
-
Priority: Minor - P4
-
Affects Version/s: None
-
Component/s: Encryption
It seems that when pymongo tries to spawn mongocryptd and the spawn fails, the driver surfaces the reason why the spawn failed ("couldn't find the file") but it does not say which file it was looking for (in this case presumably mongocryptd).
Since mongocryptd spawning is not explicitly requested/managed by the user, users have no idea what the driver was looking for that it couldn't find, and hence don't know what they need to fix. The error message is not directly actionable.