Re: InnoDB bug?
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm (http://www.ezmlm.org) From: gbu [EMAIL PROTECTED] I'm experiencing very strange innodb behavior. What version of mysqld? - 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
Re: InnoDB bug?
I'm experiencing very strange innodb behavior. What version of mysqld? About test system. FreeBSD 4.2, MySQL 3.23.49, my.cnf innodb settings: === # Uncomment the following if you are using Innobase tables innodb_data_file_path = ibdata1:2M innodb_data_home_dir = /db/mysql/ innodb_log_group_home_dir = /db/mysql/ innodb_log_arch_dir = /db/mysql/ set-variable = innodb_mirrored_log_groups=1 set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=128M set-variable = innodb_log_buffer_size=64M innodb_flush_log_at_trx_commit=1 innodb_log_archive=0 set-variable = innodb_buffer_pool_size=128M set-variable = innodb_additional_mem_pool_size=16M set-variable = innodb_file_io_threads=4 - 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
Re: innodb bug
Heikki,
Thanks for the patch. As I'm going on vacation tomorrow, I'll give it a
try next week and let you know if I find anything.
--shak
Heikki Tuuri wrote:
Hi!
It turned out that the bug indeed was connected with a 32-bit signed integer
wrap-over if the buffer pool on a 32-bit computer is bigger than 2 GB.
The following patch may fix the problem, but better test first if there are
also other similar wrap-overs which I did not notice.
Best regards,
Heikki
Innobase Oy
--- 1.4/innobase/include/buf0buf.ic Tue Dec 4 16:14:52 2001
+++ 1.5/innobase/include/buf0buf.ic Wed Jun 26 21:42:32 2002
@@ -209,7 +209,7 @@
ut_ad((ulint)ptr = (ulint)frame_zero);
- block = buf_pool_get_nth_block(buf_pool, (ptr - frame_zero)
+ block = buf_pool_get_nth_block(buf_pool, ((ulint)(ptr - frame_zero))
UNIV_PAGE_SIZE_SHIFT);
ut_a(block = buf_pool-blocks);
ut_a(block buf_pool-blocks + buf_pool-max_size);
@@ -236,7 +236,7 @@
ut_ad((ulint)ptr = (ulint)frame_zero);
- block = buf_pool_get_nth_block(buf_pool, (ptr - frame_zero)
+ block = buf_pool_get_nth_block(buf_pool, ((ulint)(ptr - frame_zero))
UNIV_PAGE_SIZE_SHIFT);
ut_a(block = buf_pool-blocks);
ut_a(block buf_pool-blocks + buf_pool-max_size);
- Original Message -
From: Heikki Tuuri [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, June 26, 2002 4:42 PM
Subject: Re: innodb bug
Shakeel,
this may be something with 32-bit unsigned integer / signed integer
arithmetic. I assume mysqld runs in the 32-bit mode?
Are you able to compile mysqld yourself? You could add the following to
line
214 of mysql/innobase/include/buf0buf.ic
...
if (block buf_pool-blocks) {
printf(Values %lu, %lu, %lu, %lu\n, (ulint)(ptr - frame_zero),
(ulint)((ptr - frame_zero) UNIV_PAGE_SIZE_SHIFT),
(ulint)block, (ulint)(buf_pool-blocks),
(ulint)ptr, (ulint)frame_zero);
}
...
Regards,
Heikki
Innobase Oy
- Original Message -
From: Shakeel Sorathia [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Wednesday, June 26, 2002 1:19 AM
Subject: innodb bug
I've been having a problem with innodb lately. We just upgraded one of
our machine to have 4 GB of ram in it. However, whenever I make the
innodb_buffer_pool_size greater then 2048M It crashes with the
following in the error log. It's 3.23.51 running on a Solaris 8
Ultrasparc II machine with 4 GB ram. Is the limit 2gb of ram, or is
there something that I'm doing wrong? Thanks for the help!
--shak
020625 12:57:14 mysqld started
InnoDB: Assertion failure in thread 1 in file ../include/buf0buf.ic line
214
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to [EMAIL PROTECTED]
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=8388600
record_buffer=131072
sort_buffer=1048568
max_used_connections=0
max_connections=1024
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections =
1187831
K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation
020625 12:57:54 mysqld ended
--
Shakeel Sorathia
Systems Administrator
(213) 739-5348
-
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
-
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
--
Shakeel Sorathia
Systems Administrator
(213) 739-5348
-
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
RE: innodb bug
Hi, I'm sort of glad we're not the only one having this problem. Yesterday we had kind of the same error message on an Solaris 8 machine with 512Mb of ram. Our buffer_pool_size was set to 250Mb, because the other 250Mb is used by the orion-web-server. Today I will perform crash-tests on another machine and try to find out the problem. Fyi, our error log: = /opt/nusphere/mysql-max-3.23.49-sun-solaris2.8-sparc/bin/mysqld: ready for connections mysqld got signal 10; 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=8388600 record_buffer=131072 sort_buffer=2097144 max_used_connections=16 max_connections=100 threads_connected=3 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K bytes of memory Hope that's ok, if not, decrease some variables in the equation 020625 15:39:58 mysqld restarted 020625 15:40:34 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 272046313 InnoDB: Fatal error: cannot allocate 2310548 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 334012166 bytes. Operating system errno: 11 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. 020625 15:40:37 mysqld ended -Original Message- From: Shakeel Sorathia [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 25, 2002 21:01 To: [EMAIL PROTECTED] Subject: innodb bug I've been having a problem with innodb lately. We just upgraded one of our machine to have 4 GB of ram in it. However, whenever I make the innodb_buffer_pool_size greater then 2048M It crashes with the following in the error log. It's 3.23.51 running on a Solaris 8 Ultrasparc II machine with 4 GB ram. Is the limit 2gb of ram, or is there something that I'm doing wrong? Thanks for the help! --shak 020625 12:57:14 mysqld started InnoDB: Assertion failure in thread 1 in file ../include/buf0buf.ic line 214 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] 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=8388600 record_buffer=131072 sort_buffer=1048568 max_used_connections=0 max_connections=1024 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 1187831 K bytes of memory Hope that's ok, if not, decrease some variables in the equation 020625 12:57:54 mysqld ended -- Shakeel Sorathia Systems Administrator (213) 739-5348 - 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 - 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
Re: innodb bug
Ah, that makes sense. So it potentially could be the simple matter of telling the compiler that the type is unsigned. --shak Chuck Simmons wrote: Bert -- Your problem is not the same as Shakeel's. For you, the database is saying that it couldn't allocate memory. For Shakeel, it is saying that an assert failed. At about line 213, there is a right shift (X Y) that is occuring. The behavior of a right shift is different depending on whether the value being shifted is signed or unsigned. The value is supposed to be unsigned, but the programmers forgot to tell the compiler. This effectively means that mysql cannot allocate more than 2GB of ram. block = buf_pool_get_nth_block(buf_pool, (ptr - frame_zero) UNIV_PAGE_SIZE_SHIFT); ut_a(block = buf_pool-blocks); Chuck Bert VdB wrote: Hi, I'm sort of glad we're not the only one having this problem. Yesterday we had kind of the same error message on an Solaris 8 machine with 512Mb of ram. Our buffer_pool_size was set to 250Mb, because the other 250Mb is used by the orion-web-server. Today I will perform crash-tests on another machine and try to find out the problem. Fyi, our error log: = /opt/nusphere/mysql-max-3.23.49-sun-solaris2.8-sparc/bin/mysqld: ready for connections mysqld got signal 10; 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=8388600 record_buffer=131072 sort_buffer=2097144 max_used_connections=16 max_connections=100 threads_connected=3 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K bytes of memory Hope that's ok, if not, decrease some variables in the equation 020625 15:39:58 mysqld restarted 020625 15:40:34 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 272046313 InnoDB: Fatal error: cannot allocate 2310548 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 334012166 bytes. Operating system errno: 11 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. 020625 15:40:37 mysqld ended -Original Message- From: Shakeel Sorathia [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 25, 2002 21:01 To: [EMAIL PROTECTED] Subject: innodb bug I've been having a problem with innodb lately. We just upgraded one of our machine to have 4 GB of ram in it. However, whenever I make the innodb_buffer_pool_size greater then 2048M It crashes with the following in the error log. It's 3.23.51 running on a Solaris 8 Ultrasparc II machine with 4 GB ram. Is the limit 2gb of ram, or is there something that I'm doing wrong? Thanks for the help! --shak 020625 12:57:14 mysqld started InnoDB: Assertion failure in thread 1 in file ../include/buf0buf.ic line 214 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] 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=8388600 record_buffer=131072 sort_buffer=1048568 max_used_connections=0 max_connections=1024 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 1187831 K bytes of memory Hope that's ok, if not, decrease some variables in the equation 020625 12:57:54 mysqld ended - 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
Re: innodb bug
Hi!
It turned out that the bug indeed was connected with a 32-bit signed integer
wrap-over if the buffer pool on a 32-bit computer is bigger than 2 GB.
The following patch may fix the problem, but better test first if there are
also other similar wrap-overs which I did not notice.
Best regards,
Heikki
Innobase Oy
--- 1.4/innobase/include/buf0buf.ic Tue Dec 4 16:14:52 2001
+++ 1.5/innobase/include/buf0buf.ic Wed Jun 26 21:42:32 2002
@@ -209,7 +209,7 @@
ut_ad((ulint)ptr = (ulint)frame_zero);
- block = buf_pool_get_nth_block(buf_pool, (ptr - frame_zero)
+ block = buf_pool_get_nth_block(buf_pool, ((ulint)(ptr - frame_zero))
UNIV_PAGE_SIZE_SHIFT);
ut_a(block = buf_pool-blocks);
ut_a(block buf_pool-blocks + buf_pool-max_size);
@@ -236,7 +236,7 @@
ut_ad((ulint)ptr = (ulint)frame_zero);
- block = buf_pool_get_nth_block(buf_pool, (ptr - frame_zero)
+ block = buf_pool_get_nth_block(buf_pool, ((ulint)(ptr - frame_zero))
UNIV_PAGE_SIZE_SHIFT);
ut_a(block = buf_pool-blocks);
ut_a(block buf_pool-blocks + buf_pool-max_size);
- Original Message -
From: Heikki Tuuri [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, June 26, 2002 4:42 PM
Subject: Re: innodb bug
Shakeel,
this may be something with 32-bit unsigned integer / signed integer
arithmetic. I assume mysqld runs in the 32-bit mode?
Are you able to compile mysqld yourself? You could add the following to
line
214 of mysql/innobase/include/buf0buf.ic
...
if (block buf_pool-blocks) {
printf(Values %lu, %lu, %lu, %lu\n, (ulint)(ptr - frame_zero),
(ulint)((ptr - frame_zero) UNIV_PAGE_SIZE_SHIFT),
(ulint)block, (ulint)(buf_pool-blocks),
(ulint)ptr, (ulint)frame_zero);
}
...
Regards,
Heikki
Innobase Oy
- Original Message -
From: Shakeel Sorathia [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Wednesday, June 26, 2002 1:19 AM
Subject: innodb bug
I've been having a problem with innodb lately. We just upgraded one of
our machine to have 4 GB of ram in it. However, whenever I make the
innodb_buffer_pool_size greater then 2048M It crashes with the
following in the error log. It's 3.23.51 running on a Solaris 8
Ultrasparc II machine with 4 GB ram. Is the limit 2gb of ram, or is
there something that I'm doing wrong? Thanks for the help!
--shak
020625 12:57:14 mysqld started
InnoDB: Assertion failure in thread 1 in file ../include/buf0buf.ic line
214
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to [EMAIL PROTECTED]
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=8388600
record_buffer=131072
sort_buffer=1048568
max_used_connections=0
max_connections=1024
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections =
1187831
K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation
020625 12:57:54 mysqld ended
--
Shakeel Sorathia
Systems Administrator
(213) 739-5348
-
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
-
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
Re: innodb bug
Bert -- Your problem is not the same as Shakeel's. For you, the database is saying that it couldn't allocate memory. For Shakeel, it is saying that an assert failed. At about line 213, there is a right shift (X Y) that is occuring. The behavior of a right shift is different depending on whether the value being shifted is signed or unsigned. The value is supposed to be unsigned, but the programmers forgot to tell the compiler. This effectively means that mysql cannot allocate more than 2GB of ram. block = buf_pool_get_nth_block(buf_pool, (ptr - frame_zero) UNIV_PAGE_SIZE_SHIFT); ut_a(block = buf_pool-blocks); Chuck Bert VdB wrote: Hi, I'm sort of glad we're not the only one having this problem. Yesterday we had kind of the same error message on an Solaris 8 machine with 512Mb of ram. Our buffer_pool_size was set to 250Mb, because the other 250Mb is used by the orion-web-server. Today I will perform crash-tests on another machine and try to find out the problem. Fyi, our error log: = /opt/nusphere/mysql-max-3.23.49-sun-solaris2.8-sparc/bin/mysqld: ready for connections mysqld got signal 10; 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=8388600 record_buffer=131072 sort_buffer=2097144 max_used_connections=16 max_connections=100 threads_connected=3 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K bytes of memory Hope that's ok, if not, decrease some variables in the equation 020625 15:39:58 mysqld restarted 020625 15:40:34 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 272046313 InnoDB: Fatal error: cannot allocate 2310548 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 334012166 bytes. Operating system errno: 11 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. 020625 15:40:37 mysqld ended -Original Message- From: Shakeel Sorathia [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 25, 2002 21:01 To: [EMAIL PROTECTED] Subject: innodb bug I've been having a problem with innodb lately. We just upgraded one of our machine to have 4 GB of ram in it. However, whenever I make the innodb_buffer_pool_size greater then 2048M It crashes with the following in the error log. It's 3.23.51 running on a Solaris 8 Ultrasparc II machine with 4 GB ram. Is the limit 2gb of ram, or is there something that I'm doing wrong? Thanks for the help! --shak 020625 12:57:14 mysqld started InnoDB: Assertion failure in thread 1 in file ../include/buf0buf.ic line 214 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] 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=8388600 record_buffer=131072 sort_buffer=1048568 max_used_connections=0 max_connections=1024 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 1187831 K bytes of memory Hope that's ok, if not, decrease some variables in the equation 020625 12:57:54 mysqld ended - 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
Re: innodb bug
Shakeel,
this may be something with 32-bit unsigned integer / signed integer
arithmetic. I assume mysqld runs in the 32-bit mode?
Are you able to compile mysqld yourself? You could add the following to line
214 of mysql/innobase/include/buf0buf.ic
...
if (block buf_pool-blocks) {
printf(Values %lu, %lu, %lu, %lu\n, (ulint)(ptr - frame_zero),
(ulint)((ptr - frame_zero) UNIV_PAGE_SIZE_SHIFT),
(ulint)block, (ulint)(buf_pool-blocks),
(ulint)ptr, (ulint)frame_zero);
}
...
Regards,
Heikki
Innobase Oy
- Original Message -
From: Shakeel Sorathia [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Wednesday, June 26, 2002 1:19 AM
Subject: innodb bug
I've been having a problem with innodb lately. We just upgraded one of
our machine to have 4 GB of ram in it. However, whenever I make the
innodb_buffer_pool_size greater then 2048M It crashes with the
following in the error log. It's 3.23.51 running on a Solaris 8
Ultrasparc II machine with 4 GB ram. Is the limit 2gb of ram, or is
there something that I'm doing wrong? Thanks for the help!
--shak
020625 12:57:14 mysqld started
InnoDB: Assertion failure in thread 1 in file ../include/buf0buf.ic line
214
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to [EMAIL PROTECTED]
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=8388600
record_buffer=131072
sort_buffer=1048568
max_used_connections=0
max_connections=1024
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 1187831
K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation
020625 12:57:54 mysqld ended
--
Shakeel Sorathia
Systems Administrator
(213) 739-5348
-
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
-
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
