My MySQL server was shut down for something. and echopet crashed the server when it could not connect: http://pastebin.com/DikbF9h8

All heavy saving-related tasks in EchoPet v3 are executed asynchronously, meaning that this sort of problem won't arise.

I've added the 3.x milestone to this issue, as it would be slightly more complicated to fit this safely and easily into the narrow v2 infrastructure.

(My apologies for not mentioning this earlier).

its k