Skip to content
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

Closed
ianks opened this issue Sep 2, 2014 · 8 comments
Closed

Connection lost on import of database #13

ianks opened this issue Sep 2, 2014 · 8 comments

Comments

@ianks
Copy link

ianks commented Sep 2, 2014

This keeps happening about 30 minutes into import. There are no interesting messages in the logs. Not sure what is going on here.

ERROR 2013 (HY000): Lost connection to MySQL server during query
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:    6
Current database: dev_imobitrax
@tianon
Copy link
Member

tianon commented Sep 2, 2014

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. 😄

@ianks
Copy link
Author

ianks commented Sep 2, 2014

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 tutum/mysql)

@tianon
Copy link
Member

tianon commented Oct 8, 2014

I wonder if this is related to the memory usage issues we're seeing in #3.

@jberkel
Copy link

jberkel commented Nov 25, 2014

have the same problem, happens during a big mediawiki import, nothing useful in the logs. will try another container now.

@yosifkit
Copy link
Member

Closing, reopen/post if there is any info that can reproduce or solve the issue.

@jboynton
Copy link

jboynton commented Nov 5, 2015

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.

@marsh0lion
Copy link

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

@timclifford
Copy link

As @marsh0lion said fin start --max_allowed_packet=1073741824 allowed me to import my 250mb db

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants