OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: MySQL Crash when Open_files reach 128

From: Todd Lyons (tlyonsivenue.com)
Date: Wed May 02 2012 - 11:12:02 CDT


On Wed, May 2, 2012 at 4:58 AM, vishesh kumar <linuxtovisheshgmail.com> wrote:
> I am getting following in error log
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
> 120502 07:52:05  mysqld started
> 120502  7:52:05 [Warning] Asked for 196608 thread stack, but got 126976
> 120502  7:52:05  InnoDB: Started; log sequence number 0 479249
> 120502  7:52:05 [Note] /usr/local/mysql-5.0.67/bin/mysqld: ready for
> connecti.
> Version: '5.0.67-community'  socket: '/tmp/mysql.sock'  port: 3306  MySQL
> Comity Edition (GPL)
> 120502  7:56:01 [Note] /usr/local/mysql-5.0.67/bin/mysqld: Normal shutdown
>
> 120502  7:56:03  InnoDB: Starting shutdown...
> 120502  7:56:04  InnoDB: Shutdown completed; log sequence number 0 479249
> 120502  7:56:04 [Note] /usr/local/mysql-5.0.67/bin/mysqld: Shutdown complete
> 120502 07:56:04  mysqld ended

Honestly, that doesn't look like an error. It looks like something is
connecting to your server and telling mysql to shut down. It's one
second after 7:56, so I'd look for something in a cronjob that's
telling it to shut down. Please check that before deciding it's a
memory or file issue.

...Todd
--
Always code as if the guy who ends up maintaining your code will be a
violent psychopath who knows where you live. -- Martin Golding

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