Bug #36542 fatal Innodb error didn't crash mysql
Submitted: 6 May 2008 17:37 Modified: 7 May 2008 0:29
Reporter: dan radom Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.45 OS:Linux
Assigned to: CPU Architecture:Any

[6 May 2008 17:37] dan radom
MySQL couldn't allocate memory to the buffer pool.  A fatal InnoDB error occurred, but MySQL didn't crash.  The safe_mysqld process then tried to start the database generating an error that it couldn't bind to the port.

080506  3:37:14  InnoDB: Error: cannot allocate 6291472384 bytes of
InnoDB: memory with malloc! Total allocated memory
InnoDB: by InnoDB 44607576 bytes. Operating system errno: 12
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: Note that in most 32-bit computers the process
InnoDB: memory space is limited to 2 GB or 4 GB.
InnoDB: We keep retrying the allocation for 60 seconds...
InnoDB: Fatal error: cannot allocate the memory for the buffer pool
080506  3:38:14 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
080506  3:38:14 [ERROR] Do you already have another mysqld server running on port: 3306 ?
080506  3:38:14 [ERROR] Aborting

How to repeat:
[6 May 2008 17:52] MySQL Verification Team
Thank you for the bug report. Duplicate of bug: http://bugs.mysql.com/bug.php?id=11609
[7 May 2008 0:29] dan radom
How is it not a bug when safe_mysqld tries to start the DB thinking it has crashed?