-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection lost on import of database #13
Comments
Not sure how to help debug this. Have you tried pushing the same SQL file into a normal host install of MySQL so we can compare? We don't exactly have a 30 minute import SQL file lying around to test, verify, and debug this with. 😄 |
I wish I could provide more information. I realize it is not much to go on 😦 ... Any way you can help me decipher more about what is going on? I have confirmed the issue happens on both boot2docker and Ubuntu. I have also confirmed that other MySQL containers work. (in this case |
I wonder if this is related to the memory usage issues we're seeing in #3. |
have the same problem, happens during a big mediawiki import, nothing useful in the logs. will try another container now. |
Closing, reopen/post if there is any info that can reproduce or solve the issue. |
I had this problem with a large import and it turned out the host VM RAM wasn't set high enough. Doubled it from 1 GB to 2 GB and the import succeeded. |
This is a general issue with MySQL (see https://stackoverflow.com/questions/10474922/error-2006-hy000-mysql-server-has-gone-away). To fix this with Docker (or at least lessen the likelyhood of it happening) add ' --max_allowed_packet=1073741824' (or to some other appropriately large number) to your startup command |
As @marsh0lion said |
This keeps happening about 30 minutes into import. There are no interesting messages in the logs. Not sure what is going on here.
The text was updated successfully, but these errors were encountered: