Re: MySQL 4.0 crashed; Please help

2004-02-13 Thread Jacob Friis Larsen (Eksperten admin)
[EMAIL PROTECTED] wrote:
Did you perform a stack trace?
No, how do I do that?

/Jacob

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


MySQL 4.0 crashed; Please help

2004-02-13 Thread Jacob Friis Larsen [Eksperten admin]
Can someone help me find out what caused this crash?
My system is a Red Hat 7.3 on a HP Netserver LC2000, dual PIII 800mhz 
with 2.5G ram. 3 disks in raid 5.

The MySQL database is 4.0.17

040212 19:27:36  read_const: Got error 126 when reading table 
./exp4/sql_cache

Number of processes running now: 0
040212 19:28:04  mysqld restarted
InnoDB: Fatal error: cannot allocate 1073758208 bytes of
InnoDB: memory with malloc! Total allocated memory
InnoDB: by InnoDB 24482732 bytes. Operating system errno: 12
InnoDB: Cannot continue operation!
InnoDB: Check if you should increase the swap file or
InnoDB: ulimits of your operating system.
InnoDB: On FreeBSD check you have compiled the OS with
InnoDB: a big enough maximum process size.
InnoDB: We now intentionally generate a seg fault so that
InnoDB: on Linux we get a 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=402653184
read_buffer_size=1044480
max_used_connections=0
max_connections=800
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections 
= 291705 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8450b80
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, fp=0xbfffe718, 
stack_bottom=0x58575655, thread_stack=126976, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x54535251  is invalid pointer
thd->thread_id=1601790316
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
040212 19:28:06  mysqld ended

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]