On Tuesday 24 April 2001 04:29, [EMAIL PROTECTED] wrote:
> >Description:
> We have a production server with mysql as db server. Currently we
> are using 1 server for only processing a mysql queries and ther is
> 4 mysql servers running on it each using diiferent IP. When I try
> to make 1 common mysql server it just recieving signal 11 after
> some time. It seems it hangs under heavy load(right before hang I
> saw statistics and it told me 170 queries/second).Here what I got
> from logs:
> 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.
> Attempting 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=0xb9fff8b8, backtrace may not be correct.
> Stack range sanity check OK, backtrace follows:
> 0x813744a
> 0x8137ed0
> 0x813465d
> 0x807c2ec
> 0x8080306
> 0x8135846
> 0x815d60a
> New value of ebp failed sanity check, terminating backtrace!
> First it hangs at 12:06:23 and totally hanged 8 times till 12:17:43
> always with the same backtrace. I compiled mysqld without debug
> and with maximum perfomance boost options that I could get from
> manual(I think that is why backtrace cannot determine thread number).
> When working on 4 mysqld servers which are servicing the same databases
> they are working much more stable-1 of them never hanged(it has the
> most databases),2 of them hanged 1 time each, and last one hanged
> 7 times for all the time, having latest a week ago. This one also
> hangs with the same backtrace. It has only 2 databases but one of
> them is accessed viry intensively.
> Maybe this is a bug, maybe it is my incorrect adjustment
> of mysql. However I think this is more right to write here than
> any other place. I can't do full debug on our servers because my
> boss don't like when something doesn't work, but if I can give
> you more information you are welcome.
> BTW, this hangs become to appear when I upgraded from
> 3.23.29a-gamma to 3.23.33, and exists through 3.23.34a,3.23.36
> and 3.23.37.
>
>
>
> >How-To-Repeat:
> Don't know, just wait for midday when there is heaviest load.
> >Fix:
> Maybe downgrade, which I don't like
>
> >Submitter-Id: <submitter ID>
> >Originator: root
> >Organization:
>
> >MySQL support: [none]
> >Synopsis: Signal 11
> >Severity:
> >Priority:
> >Category: mysql
> >Class:
> >Release: mysql-3.23.37 (Source distribution)
>
> >Environment:
>
> System: Linux xeon.tr155m.krystech.ru 2.4.2-4 #9 SMP Mon Mar 5 12:19:58 MSK
2001 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/egcs-2.91.66/specs
> gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
> Compilation info: CC='gcc' CFLAGS='' CXX='c++' CXXFLAGS='' LDFLAGS=''
> LIBC:
> lrwxrwxrwx 1 root root 13 Feb 22 21:52 /lib/libc.so.6 ->
libc-2.1.3.so
> -rwxr-xr-x 1 root root 4101324 Mar 1 2000 /lib/libc-2.1.3.so
> -rw-r--r-- 1 root root 20272704 Mar 1 2000 /usr/lib/libc.a
> -rw-r--r-- 1 root root 178 Mar 1 2000 /usr/lib/libc.so
> Configure command: ./configure --prefix=/opt/local/mysql
--with-charset=cp1251 --with-extra-charsets=koi8_ru --enable-assembler
--enable-large-files --without-debug --with-mysqld-ldflags=-all-static
--with-pthread --without-debug --with-raid --with-gnu-ld
--with-mysqld-user=mysql --with-port=3306
--with-unix-socket-path=/tmp/mysql.sock --with-client-ldflags=-all-static
> Perl: This is perl, version 5.005_03 built for i386-linux
>
>
First, make sure to follow the instructuctions in the manual on symbolic
resolve of the stack trace. Without it, numeric trace is not much help,
especially when you built your own binary and we do not have a symbol table.
Second, building your own binary on Linux is not a good idea when running
with lots of connections, unless you patch your libc according to our
instructions in the Linux notes section of the manual. I would recommend
using our binary - it is properly tuned for handling 1500+ concurrent
connections, and also has the default LinuxThreads mutex behaviour corrected.
Thrid, I did not quite understand what you were saying about running 4 MySQL
servers - are they on the same machine? If yes, do they have a different
datadir? If they share the datadir, this would explain the problem.
--
MySQL Development Team
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sasha Pachev <[EMAIL PROTECTED]>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
/_/ /_/\_, /___/\___\_\___/ Provo, Utah, USA
<___/
---------------------------------------------------------------------
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
