Hi,
MySQL-4.0.3 has just segfault with the following stack trace :
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 against 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=335540224
read_buffer_size=520192
sort_buffer_size=524280
max_used_connections=184
max_connections=320
threads_connected=222
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections =
654073 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 222 concurrent connections.
If you have not changed STACK_SIZE in LinuxThreads and built the binary
yourself, LinuxThreads is quite likely to steal a part of the global heap
for
the thread stack. Please read http://www.mysql.com/doc/L/i/Linux.html
thd=0x59a149b0
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, fp=0xbf59f338, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8095207 _Z15handle_segfaulti + 487
0x8263642 pthread_sighandler + 114
0x829145c strncasecmp + 92
0x809dd09 _Z16dispatch_command19enum_server_commandP3THDPcj + 441
0x809db3d _Z10do_commandP3THD + 109
0x809d418 _Z21handle_one_connectionPv + 920
0x8260dd8 pthread_start_thread + 152
0x8298dba clone + 26
New value of fp=(nil) failed sanity check, terminating stack trace!
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 (nil) is invalid pointer
thd->thread_id=70210
As I'm using NGPT 2.0.1 threads, I'm wondering if this is a MySQL problem or
if NGPT could be involved.
Thanks and regards,
Jocelyn
---------------------------------------------------------------------
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 internals-thread4474@xxxxxxxxxxxxxxx
To unsubscribe, e-mail <internals-unsubscribe@xxxxxxxxxxxxxxx>
|
