By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,016 Members | 2,265 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,016 IT Pros & Developers. It's quick & easy.

MySQL server has gone away problem

P: n/a
I have MySql server version: 5.0.22-community-nt.
When I try to import data with this command

mysql --default-character-set=utf8 mimi < c:\django\mujserver\mimi.sql

I will get the error

ERROR 2006 (HY000) at line 230: MySQL server has gone away
File c:\django\mujserver\mimi.sql is about 3.5 MB large

Any idea how to solve that problem?
Thank you for help

Regards,
L.

Jun 23 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
>I have MySql server version: 5.0.22-community-nt.
When I try to import data with this command

mysql --default-character-set=utf8 mimi < c:\django\mujserver\mimi.sql

I will get the error

ERROR 2006 (HY000) at line 230: MySQL server has gone away
File c:\django\mujserver\mimi.sql is about 3.5 MB large


'MySQL server has gone away' generally means one of:
(1) the connection timed out due to idle time limit,
(2) mysqld dumped core or otherwise aborted
(3) the server or mysqld was shut down or rebooted,
or network connectivity went away

(1) is unlikely in your situation. (2) is a likely cause and the
best fix I can think of is to upgrade to a newer version of MySQL.

There might possibly be an issue of the MySQL server exceeding
resource limits.

Gordon L. Burditt
Jun 23 '06 #2

P: n/a

Gordon Burditt wrote:
I have MySql server version: 5.0.22-community-nt.
When I try to import data with this command

mysql --default-character-set=utf8 mimi < c:\django\mujserver\mimi.sql

I will get the error

ERROR 2006 (HY000) at line 230: MySQL server has gone away
File c:\django\mujserver\mimi.sql is about 3.5 MB large


'MySQL server has gone away' generally means one of:
(1) the connection timed out due to idle time limit,
(2) mysqld dumped core or otherwise aborted
(3) the server or mysqld was shut down or rebooted,
or network connectivity went away

(1) is unlikely in your situation. (2) is a likely cause and the
best fix I can think of is to upgrade to a newer version of MySQL.

There might possibly be an issue of the MySQL server exceeding
resource limits.


Hello Gordon ,
Thank you for your reply.
The reason was that I wanted to import about 3MB data and I think the
default is about 1MB only.So ,.
I had to add
max_allowed_packet=16M
to my my.ini file,restart the service and now it works .
Regards,
L.

Jun 24 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.