Description:
        The errors and crashes herein are related to the use of a software
        package called Phorums... version 3.2.11... The query that was crashed
        on here, is made against the phorums3211 database.

        Log errors as follows:

----------

020209 13:52:17  Aborted connection 1107 to db: 'unconnected' user: 'KidsWB' host: 
`talk-backdow.thewb.com' (Got an error writing communication packets)
020209 13:52:29  Aborted connection 4735 to db: 'phorums3211' user: 'phorums' host: 
`talk-backdow.thewb.com' (Got timeout reading communication packets)
020209 13:52:39  Aborted connection 6502 to db: 'phorums3211' user: 'phorums' host: 
`talk-backdow.thewb.com' (Got timeout reading communication packets)
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked agaist is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail

key_buffer_size=402649088
record_buffer=1044480
sort_buffer=1048568
max_used_connections=463
max_connections=600
threads_connected=463
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 1619607 K bytes of 
memory
Hope that's ok, if not, decrease some variables in the equation

You seem to be running 32-bit Linux and have 463 concurrent connections.
If you have not changed STACK_SIZE in LinuxThreads and build the binary
yourself, LinuxThreads is quite likely to steal a part of global heap for
the thread stack. Please read http://www.mysql.com/doc/L/i/Linux.html

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:
0x80bbbd8
0x2aad1552
0x2abe76d9
0x2abe759e
0x81cecb8
0x80e1460
0x80d907d
0x80c2279
0x80c605d
0x80c1689
0x80c0bb6
Stack trace seems successful - bottom reached
Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow 
instructions on how to 
resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8794518 = SELECT p.*, pt.post_text FROM posts p, posts_text pt
   WHERE topic_id = '575'
   AND p.post_id = pt.post_id
   ORDER BY post_id LIMIT 6920, 40
thd->thread_id=6881


Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 6881 did to cause the crash.  In some cases of really
bad corruption, the above values may be invalid

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash

Number of processes running now: 0
020209 13:52:43  mysqld restarted
/usr/local/libexec/mysqld: ready for connections
020209 13:57:54  Aborted connection 22 to db: 'phorums3211' user: 'phorums' host: 
`talk-backdow.thewb.com
' (Got timeout reading communication packets)
020209 13:57:56  Aborted connection 32 to db: 'phorums3211' user: 'phorums' host: 
`talk-backdow.thewb.com
' (Got timeout reading communication packets)

----------

How-To-Repeat:
        Just wait. It seems to happen every couple weeks or so.. like 
        clockwork.
Fix:
        Unknown as of yet.. restarting mysql only just gives us more time
        before it happens again.

Submitter-Id:   .....
Originator:     Steven Deaton
Organization:   Apollo Interactive
MySQL support:  none
Synopsis:       MySQL crashes after specific query.
Severity:       serious
Priority:       medium
Category:       mysql
Class:          sw-bug
Release:        mysql-3.23.39 (yes)

Environment:    VA Linux release 6.2.4 S04.01.01
System:         Linux talk-db.thewb.com 2.4.5-beta4va3.17smp-piii #1 SMP Wed Jun 20 
22:10:48 PDT 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 Jun 22  2001 /lib/libc.so.6 -> libc-2.1.3.so
-rwxr-xr-x    1 root     root      4110037 Apr  2  2001 /lib/libc-2.1.3.so
-rw-r--r--    1 root     root     20366272 Apr  2  2001 /usr/lib/libc.a
-rw-r--r--    1 root     root          178 Apr  2  2001 /usr/lib/libc.so
Configure command: ./configure  --prefix=/usr/local --datadir=/home/mysql 
--enable-assembler --with-mysql-user=mysql 
--with-unix-socket-path=/home/mysql/mysql.sock --with-raid --enable-thread-safe-client 
--with-libwrap --with-comment --with-berkeley-db --sysconfdir=/home/mysql
Perl: This is perl, version 5.005_03 built for i386-linux

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