try to restart master and see what happen....

----- Original Message -----
From: "Luc Foisy" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "MYSQL-List (E-mail)" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, May 17, 2002 7:25 PM
Subject: RE: mysqld got signal 11;


>
> >Luc Foisy writes:
> >> Can someone give me some clue as to what this means to me?
> >>
> >> mysqld got signal 11;
> >> The manual section 'Debugging a MySQL server' tells you how to use a
> >> stack trace and/or the core file to produce a readable backtrace that
may
> >> help in finding out why mysqld died
> >> Attemping backtrace. You can use the following information to find out
> >> where mysqld died.  If you see no messages after this, something went
> >> terribly wrong
> >> Cannot determine thread, ebp=0xb, backtrace may not be correct
> >> Bogus stack limit or frame pointer, aborting backtrace
> >>
> >> Number of processes running now: 0
> >>
> >>
> >> Luc Foisy
> >>
>
> >Hi!
> >
> >The above means that MySQL server has crashed for some reason.
> >
> >Can you provide us with more info. Is it our binary , what OS and
> >system software do you use, what does error log contains and all other
> >info that you can compile.
> >
> >You may use mysqlbug program to provide much of the above info.
> >
> >As corrupted tables can still cause crashes, please check your tables
> >with CHECK TABLES command, or if MySQL server is not running, with
> >myisamchk -s and repair all tables that are not OK.
>
> ------------------------
> ************************
> (note: I have editied some hostnames, don't need to advertise)
> Did some looking around and was very surprised. The signal 11 above
occured
> on a slave server ( over LAN ), here is a little more of the err output
>
> 020513  9:06:13  Error reading packet from server: Could not find first
log
> (read_errno 0,server_errno=65535)
> 020513  9:07:13  Slave: Failed reading log event, reconnecting to retry,
log
> 'QBSLXDB1-bin.040
> ' position 110194576
> 020513  9:07:13  Slave: reconnected to master
> '[EMAIL PROTECTED]:3306',replication resumed in log 'QBSLXDB1-bin.040
> ' at position 110194576
> 020513  9:07:13  Error reading packet from server: Could not find first
log
> (read_errno 0,server_errno=65535)
> 020513  9:07:15  Slave thread exiting, replication stopped in log
> 'QBSLXDB1-bin.040
> ' at position 110194576
> 020513  9:07:15  Slave: connected to master '[EMAIL PROTECTED]:3306',
> replication started in log 'QBSLXDB1-bin.040' at position 110194576
> 020514  5:55:00  Slave thread exiting, replication stopped in log
> 'QBSLXDB1-bin.041' at position 18927577
> 020514  5:55:00  Slave: connected to master '[EMAIL PROTECTED]:3306',
> replication started in log 'QBSLXDB1-bin.041' at position 18927577
> 020515  5:55:00  Slave thread exiting, replication stopped in log
> 'QBSLXDB1-bin.041' at position 51129469
> 020515  5:55:00  Slave: connected to master '[EMAIL PROTECTED]:3306',
> replication started in log 'QBSLXDB1-bin.041' at position 51129469
> 020516  5:55:00  Slave thread exiting, replication stopped in log
> 'QBSLXDB1-bin.041' at position 73667044
> 020516  5:55:00  Slave: connected to master '[EMAIL PROTECTED]:3306',
> replication started in log 'QBSLXDB1-bin.041' at position 73667044
> mysqld got signal 11;
> The manual section 'Debugging a MySQL server' tells you how to use a
> stack trace and/or the core file to produce a readable backtrace that may
> help in finding out why mysqld died
> Attemping backtrace. You can use the following information to find out
> where mysqld died.  If you see no messages after this, something went
> terribly wrong
> Cannot determine thread, ebp=0xb, backtrace may not be correct
> Bogus stack limit or frame pointer, aborting backtrace
>
> Number of processes running now: 0
> 020516 14:52:47  mysqld restarted
> /usr/sbin/mysqld: ready for connections
>
> ------------------
> So after seeing this, we decided to check our other slave server (
> replicating the same master, over WAN )
> It too got a signal 11, here is output from err log
>
> 020516 14:55:10  Error reading packet from server: Lost connection to
MySQL
> server during query (read_errno 0,server_errno=2013)
> 020516 14:55:10  Slave: Failed reading log event, reconnecting to retry,
log
> 'QBSLXDB1-bin.041' position 89957769
> 020516 14:55:11  Slave: reconnected to master
> 'repslave2@<address>:3306',replication resumed in log 'QBSLXDB1-bin.041'
at
> position 89957769
> 020516 15:01:14  Error reading packet from server: Lost connection to
MySQL
> server during query (read_errno 0,server_errno=2013)
> 020516 15:01:14  Slave: Failed reading log event, reconnecting to retry,
log
> 'QBSLXDB1-bin.041' position 90472635
> 020516 15:01:14  Slave: reconnected to master
> 'repslave2@<address>:3306',replication resumed in log 'QBSLXDB1-bin.041'
at
> position 90472635
> 020516 15:23:43  Error reading packet from server: Lost connection to
MySQL
> server during query (read_errno 0,server_errno=2013)
> 020516 15:23:43  Slave: Failed reading log event, reconnecting to retry,
log
> 'QBSLXDB1-bin.041' position 91888510
> 020516 15:23:43  Slave: reconnected to master
> 'repslave2@<address>:3306',replication resumed in log 'QBSLXDB1-bin.041'
at
> position 91888510
> 020516 15:26:53  Error reading packet from server: Lost connection to
MySQL
> server during query (read_errno 0,server_errno=2013)
> 020516 15:26:53  Slave: Failed reading log event, reconnecting to retry,
log
> 'QBSLXDB1-bin.041' position 92103271
> 020516 15:26:53  Slave: reconnected to master
> 'repslave2@<address>:3306',replication resumed in log 'QBSLXDB1-bin.041'
at
> position 92103271
> 020516 15:38:24  Error reading packet from server: Lost connection to
MySQL
> server during query (read_errno 0,server_errno=2013)
> 020516 15:38:24  Slave: Failed reading log event, reconnecting to retry,
log
> 'QBSLXDB1-bin.041' position 93303069
> 020516 15:38:25  Slave: reconnected to master
> 'repslave2@<address>:3306',replication resumed in log 'QBSLXDB1-bin.041'
at
> position 93303069
> ERROR: 1064  You have an error in your SQL syntax near 'bslive' at line 1
> 020516 16:05:30  mysqld got signal 11;
> The manual section 'Debugging a MySQL server' tells you how to use a
> stack trace and/or the core file to produce a readable backtrace that may
> help in finding out why mysqld died
> Attemping backtrace. You can use the following information to find out
> where mysqld died.  If you see no messages after this, something went
> terribly wrong
> Bogus stack limit or frame pointer, aborting backtrace
>
> Number of processes running now: 0
> 020516 16:05:31  mysqld restarted
> /usr/sbin/mysqld: ready for connections
>
> ---------------------
>
> As you can see the troubles occured about the same time ( hard to tell
since
> one of them did not have a timestamp ) but they could have been at
entirely
> different positions. The logs on the master didn't indicate there was a
> problem
>
>
> Here is some server stats
>
> *****Slave Server 1******
> >Release:       mysql-3.23.32 (Official MySQL RPM)
>
> >Environment:
>         <machine, os, target, libraries (multiple lines)>
> System: Linux QBSCOM200.<hostname> 2.2.16-22 #1 Tue Aug 22 16:49:06 EDT
2000
> i686 unknown
> Architecture: i686
>
> Some paths:  /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc
> /usr/bin/cc
> GCC: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
> gcc version 2.96 20000731 (Red Hat Linux 7.0)
> Compilation info: CC='egcs'  CFLAGS='-O6 -fomit-frame-pointer -mpentium'
> CXX='egcs'  CXXFLAGS='-O6 -fomit-frame-pointer
> -felide-constructor\
> s -fno-exceptions -fno-rtti -mpentium'  LDFLAGS=''
> LIBC:
> lrwxrwxrwx    1 root     root           14 Sep  3  2001 /lib/libc.so.6 ->
> libc-2.1.92.so
> -rwxr-xr-x    1 root     root      4776568 Aug 30  2000
/lib/libc-2.1.92.so
> -rw-r--r--    1 root     root     22607104 Aug 30  2000 /usr/lib/libc.a
> -rw-r--r--    1 root     root          178 Aug 30  2000 /usr/lib/libc.so
> Configure command: ./configure  --disable-shared
> --with-mysqld-ldflags=-all-static --with-client-ldflags=-all-static
> --enable-assembler --with-mysqld-user=my\
> sql --with-unix-socket-path=/var/lib/mysql/mysql.sock --prefix=/
> --with-extra-charsets=complex --exec-prefix=/usr --libexecdir=/usr/sbin
> --sysconfdir=/etc --\
> datadir=/usr/share --localstatedir=/var/lib/mysql --infodir=/usr/info
> --includedir=/usr/include --mandir=/usr/man --without-berkeley-db
> '--with-comment=Offic\
> ial MySQL RPM'
>
>
> *****Slave Server 2******
> >Release:       mysql-3.23.32 (Official MySQL RPM)
>
> >Environment:
>         <machine, os, target, libraries (multiple lines)>
> System: Linux TMCLX222.<hostname> 2.2.16-22 #1 Tue Aug 22 16:49:06 EDT
2000
> i686 unknown
> Architecture: i686
>
> Some paths:  /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc
> /usr/bin/cc
> GCC: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
> gcc version 2.96 20000731 (Red Hat Linux 7.0)
> Compilation info: CC='egcs'  CFLAGS='-O6 -fomit-frame-pointer -mpentium'
> CXX='egcs'  CXXFLAGS='-O6 -fomit-frame-pointer
> -felide-constructor\
> s -fno-exceptions -fno-rtti -mpentium'  LDFLAGS=''
> LIBC:
> lrwxrwxrwx    1 root     root           14 Aug 21  2001 /lib/libc.so.6 ->
> libc-2.1.92.so
> -rwxr-xr-x    1 root     root      4776568 Aug 30  2000
/lib/libc-2.1.92.so
> -rw-r--r--    1 root     root     22607104 Aug 30  2000 /usr/lib/libc.a
> -rw-r--r--    1 root     root          178 Aug 30  2000 /usr/lib/libc.so
> Configure command: ./configure  --disable-shared
> --with-mysqld-ldflags=-all-static --with-client-ldflags=-all-static
> --enable-assembler --with-mysqld-user=my\
> sql --with-unix-socket-path=/var/lib/mysql/mysql.sock --prefix=/
> --with-extra-charsets=complex --exec-prefix=/usr --libexecdir=/usr/sbin
> --sysconfdir=/etc --\
> datadir=/usr/share --localstatedir=/var/lib/mysql --infodir=/usr/info
> --includedir=/usr/include --mandir=/usr/man --without-berkeley-db
> '--with-comment=Offic\
> ial MySQL RPM'
>
>
> *****Master Server******
> >Release:       mysql-3.23.36 (Official MySQL RPM)
>
> >Environment:
>         <machine, os, target, libraries (multiple lines)>
> System: Linux QBSLXDB1.<hostname> 2.2.16-22 #1 Tue Aug 22 16:49:06 EDT
2000
> i686 unknown
> Architecture: i686
>
> Some paths:  /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc
> /usr/bin/cc
> GCC: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
> gcc version 2.96 20000731 (Red Hat Linux 7.0)
> Compilation info: CC='egcs'  CFLAGS='-O6 -fomit-frame-pointer -mpentium'
> CXX='egcs'  CXXFLAGS='-O6 -fomit-frame-pointer
> -felide-constru\
> ctors -fno-exceptions -fno-rtti -mpentium'  LDFLAGS=''
> LIBC:
> lrwxrwxrwx    1 root     root           14 Jun  6  2001 /lib/libc.so.6 ->
> libc-2.1.92.so
> -rwxr-xr-x    1 root     root      4776568 Aug 30  2000
/lib/libc-2.1.92.so
> -rw-r--r--    1 root     root     22607104 Aug 30  2000 /usr/lib/libc.a
> -rw-r--r--    1 root     root          178 Aug 30  2000 /usr/lib/libc.so
> Configure command: ./configure  --disable-shared
> --with-mysqld-ldflags=-all-static --with-client-ldflags=-all-static
> --enable-assembler --with-mysqld-use\
> r=mysql --with-unix-socket-path=/var/lib/mysql/mysql.sock --prefix=/
> --with-extra-charsets=complex --exec-prefix=/usr --libexecdir=/usr/sbin
> --sysconfdir\
> =/etc --datadir=/usr/share --localstatedir=/var/lib/mysql
> --infodir=/usr/info --includedir=/usr/include --mandir=/usr/man
> --without-berkeley-db --without\
> -innobase '--with-comment=Official MySQL RPM'
>
> --------------------------------------------
>
> A post from the MySQL list
> MEMORY PROBLEM ... a pointers is "gone a way" ...
> The signal is SIGSEV and this mean in fact: Invalid memory
> reference.
>
> If this is a memory problem, how did it hit two servers ( several
kilometers
> apart ) at the same time?
>
> ---------------------------------------------------------------------
> 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
>
>


---------------------------------------------------------------------
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

Reply via email to