Bug #32967 InnoDB Crashes sometimes
Submitted: 4 Dec 2007 15:40 Modified: 16 Feb 2008 13:46
Reporter: MuraliDharan V Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S5 (Performance)
Version:5.0.22 maxlog OS:Linux
Assigned to: Assigned Account CPU Architecture:Any
Tags: InnoDB Crash

[4 Dec 2007 15:40] MuraliDharan V
Description:
071019  6:38:37 [Note] /home/local/mysql/libexec/mysqld: ready for connections.
Version: '5.0.22-max-debug-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
071019 13:25:43 [Note] /home/local/mysql/libexec/mysqld: Normal shutdown

071019 13:25:43  InnoDB: Starting shutdown...
071019 13:25:46  InnoDB: Shutdown completed; log sequence number 0 43655
071019 13:25:46 [Note] /home/local/mysql/libexec/mysqld: Shutdown complete

071019 13:25:46  mysqld ended

071019 19:37:20  mysqld started
071019 19:37:20  InnoDB: Started; log sequence number 0 43655
071019 19:37:21 [Note] /home/local/mysql/libexec/mysqld: ready for connections.
Version: '5.0.22-max-debug-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
071022 12:59:11 [Note] /home/local/mysql/libexec/mysqld: Normal shutdown

071022 12:59:11  InnoDB: Starting shutdown...
071022 12:59:13  InnoDB: Shutdown completed; log sequence number 0 43655
071022 12:59:13 [Note] /home/local/mysql/libexec/mysqld: Shutdown complete

071022 12:59:13  mysqld ended

071023 17:09:42  mysqld started
071023 17:09:43  InnoDB: Started; log sequence number 0 43655
071023 17:09:43 [Note] /home/local/mysql/libexec/mysqld: ready for connections.
Version: '5.0.22-max-debug-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
071023 17:17:30 [Note] /home/local/mysql/libexec/mysqld: Normal shutdown

071023 17:17:30  InnoDB: Starting shutdown...
071023 17:17:31  InnoDB: Shutdown completed; log sequence number 0 43655
071023 17:17:31 [Note] /home/local/mysql/libexec/mysqld: Shutdown complete

071023 17:17:31  mysqld ended

How to repeat:
I dont understand this point.
[4 Dec 2007 16:43] Heikki Tuuri
Murali,

I do not see any mysqld crash in the .err log. Since InnoDB's log sequence number does not change, you are probably not using InnoDB at all.

Are you unintentionally shutting down mysqld?

Regards,

Heikki
[4 Dec 2007 17:11] MuraliDharan V
Here is my .err file from Database server

Attachment: Database_Error.err (text/plain), 248.29 KiB.

[14 Jan 2008 18:04] Heikki Tuuri
Murali,

have you configured too much buffer pool:

071026 02:45:29  mysqld started
071026  2:45:29  InnoDB: Error: cannot allocate 2621440000 bytes of
InnoDB: memory with malloc! Total allocated memory
InnoDB: by InnoDB 10001456 bytes. Operating system errno: 12

Maybe you are just running out of memory?

Regards,

Heikki
[16 Jan 2008 6:23] MuraliDharan V
Can u please help me on this?
How can i check my memory space and how to edit it as per the standard memory size without any problem?
[16 Jan 2008 12:14] Heikki Tuuri
Murali,

in your my.cnf file you probably have something like:

innodb_buffer_pool_size=2G

now.

Try:

innodb_buffer_pool_size=1500M

Regards,

Heikki
[16 Jan 2008 13:05] MuraliDharan V
Hi Heikki,

Here is my Inno DB Configuration in my.cnf file,

innodb_buffer_pool_size =  500M #1000M #16M
innodb_additional_mem_pool_size = 200M #400M # 2M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 500M #5M
innodb_log_buffer_size = 250M #8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

#query_cache_size = 300M #268435456
#query_cache_type= 1
query_cache_limit= 1048576

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

Will the settings of InnoDB Buffer Size and other required parameters depends on the Hardware of the server?.

I will give u the details of the hardware in few mins.
[16 Jan 2008 13:22] Heikki Tuuri
Murali,

please make sure mysqld is really reading that my.cnf and not some other file. I do not see how this can happen:

071026 02:45:29  mysqld started
071026  2:45:29  InnoDB: Error: cannot allocate 2,621,440,000 bytes of

if you only have InnoDB buffers configured to <= 500 MB.

You can specify:

./mysqld --defaults-file=<the path to your my.cnf> to make sure it reads the file you mean it to read.

Regards,

Heikki
[16 Jan 2008 13:27] MuraliDharan V
Where i need to specify this ?  

./mysqld --defaults-file=<the path to your my.cnf> to make sure it
reads the file you mean it to read.
[16 Jan 2008 13:40] Heikki Tuuri
Murali,

when you start the mysqld server.

--Heikki
[16 Jan 2008 13:43] MuraliDharan V
Do u mean starting up of mysql

/etc/init.d/mysql start
/etc/init.d/mysql stop
[16 Jan 2008 13:46] Heikki Tuuri
Murali,

please start it manuall with:

./mysqld --defaults-file=...

so that you can be sure what my.cnf file it is reading. Do noty start automatically.

--Heikki
[17 Feb 2008 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".