Re: MySQL crashes while importing a dump

Jocelyn Fournier writes:
> Hi,
>
> How-to-repeat :
>
> Use the sql file uploaded into :
>
> ftp://support.mysql.com/pub/mysql/secret/posts.tar.gz
>
> Then :
>
> mysql taist -uroot -p < posts.sql
> <3:19:23
> Enter password:
> ERROR 2006 at line 42: MySQL server has gone away

[skip]

> mysql> SHOW WARNINGS;
> Empty set (0.00 sec)

Hi!

I have downloaded your test case and it worked like charm for me on
both latest 4.0 and 4.1.

What is your max_allowed_packet. Not just that, send me your global
my.cnf, and may be I might be able to repeat the case.

Did you try both 4.0 and 4.1 ??

SHOW WARNINGS are work in progress..

--
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread13062@lists.mysql.com
To unsubscribe, e-mail

Re: MySQL crashes while importing a dump

Hi,

In fact, after taking a look at mysqld.trace, I noticed :

T@2051 : | error: Packet too large (1497957)

So it seems it was a problem with max_allowed_packet too small (1 MB)
As "packet too large" is detected in mysqld.trace, would it be smarter to
return "ERROR xxxx at line 42: Packet is too large. Try to increase
max_allowed_packet variable" or sometime like that instead of "ERROR 2006 at
line 42: MySQL server has gone away" ? :)

My my.cnf :

[client]
#password = my_password
port = 3306
socket = /var/adm/mysql/mysql.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# The MySQL server
[mysqld]
skip-external-locking
skip-networking
skip-name-resolve
skip-bdb
#myisam-recover=BACKUP,FORCE
#skip-innodb
#delay-key-write-for-all-tables
user = mysql
port = 3306
socket = /var/adm/mysql/mysql.sock
datadir = /home/mysql
set-variable = max_allowed_packet=1M
#set-variable = thread_stack=128K
set-variable = key_buffer=786M
set-variable = table_cache=2400
set-variable = read_buffer_size=1M
set-variable = read_rnd_buffer_size=2M
set-variable = back_log=300
set-variable = thread_cache=200
set-variable = query_cache_size=16M
set-variable = delayed_insert_limit=80
set-variable = max_delayed_threads=100
set-variable = join_buffer=32M
#set-variable = max_write_lock_count=50
set-variable = sort_buffer_size=1M
set-variable = delayed_insert_timeout=150
set-variable = wait_timeout=20
set-variable = max_connections=320
set-variable = myisam_sort_buffer_size=512M
set-variable = thread_concurrency=4
#set-variable = interactive_timeout=3600
# Start logging
#log
innodb_data_home_dir = /home/mysql/Hardwarefr
innodb_data_file_path = ibdata1:500M:autoextend
#set-variable = innodb_mirrored_log_groups=1
innodb_log_group_home_dir = /home/mysql/Hardwarefr/loginno
set-variable = innodb_log_files_in_group=3
set-variable = innodb_log_file_size=50M
set-variable = innodb_log_buffer_size=8M
innodb_flush_log_at_trx_commit=0
innodb_log_arch_dir = /home/mysql/Hardwarefr/loginno
innodb_log_archive=0
set-variable = innodb_buffer_pool_size=256M
set-variable = innodb_additional_mem_pool_size=10M
set-variable = innodb_file_io_threads=4
set-variable = innodb_lock_wait_timeout=50
innodb_flush_method=fdatasync

[mysqldump]
quick
set-variable = max_allowed_packet=16M

[mysql]
no-auto-rehash

[myisamchk]
set-variable = sort_buffer=128M
set-variable = key_buffer=1G

Regards,
Jocelyn


----- Original Message -----
From: "Sinisa Milivojevic"
To:
Cc:
Sent: Thursday, November 21, 2002 2:11 PM
Subject: Re: MySQL crashes while importing a dump


> Jocelyn Fournier writes:
> > Hi,
> >
> > How-to-repeat :
> >
> > Use the sql file uploaded into :
> >
> > ftp://support.mysql.com/pub/mysql/secret/posts.tar.gz
> >
> > Then :
> >
> > mysql taist -uroot -p < posts.sql
> > <3:19:23
> > Enter password:
> > ERROR 2006 at line 42: MySQL server has gone away
>
> [skip]
>
> > mysql> SHOW WARNINGS;
> > Empty set (0.00 sec)
>
> Hi!
>
> I have downloaded your test case and it worked like charm for me on
> both latest 4.0 and 4.1.
>
> What is your max_allowed_packet. Not just that, send me your global
> my.cnf, and may be I might be able to repeat the case.
>
> Did you try both 4.0 and 4.1 ??
>
> SHOW WARNINGS are work in progress..
>
> --
> Regards,
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
> /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
> <___/ www.mysql.com
>
>
>
>


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread13063@lists.mysql.com
To unsubscribe, e-mail

Re: MySQL crashes while importing a dump

On Thursday 21 November 2002 17:17, Jocelyn Fournier wrote:
> Hi,
>
> In fact, after taking a look at mysqld.trace, I noticed :
>
> T@2051 : | error: Packet too large (1497957)
>
> So it seems it was a problem with max_allowed_packet too small (1 MB)
> As "packet too large" is detected in mysqld.trace, would it be smarter to
> return "ERROR xxxx at line 42: Packet is too large. Try to increase
> max_allowed_packet variable" or sometime like that instead of "ERROR 2006 at
> line 42: MySQL server has gone away" ? :)



This is not that easy. The problem is this error is basically identified by
client not server. Server just closes connection in case it gets too lage
packet. So client just knows it have lost connection but there are many
different reasons why this may happen.

This is why we have doccumented too large packed as likely cause in the manual
but we do not report it with error message.


--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Peter Zaitsev
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Moscow, Russia
<___/ www.mysql.com M: +7 095 725 4955


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread13064@lists.mysql.com
To unsubscribe, e-mail

Re: MySQL crashes while importing a dump

Jocelyn Fournier writes:
> Hi,
>
> In fact, after taking a look at mysqld.trace, I noticed :
>
> T@2051 : | error: Packet too large (1497957)
>
> Regards,
> Jocelyn
>

Strange, I have set both client and server max_allowed_packet to 1M
and checked it out, with net_buffer_lenght on both side at 16K and it
all worked fine for me with both 4.0.5 and 4.1.0.


Table was created, all rows inserted, check table showed that all is
OK.

--
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread13066@lists.mysql.com
To unsubscribe, e-mail

MySQL crashes while importing a dump

Hi,

How-to-repeat :

Use the sql file uploaded into :

ftp://support.mysql.com/pub/mysql/secret/posts.tar.gz

Then :

mysql taist -uroot -p < posts.sql
<3:19:23
Enter password:
ERROR 2006 at line 42: MySQL server has gone away

However :

mysql> LOAD DATA INFILE "/home/sly/dump/posts.sql" INTO TABLE phpbb_posts;
Query OK, 21116 rows affected (0.38 sec)
Records: 21116 Deleted: 0 Skipped: 0 Warnings: 274508

don't crash MySQL.

What are all those warnings ??
BTW with MySQL-4.1 :

mysql> SHOW WARNINGS;
Empty set (0.00 sec)

It seems odd with 274508 warnings ;)

Thanks and regards,
Jocelyn


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread13055@lists.mysql.com
To unsubscribe, e-mail