That's what I'm thinking as well. The service log is often a better guide to what actually went wrong, and the ConnectionError points to the possibility that the database connection pool is full. Because of the ConnectionError, I think it's possible that the behavior you're seeing is related to this post:
This may be an issue with Central, and we're investigating the issue further. We'll let you know once we have more information (or more questions)!