Re: MySQL 4.0.13 Crashed

On Tue, 2003-09-23 at 04:18, [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.
> 
> I will really appreciate any help from the list....

Out of memory errors followed by a SIGSEGV... Are you sure that there is
enough available memory? 

Has it only recently started doing that?

Increasing the buffer sizes would not help if there is not enough memory
available from the operating system.

-- 
Antony T Curtis, Senior Software Developer
MySQL AB, www.mysql.com
 Office: +44 118 377 3247

Are you MySQL certified?  www.mysql.com/certification

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQA/cAPzLUyqNTyfZjARAuIwAJwIpfzIHGEn2Td+lfQLKRKKZnpaywCgoANl
2TfHbOK37jHNUfI9pVd7vV4=
=I1nY
-----END PGP SIGNATURE-----