Comment 9 for bug 1736565

We're seeing this with Evergreen Version 3.7.3, though I can't help but wonder if it might be a server configuration issue. It sounds a lot like the kind of error I've seen in other systems when not enough resources were allocated on the server or a timeout threshold was set too low.