I've never seen this particular error before and looking at the code I see there's more information we could expose. I'll make a quick change to do that which will be available in the release next week. Until then I think you're best off with the MySQL logs.