Re: getting frequent signal 11 after upgrade from 3.23.28 to 3.23.34
I'm not sure if anyone cares but... here's my final post on this topic. I believe my signal 11 problem was due to me installing the 3.23.34 rpms from mysql.com on top of my Redhat 7.0 system. I had heard that the RPMs on mysql.com are Redhat 6.2 based and thus may be expecting different dynamic libraries (libc?). Normally, rpms will complain about missing dependencies, but it's possible the ones on mysql.com were not made to check such things. I'm not really sure this is the problem, but it's a good enough guess that I'm willing to let it go now. I've installed the 3.23.32 rpms for 7.0 from redhat.com and it went smoothly. So far no signal 11's. Interestingly, redhat has got a different (and I think more standard) mysqld start script (for /etc/init.d/rc.d/mysqld - note the name change from ".../rc.d/mysql"). I had to edit it though as it had a --default option for safe_mysqld that mysqld had never heard of (odd). From now on, I'll be restricting myself to redhat.com's 7.0 Mysql rpms. I can live with being a few releases behind (sounds like the mysql people recommend not installing new release right away anyway). over and out, -bill - 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
Re: getting frequent signal 11 after upgrade from 3.23.28 to 3.23.34
On Mon, 12 Mar 2001 10:02:51 -0500 [EMAIL PROTECTED] wrote: I just upgraded from Mysql 3.23.28 to 3.23.34 and I'm now seeing mysql errors from my scripts that say "mysqld has gone away". The /var/lib/mysql/host.err log says this repeatedly: same here. Compiling with Innobase, and doing "mysqladmin variables" command always leads to mysql crashing restarting. % configure --with-charsets-extra=complex --with-charsets=ujis \ --with-innobase % make % make install % cat /etc/my.cnf [mysqld] innobase_data_file_path = ibdata1:25M;ibdata2:37M;ibdata3:100M;ibdata4:300M % mysqladmin version mysqladmin Ver 8.18 Distrib 3.23.34a, for unknown-freebsdelf4.1 on i386 Copyright (C) 2000 MySQL AB MySQL Finland AB TCX DataKonsult AB This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license Server version 3.23.34a Protocol version10 Connection Localhost via UNIX socket UNIX socket /tmp/mysql.sock Uptime: 8 min 7 sec Threads: 1 Questions: 27 Slow queries: 0 Opens: 12 Flush tables: 1 Open table s: 6 Queries per second avg: 0.055 % mysqladmin variables mysqladmin: unable to show variables; error: 'Lost connection to MySQL server duri ng query' 010314 14:41:00 mysqld restarted % cd /usr/local/var % tail -18 **myhost**.err 010314 14:32:35 mysqld restarted Innobase: Database was not shut down normally. Innobase: Starting recovery from log files... Innobase: Starting log scan based on checkpoint at Innobase: log sequence number 0 33386 Innobase: Started /usr/local/libexec/mysqld: ready for connections 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. 010314 14:41:00 mysqld restarted Innobase: Database was not shut down normally. Innobase: Starting recovery from log files... Innobase: Starting log scan based on checkpoint at Innobase: log sequence number 0 33713 Innobase: Started /usr/local/libexec/mysqld: ready for connections -- Tatsuhiko Miyagawa Livin' On The EDGE, Co.,Ltd. mailto:[EMAIL PROTECTED] http://www.edge.co.jp/ - 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
Re: Innobase SHOW VARIABLES (Re: getting frequent signal 11 after upgrade from 3.23.28 to 3.23.34)
On Tue, Mar 13, 2001 at 09:48:22PM -0800, Jeremy D. Zawodny wrote: On Wed, Mar 14, 2001 at 02:42:30PM +0900, Tatsuhiko Miyagawa wrote: On Mon, 12 Mar 2001 10:02:51 -0500 [EMAIL PROTECTED] wrote: I just upgraded from Mysql 3.23.28 to 3.23.34 and I'm now seeing mysql errors from my scripts that say "mysqld has gone away". The /var/lib/mysql/host.err log says this repeatedly: same here. Compiling with Innobase, and doing "mysqladmin variables" command always leads to mysql crashing restarting. Similar here. Innobase appears to work well, but when I issue a "SHOW VARIABLES" on the server, it will crash. I can produce a core/backtrace if necessary, but it sounds like this easy to reproduce. Damn. Monty has already patched it. :-) -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 328-7878Fax: (408) 530-5454 Cell: (408) 439-9951 - 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
Re: Innobase SHOW VARIABLES (Re: getting frequent signal 11 after upgrade from 3.23.28 to 3.23.34)
Oops, really :-) On Tue, 13 Mar 2001 22:48:58 -0800 "Jeremy D. Zawodny" [EMAIL PROTECTED] wrote: I can produce a core/backtrace if necessary, but it sounds like this easy to reproduce. Damn. Monty has already patched it. :-) -- Tatsuhiko Miyagawa Livin' On The EDGE, Co.,Ltd. mailto:[EMAIL PROTECTED] http://www.edge.co.jp/ - 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
Re: Innobase SHOW VARIABLES (Re: getting frequent signal 11 after upgrade from 3.23.28 to 3.23.34)
On Wed, Mar 14, 2001 at 03:51:18PM +0900, Tatsuhiko Miyagawa wrote: Oops, really :-) Yes, he posted it in the message with Message-ID: [EMAIL PROTECTED] Jeremy On Tue, 13 Mar 2001 22:48:58 -0800 "Jeremy D. Zawodny" [EMAIL PROTECTED] wrote: I can produce a core/backtrace if necessary, but it sounds like this easy to reproduce. Damn. Monty has already patched it. :-) -- Tatsuhiko Miyagawa Livin' On The EDGE, Co.,Ltd. mailto:[EMAIL PROTECTED] http://www.edge.co.jp/ -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 328-7878Fax: (408) 530-5454 Cell: (408) 439-9951 - 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
getting frequent signal 11 after upgrade from 3.23.28 to 3.23.34
Description: I just upgraded from Mysql 3.23.28 to 3.23.34 and I'm now seeing mysql errors from my scripts that say "mysqld has gone away". The /var/lib/mysql/host.err log says this repeatedly: 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... Bogus stack limit or frame pointer, aborting backtrace. The db is working otherwise and the system seems otherwise unaffected, there are just errors now and again. How-To-Repeat: It's happening intermittently. Fix: none know at this time. Submitter-Id: submitter ID Originator:Bill Marrs Organization: MySQL support: none Synopsis: frequent signal 11 after upgrade from 3.23.28 to 3.23.34 Severity: serious Priority: medium Category: mysql Class: sw-bug Release: mysql-3.23.34 (Official MySQL RPM) Server: /usr/bin/mysqladmin Ver 8.17 Distrib 3.23.34, for pc-linux-gnu on i686 Copyright (C) 2000 MySQL AB MySQL Finland AB TCX DataKonsult AB This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license Server version 3.23.34 Protocol version10 Connection Localhost via UNIX socket UNIX socket /var/lib/mysql/mysql.sock Uptime: 56 min 45 sec Threads: 19 Questions: 51769 Slow queries: 0 Opens: 61 Flush tables: 1 Open tables: 55 Queries per second avg: 15.204 Environment: System: Linux ugtz.com 2.2.17 #6 SMP Wed Dec 6 18:47:48 EST 2000 i686 unknown Architecture: i686 I'm using Redhat Linux 7.0, 2.2.17 kernel. My system is a dual 800Mhz Pentium III, 756MB RAM, with a SCSI disk. 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 2731 (Red Hat Linux 7.0) Compilation info: CC='egcs' CFLAGS='-O6 -fomit-frame-pointer -mpentium' CXX='egcs' CXXFLAGS='-O6 -fomit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti -mpentium' LDFLAGS='' LIBC: lrwxrwxrwx1 root root 11 Dec 8 05:21 /lib/libc.so.6 - libc-2.2.so -rwxr-xr-x1 root root 4733359 Nov 19 09:25 /lib/libc-2.2.so -rw-r--r--1 root root 22806158 Nov 19 09:22 /usr/lib/libc.a -rw-r--r--1 root root 178 Nov 19 09:22 /usr/lib/libc.so Configure command: ./configure --disable-shared --with-mysqld-ldflags=-all-static --with-client-ldflags=-all-static --enable-assembler --with-mysqld-user=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' - 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
Re: getting frequent signal 11 after upgrade from 3.23.28 to 3.23.34
HI!
Please try to make a repeatable test case if possible.
This means a set of commands that would always lead to MySQL crashing.
Regards,
Sinisa
__ _ _ ___ == MySQL AB
/*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic
/*/ /*/ /*/ \*\_ |*| |*||*| mailto:[EMAIL PROTECTED]
/*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaca, Cyprus
/*/ /*/ /*/\*\_/*/ \*\_/*/ |*|
/*/^^^\*\^^^
/*/ \*\Developers Team
-
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
Re: getting frequent signal 11 after upgrade from 3.23.28 to 3.23.34
At 05:14 PM 3/12/2001 +0200, Sinisa Milivojevic wrote: Please try to make a repeatable test case if possible. This means a set of commands that would always lead to MySQL crashing. The problem does seem caused by a sequential set of operations. The script that I've seen cause the problem sometimes crashes with this error and other times does not. I'll keep trying to track it down though... I was hoping that someone out there would have seen something similar... -bill - 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
Re: getting frequent signal 11 after upgrade from 3.23.28 to 3.23.34
The problem does seem caused by a sequential set of operations. The script oops, I'm meant to say "doesn't seem caused" -bill - 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
Re: getting frequent signal 11 after upgrade from 3.23.28 to 3.23.34
FYI, This problem got worse as more users began using the system. I had to revert back to 3.23.28, which did solve the problem. I'm sorry that I didn't come up with a reproducible test case. As near as I could tell it seemed to be intermittent in nature. Things would work, then not work. I had a couple hours where there were zero server crashes, but in the last hour the crashes were continuous so I had to revert. My system is a fairly complicate dynamic website, so it's hard to narrow things down on the live site. I'll try to reproduce it on my test system, but it's hard to simulate the same levels of load (so far, I have no luck reproducing it there). -bill - 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
