MySQL server has gone away problem
am 23.06.2006 15:50:08 von python
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.
Re: MySQL server has gone away problem
am 23.06.2006 20:19:43 von gordonb.xxh1h
>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
Re: MySQL server has gone away problem
am 24.06.2006 07:43:29 von python
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.