On Mon, Feb 11, 2002 at 07:29:19PM -0700, Sasha Pachev wrote:
> On Monday 11 February 2002 12:55 pm, Jeremy Zawodny wrote:
> > The slave hit a duplicate key error and died. ?The IO thread appears
> > to still be running, but the SQL thread is not. ?When I try to do a
> > "SLAVE START" on the slave, the command never returns to the "mysql> "
> > prompt.
>
> Jeremy:
>
> First, do SHOW PROCESSLIST.
Here you go:
---snip---
mysql> show processlist \G
*************************** 1. row ***************************
Id: 1
User: system user
Host: none
db: NULL
Command: Connect
Time: 170724
State: Reading master update
Info: NULL
*************************** 2. row ***************************
Id: 1371
User: root
Host: localhost
db: NULL
Command: Query
Time: 102665
State: Waiting for slave thread to start
Info: slave start
*************************** 3. row ***************************
Id: 3433
User: root
Host: localhost
db: NULL
Command: Query
Time: 0
State: NULL
Info: show processlist
3 rows in set (0.00 sec)
---snip---
> Then I have a dilema - on one hand I want to see if SLAVE STOP/SLAVE
> START will get it going, but on the other hand, I want to see the
> core from the time when slave start got stuck, and we cannot do both
> at the same time :-)
Indeed.
> So let's try SLAVE STOP/SLAVE START
Tried that, and it hangs, too, never returning to the "mysql> "
prompt. So I got another processlist:
---snip---
mysql> show processlist \G
*************************** 1. row ***************************
Id: 1
User: system user
Host: none
db: NULL
Command: Connect
Time: 170903
State: Reading master update
Info: NULL
*************************** 2. row ***************************
Id: 1371
User: root
Host: localhost
db: NULL
Command: Query
Time: 102844
State: Waiting for slave thread to start
Info: slave start
*************************** 3. row ***************************
Id: 3433
User: root
Host: localhost
db: NULL
Command: Query
Time: 30
State: Killing slave
Info: slave stop
*************************** 4. row ***************************
Id: 3438
User: root
Host: localhost
db: NULL
Command: Query
Time: 0
State: NULL
Info: show processlist
4 rows in set (0.00 sec)
---snip---
> and if that does not help, kill mysqld with signal 6 ( SIGABRT),
> find the core file in datadir, and FTP the core and the binary to
> ftp://support.mysql.com/pub/mysql/secret
>
> In the mean time, I will check the code to see if I can find a bug.
I can upload the core file. It's from a FreeBSD 4.3 box, BTW. Will
do so shortly as mysqld.core.yahoo-1.
Here's a quick backtrace for the resulting core:
---snip---
root@db3:/home/mysql/data# gdb /home/mysql/libexec/mysqld mysqld.core
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)...
Core was generated by `mysqld'.
Program terminated with signal 6, Abort trap.
#0 0x8260d44 in _thread_sys_poll ()
(gdb) bt
#0 0x8260d44 in _thread_sys_poll ()
#1 0x82601f8 in _thread_kern_sched_state_unlock ()
#2 0x825fba6 in _thread_kern_scheduler ()
#3 0x0 in ?? ()
(gdb)
---snip---
Somehow that doesn't look very interesting to me. :-(
> Your help is very much appreciated.
Ditto. :-)
Jeremy
--
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936
MySQL 3.23.47-max: up 5 days, processed 188,565,209 queries (402/sec. avg)
---------------------------------------------------------------------
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 <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
