root writes:
> >Description:
>
> When I sent this problem to the list earlier, I hadn't read about mysqlbug, so
>please excuse the
> improper question submission. Here is the repeat;
>
> I am trying to get a new installation of Bugzilla, v 2.12 installed and working.
>I used a binary tarball of 3.23.36
> for the installation. I am also using the Msql-MySQL modules 1.2215. While
>performing a variety of functions with Bugzilla,
> MySQL is crashing with the following output in the 'hostname.err' file:
>
>
> 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...
> Stack range sanity check OK, backtrace follows:
> 0x81402ca
> 0x8077d5f
> 0x80c9858
> 0x80b0aa2
> 0x80b0341
> 0x8087de2
> 0x808ab9c
> 0x808617d
> 0x808569e
> Stack trace successful, trying to get some variables.
> Some pointers may be invalid and cause the dump to abort...
> thd->query at 0x827ba40 = insert into logincookies (userid,cryptpassword,hostname)
>values (1, 'lv8RdtnjowP22', '10.200.70.5')
> thd->thread_id = 2
> Successfully dumped variables, if you ran with --log,
> take a look at the details of what thread 2 did to cause the crash.
> In some cases of really bad corruption, this value may be invalid
> Please use the information above to create a repeatable
> test case for the crash, and send it to [EMAIL PROTECTED]
>
>
> Now, as I got a binary distro, the 'resolve_stack_dump' tool for decoding the stack
>trace wasn't included.
> So, I was hoping that someone on the list would be able to tell me why I am likely
>getting this error.
>
> >How-To-Repeat:
>
> >Fix:
>
>
> >Submitter-Id: <submitter ID>
> >Originator: [EMAIL PROTECTED]
> >Organization:
> V-Stor LLC
> >MySQL support: none
> >Synopsis: MySQL get Sig 11 during query from Bugzilla
> >Severity: critical
> >Priority: high
> >Category: mysql
> >Class: support
> >Release: mysql-3.23.36 (Official MySQL binary)
>
> >Environment:
>
> System: Linux services.v-stor.com 2.2.17 #1 Tue Dec 19 17:13:10 EST 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/egcs-2.91.66/specs
> gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
> Compilation info: CC='gcc' CFLAGS='-O6 -mpentium ' CXX='gcc' CXXFLAGS='-O6
>-mpentium -felide-constructors' LDFLAGS='-static'
> LIBC:
> lrwxrwxrwx 1 root root 13 Dec 19 20:40 /lib/libc.so.6 ->
>libc-2.1.3.so
> -rwxr-xr-x 1 root root 4101324 Feb 29 2000 /lib/libc-2.1.3.so
> -rw-r--r-- 1 root root 20272704 Feb 29 2000 /usr/lib/libc.a
> -rw-r--r-- 1 root root 178 Feb 29 2000 /usr/lib/libc.so
> Configure command: ./configure --prefix=/usr/local/mysql '--with-comment=Official
>MySQL binary' --with-extra-charsets=complex --enable-assembler
>--with-mysqld-ldflags=-all-static --with-client-ldflags=-all-static --disable-shared
>
Hi!
Beside what I wrote in the previous mail, please check with CHECK
TABLE whether logincookies table is OK.
If that is not OK, it is the most probable cause of the crash.
If it is OK, please send us it's CREATE TABLE statement.
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
