Ref T13347. The gunzip dump.sql.gz | mysql incantation can fail for various reasons. Explicitly document how to identify and resolve two of them:
We have setup guidance around "max_allowed_packet" and even-slightly-modern MySQL seems to raise a good, explicit error message about this, but I believe older MySQL clients raised an opaque error message if a statement in the dumpfile exceeded the packet length ("2006 server has gone away" with no pointer toward packet length).
The InnoDB log issue in T13347 is new to me, and has opaque client errors as of whatever mysql version we have in production (Ubuntu "Ver 14.14 Distrib 5.5.62").
I'll wait until T13347 is actually confirmed as resolved in production to deploy this since I'm not 100% the InnoDB log issue is really the issue, although it seems likely.