| edenCC |
04-25-2007 01:52 AM |
how to use 2G+mem/process on i386
Hi, folks;
my operation system is redhat-as4, mysql-4.0.25-0
when I set the default memory usage for mysql to 2G, I get the following error;
Code:
070425 14:08:43 mysqld started
InnoDB: Fatal error: cannot allocate 2147500032 bytes of
InnoDB: memory with malloc! Total allocated memory
InnoDB: by InnoDB 7705576 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=268435456
read_buffer_size=2093056
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3743343 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x84249a0
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=0xbfffec98, stack_bottom=0x383d, thread_stack=131072, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x79636e65 is invalid pointer
thd->thread_id=1684618061
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.
070425 14:08:43 mysqld ended
I've searched around, the direction is to modify the source code for innodb or glibc:
http://www2.usenetarchive.org/Dir51/File910.html
is there any other ways to resolve this issue?
it should be a common use to run mysql on an i386 with 4G+ memory, I think. :scratch: |
