Replication: Slave using MySQL 4.0.3-beta-max-nt crashes the slave on startup.

Description:
=09Theme: Replication
=09When I use MySQL 4.0.3-beta-max-nt for a slave the MySQL=
slave crashes.
=09Using MySQL 3.23.52-max-nt for the slave avoid crashing=
the slave server.

How-To-Repeat:
My configurations are:

Master:

- running MySQL 3.23.52-max-nt-log

Following MY.INI of the master:
#=
------------------------------------------------------------
#This File was made using the WinMySQLAdmin 1.3 Tool
#16.11.2002 16:42:19

#Uncomment or Add only the keys that you know how works.
#Read the MySQL Manual for instructions

[mysqld]
# master settings
log-bin
server-id=3D1

basedir=3DC:/Programme/MySQL
datadir=3DC:/Programme/mysql/data
language=3DC:/Programme/MySQL/share/german
set-variable=3Dmax_allowed_packet=3D16M

innodb_data_home_dir=3DC:/Programme/mysql/idata
innodb_data_file_path=3Didatafile1:2000M;idatafile2:2000M;
set-variable =3D innodb_mirrored_log_groups=3D1
innodb_log_group_home_dir =3D C:/Programme/mysql/iblogs
set-variable =3D innodb_log_files_in_group=3D3
set-variable =3D innodb_log_file_size=3D30M
set-variable =3D innodb_log_buffer_size=3D8M
innodb_flush_log_at_trx_commit=3D1
innodb_log_arch_dir =3D C:/Programme/mysql/iblogs
innodb_log_archive=3D0

set-variable =3D innodb_buffer_pool_size=3D200M
set-variable =3D innodb_additional_mem_pool_size=3D20M
set-variable =3D innodb_file_io_threads=3D4
set-variable =3D innodb_lock_wait_timeout=3D50

[WinMySQLadmin]
Server=3DC:/Programme/MySQL/bin/mysqld-max-nt.exe
user password
QueryInterval=3D10
#=
------------------------------------------------------------



Slave:

- running MySQL 4.0.3-beta-max-nt

Following MY.INI of the master:
#=
------------------------------------------------------------
#This File was made using the WinMySQLAdmin 1.3 Tool
#16.11.2002 16:42:19

#Uncomment or Add only the keys that you know how works.
#Read the MySQL Manual for instructions

[mysqld]
# Slave settings
master-host=3Ddb-master
master-user=3Drepli
master-password=3Dpwd
master-port=3D3306
server-id=3D3

basedir=3DC:/Programme/MySQL
datadir=3DC:/Programme/mysql/data
language=3DC:/Programme/MySQL/share/german
set-variable=3Dmax_allowed_packet=3D16M

innodb_data_home_dir=3DC:/Programme/mysql/idata
innodb_data_file_path=3Didatafile1:2000M;idatafile2:2000M;
set-variable =3D innodb_mirrored_log_groups=3D1
innodb_log_group_home_dir =3D C:/Programme/mysql/iblogs
set-variable =3D innodb_log_files_in_group=3D3
set-variable =3D innodb_log_file_size=3D30M
set-variable =3D innodb_log_buffer_size=3D8M
innodb_flush_log_at_trx_commit=3D1
innodb_log_arch_dir =3D C:/Programme/mysql/iblogs
innodb_log_archive=3D0

set-variable =3D innodb_buffer_pool_size=3D200M
set-variable =3D innodb_additional_mem_pool_size=3D20M
set-variable =3D innodb_file_io_threads=3D4
set-variable =3D innodb_lock_wait_timeout=3D50

[WinMySQLadmin]
Server=3DC:/Programme/mysql/bin/mysqld-max-nt.exe
user=3Dmysql
password
QueryInterval=3D10


Fix:
No idea!

Synopsis:=09Replication: Slave using MySQL 4.0.3-beta-max-nt=
crashes the slave on startup.
Submitter-Id:=09
Originator:=09Bernd Grell
Organization: CGS Germany
MySQL support: licence
Severity:=09critical
Priority:=09medium
Category:=09mysqld, C,
Class: sw-bug
Release:=094.0.3-beta-max-nt

Exectutable: 4.0.3-beta-max-nt
Environment: Master: Intel Pentium 1 GHz, 512 MB RAM, Slave:=
Intel Pentium 2 GHz, 512 MB RAM
System: Win2000 SP3 on Master and Server
Compiler: using pre-compiled binary of MySQL AB
Architec: i


------------------------------------------------------------ ---------
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-thread12564@lists.mysql.com
To unsubscribe, e-mail

Re: Replication: Slave using MySQL 4.0.3-beta-max-nt crashes the slave on startup.

On Friday 20 September 2002 09:40, bernd.grell@cgs.de wrote:
> Description:
> =09Theme: Replication
> =09When I use MySQL 4.0.3-beta-max-nt for a slave the MySQL sla=
ve
> crashes. Using MySQL 3.23.52-max-nt for the slave avoid crashing the sl=
ave
> server.
>
> How-To-Repeat:
> My configurations are:
>


Dear Bernd,

Unfortunately this information is not enough to fix the bug.=20
Additionally to configuration of Master and Slave we need exact sequence =
of=20
commands to repeat the problem, to be run on the empty master and slave. =
=20




--=20
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / 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-thread12566@lists.mysql.com
To unsubscribe, e-mail

Re: Replication: Slave using MySQL 4.0.3-beta-max-nt crashes the slave on startup.

On Friday 20 September 2002 17:17, bernd.grell@cgs.de wrote:
> How-To-Repeat:
>
> My configurations are:
> >Dear Bernd,
> >
> >Unfortunately this information is not enough to fix the bug.
> >Additionally to configuration of Master and Slave we need exact sequen=
ce
> > of commands to repeat the problem, to be run on the empty master and
> > slave.
>
> Dear Peter,
>
> What I did were very simple:
>
> Download the files
> =09http://www.mysql.de/Downloads/MySQL-4.0/mysql-4.0.3-beta- win.zip
> =09and
> =09http://www.mysql.de/Downloads/MySQL-Max-3.23/mysql-max-3. 23.52-win.z=
ip

>
> So, I will help you a little. I have downloaded the source, compile a d=
ebug
> version of 'mysqld' with Visual C++ 6.0 and start it with the option
> '--standalone'. 'mysqld' crashes in module '\mysql\mysys\thr_alarm.c' =
in
> function:
>
> void thr_end_alarm(thr_alarm_t *alrm_ptr) // *alrm_ptr: this pointe=
r is
> NULL {
> thr_alarm_t alrm=3D *alrm_ptr; // now, alrm is also NULL
> if (alrm->crono) =09 // now you get an access violation
> {
> KillTimer(NULL, alrm->crono);
> alrm->crono =3D 0;
> }
> }
>
> Both computers use W2000 Professional and SP3. But I think, this is no=
t
> the point.
>
> May I help you with this information.


Thank you for you bug report. It is likely we have already fixed this pro=
blem in 4.0.4 which should be out in a week.
You can wait for this version or you can check if current BitKeeper tree =
works for you.

--=20
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / 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-thread12569@lists.mysql.com
To unsubscribe, e-mail