Re: MySQL 4.0.13 Crashed

Hi Alex,
Thanks, I'll take note of that..

BRgds, Richard



Alexander Keremidarski <[email protected]>        23/09/2003 06:42 PM


To:     BORNAY Richard/Engr/STATS/ST Group@ST Domain
cc:     [email protected]
Subject: Re: MySQL 4.0.13 Crashed







Hello,

[email protected] wrote:
> Hi List,

> I am administering MySQL 4.0.13 on a Solaris 8 OS, and just this morning 
I 
> encountered an error message like the one below. This is actually my 
first 
> time to encounter such crash, I already tried searching for archives and 

> the mysql doc to look for a solution but didn't find an exact answer. I 
am 
> not sure also if I need to report a bug in Mysql website so I decided to 

> report it first in the list. The way i understand it is that it already 
> exceed the key_buffer_size of 16M which I stated in my .my.cnf, I tried 
to 
> increase it to 30M but mysqld still doesn't start-up, it actually result 

> in a segmentation fault error which has the same error message. For now, 
I 
> do not know what to do but to upgrade if there's no way to resolve this 
> problem.

As Antony already replied you increasing buffers can't help you if you 
don't have 
enough memory available. It is even opposite. If you tell MySQL to 
assigning 
bigger buffers when system memory is limited you are calling for troubles. 
In your 
case it is kernel which kills mysqld when it tries to consume too much 
memory.

Consider decreasing buffers instead of increasing them.
Keep in mind also some of buffers are session specific, some are MyISAM 
only 
related etc.

> I will really appreciate any help from the list....

Please note that bugs@list is dedicated to repeatable Bugs so you should 
always 
try to provide repeatable test case.

Your qeustion is more for Support area, not Bugs. You should better ask at 
general 
list [email protected] or you can consider purchasing Support Contract 
(check 
www.mysql.com/support for more details)

> ERROR MESSAGES:
> 030922 10:32:37  mysqld started
> 030922 10:32:38  InnoDB: Started
> /usr/local/mysql/libexec/mysqld: ready for connections.
> Version: '4.0.13-log'  socket: '/usr/local/mysql/var/mysql.sock'  port: 
> 3306
> 030923  7:30:06  Out of memory;  Check if mysqld or some other process 
> uses all available memory. If not you may have to use 'ulimit' to allow 
> mysqld to use more
>  memory or you can add more swap space
> 030923  7:30:06  Out of memory;  Check if mysqld or some other process 
> uses all available memory. If not you may have to use 'ulimit' to allow 
> mysqld to use more
>  memory or you can add more swap space
> mysqld got signal 11;
<cut>

What in the above output let you think that key_buffer_size was "exceeded"

 > The way i understand it is that it already
 > exceed the key_buffer_size of 16M which I stated in my .my.cnf,

MySQL will never try to allocate more memory for buffer than specified and 
will 
never crash when some of buffers is filled up. All buffer sizes affect 
performance 
only, not stability.

> Thanks, Richard
> 

Best regards

-- 
  Are you MySQL certified? -> http://www.mysql.com/certification
  For technical support contracts, visit https://order.mysql.com/?ref=msal
     __  ___     ___ ____  __
    /  |/  /_ __/ __/ __ \/ /    Mr. Alexander Keremidarski 
<[email protected]>
   / /|_/ / // /\ \/ /_/ / /__   MySQL AB, Full-Time Developer
  /_/  /_/\_, /___/\___\_\___/   Sofia, Bulgaria
          <___/  www.mysql.com




-- 
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe:    http://lists.mysql.com/[email protected]