MySQL 4.0.13 Crashed

--=_alternative 0017FE9D48256DAA_=
Content-Type: text/plain; charset="us-ascii"

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....

I also include the settings for my .my.cnf for additional information.
port = 3306
socket = /usr/local/mysql/var/mysql.sock
#skip-locking
set-variable = key_buffer=16M
set-variable = max_allowed_packet=1M
set-variable = table_cache=64
set-variable = sort_buffer=512K
set-variable = net_buffer_length=8K
set-variable = myisam_sort_buffer_size=8M
log-bin
server-id = 1

# Uncomment the following if you are using Innobase tables
innodb_data_file_path = ibdata1:400M
innodb_data_home_dir = /usr/local/mysql/var/
innodb_log_group_home_dir = /usr/local/mysql/var/
innodb_log_arch_dir = /usr/local/mysql/var/
set-variable = innodb_mirrored_log_groups=1
set-variable = innodb_log_files_in_group=3
set-variable = innodb_log_file_size=5M
set-variable = innodb_log_buffer_size=8M
innodb_flush_log_at_trx_commit=1
innodb_log_archive=0
set-variable = innodb_buffer_pool_size=16M
set-variable = innodb_additional_mem_pool_size=2M
set-variable = innodb_file_io_threads=4
set-variable = innodb_lock_wait_timeout=50

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;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly
built,
or misconfigured. This error can also be caused by malfunctioning
hardware.
We will try our best to scrape up some info that will hopefully help
diagnose
the problem, but since we have already crashed, something is definitely
wrong
and this may fail.

key_buffer_size=16777216
read_buffer_size=131072
sort_buffer_size=524280
max_used_connections=2
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections =
80383 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.


Thanks, Richard

--=_alternative 0017FE9D48256DAA_=--

Re: MySQL 4.0.13 Crashed

--=-cIRqOEbjM2F45k34CCDY
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2003-09-23 at 04:18, richardb@stats.st.com.sg wrote:
> Hi List,
> I am administering MySQL 4.0.13 on a Solaris 8 OS, and just this morning =
I=20
> encountered an error message like the one below. This is actually my firs=
t=20
> time to encounter such crash, I already tried searching for archives and=20
> the mysql doc to look for a solution but didn't find an exact answer. I a=
m=20
> not sure also if I need to report a bug in Mysql website so I decided to=20
> report it first in the list. The way i understand it is that it already=20
> exceed the key_buffer_size of 16M which I stated in my .my.cnf, I tried t=
o=20
> increase it to 30M but mysqld still doesn't start-up, it actually result=20
> in a segmentation fault error which has the same error message. For now, =
I=20
> do not know what to do but to upgrade if there's no way to resolve this=20
> problem.
>=20
> 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?=20

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.

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

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


--=-cIRqOEbjM2F45k34CCDY
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

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

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

--=-cIRqOEbjM2F45k34CCDY--

Re: MySQL 4.0.13 Crashed

--=_alternative 0036D1D148256DAA_=
Content-Type: text/plain; charset="us-ascii"

Hi Anthony,
Thanks for your quick response...however it just started this morning
(Singapore). I'm wondering if the GNOME application has an effect since it
eats up a lot of memory?


Thanks, Richard



Antony T Curtis 23/09/2003 04:27 PM


To: BORNAY Richard/Engr/STATS/ST Group@ST Domain
cc: bugs@lists.mysql.com
Subject: Re: MySQL 4.0.13 Crashed







On Tue, 2003-09-23 at 04:18, richardb@stats.st.com.sg 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




<< Attachment Removed : signature.asc>>



--=_alternative 0036D1D148256DAA_=--

Re: MySQL 4.0.13 Crashed

Hello,

richardb@stats.st.com.sg 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 mysql@lists.mysql.com 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;


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
/ /|_/ / // /\ \/ /_/ / /__ 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/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: MySQL 4.0.13 Crashed

--=_alternative 003CF8BD48256DAA_=
Content-Type: text/plain; charset="us-ascii"

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

BRgds, Richard



Alexander Keremidarski 23/09/2003 06:42 PM


To: BORNAY Richard/Engr/STATS/ST Group@ST Domain
cc: bugs@lists.mysql.com
Subject: Re: MySQL 4.0.13 Crashed







Hello,

richardb@stats.st.com.sg 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 mysql@lists.mysql.com 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;


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

/ /|_/ / // /\ \/ /_/ / /__ 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/bugs?unsub=richardb@stats.st.com.sg




--=_alternative 003CF8BD48256DAA_=--

Re: MySQL 4.0.13 Crashed

--=-EKBAjvPFClosZ3IL/vaJ
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2003-09-23 at 11:11, richardb@stats.st.com.sg wrote:
> Hi Anthony,
> I started uninstalling the GNOME and after sometime restart mysql
> server, and it works now..
> By the way, heres the result of vmstat command.
>=20
> Crichardb@florida at /usr1/richardb/bin > vmstat
> procs memory page disk faults =20
> cpu
> r b w swap free re mf pi po fr de sr f0 s0 s6 -- in sy cs
> us sy id
> 0 0 0 2099512 164064 198 1782 78 3 3 0 0 0 5 0 0 461 3242 2095
> 36 20 44
>=20
> I really appreciate your help !!!!
>=20
> :) Thanks, Richard
>=20

No problems.

(cc:ed to list, issue closed)

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

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


--=-EKBAjvPFClosZ3IL/vaJ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

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

iD8DBQA/cDUhLUyqNTyfZjARAqBBAJ9yvwjLAQrVNzH74YrJVLqeGS9DlACd HcPq
N4j45IKOAZAml7ju4OG8aCY=
=H44V
-----END PGP SIGNATURE-----

--=-EKBAjvPFClosZ3IL/vaJ--