From: Todd Lyons Date: May 2 2012 4:12pm Subject: Re: MySQL Crash when Open_files reach 128 List-Archive: http://lists.mysql.com/mysql/227292 Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, May 2, 2012 at 4:58 AM, vishesh kumar wr= ote: > I am getting following in error log > > -------------------------------------------------------------------------= ---------------------------------------------------------------------------= ------------ > 120502 07:52:05 =A0mysqld started > 120502 =A07:52:05 [Warning] Asked for 196608 thread stack, but got 126976 > 120502 =A07:52:05 =A0InnoDB: Started; log sequence number 0 479249 > 120502 =A07:52:05 [Note] /usr/local/mysql-5.0.67/bin/mysqld: ready for > connecti. > Version: '5.0.67-community' =A0socket: '/tmp/mysql.sock' =A0port: 3306 = =A0MySQL > Comity Edition (GPL) > 120502 =A07:56:01 [Note] /usr/local/mysql-5.0.67/bin/mysqld: Normal shutd= own > > 120502 =A07:56:03 =A0InnoDB: Starting shutdown... > 120502 =A07:56:04 =A0InnoDB: Shutdown completed; log sequence number 0 47= 9249 > 120502 =A07:56:04 [Note] /usr/local/mysql-5.0.67/bin/mysqld: Shutdown com= plete > 120502 07:56:04 =A0mysqld 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 --=20 Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live. -- Martin Golding