From: Eli Shemer (apparnetvision.net.il)
Date: Wed Feb 13 2008 - 01:23:38 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Unfortuantely the server crashed and I had to manually boost it

It happened before and I would like to know why so it doesn’t again

I don’t have any innodb database on the system, only mysiam

Do you think adding ram might help ?

From: Krishna Chandra Prajapati [mailto:prajapatikcgmail.com]
Sent: Wednesday, February 13, 2008 8:05 AM
To: Eli Shemer
Subject: Re: crash

Hi,

The below information shows that innodb data get crashed and then started
the recovery of data. During recovery of data there was a memory shortage
(Out of memory). At last recovery gets completed.

Thanks,
Prajapati

On Feb 13, 2008 12:44 AM, Eli Shemer <HYPERLINK
"mailto:apparnetvision.net.il"apparnetvision.net.il> wrote:

Can someone explain this?

Thanks.

080212 15:54:39 mysqld started

080212 15:54:39 InnoDB: Started; log sequence number 0 43743

080212 15:54:40 [Note] /usr/libexec/mysqld: ready for connections.

Version: '5.0.54-log' socket: '/var/lib/mysql/mysql.sock' port: 3306
Source distribution

Number of processes running now: 0

080212 17:23:24 mysqld restarted

080212 17:23:25 InnoDB: Started; log sequence number 0 43743

080212 17:23:25 [Note] Recovering after a crash using mysql-bin

080212 17:23:25 [Note] Starting crash recovery...

080212 17:23:25 [Note] Crash recovery finished.

/usr/libexec/mysqld: Out of memory (Needed 463827968 bytes)

/usr/libexec/mysqld: Out of memory (Needed 347870208 bytes)

/usr/libexec/mysqld: Out of memory (Needed 260901888 bytes)

/usr/libexec/mysqld: Out of memory (Needed 195674112 bytes)

/usr/libexec/mysqld: Out of memory (Needed 146755584 bytes)

080212 17:23:26 [Note] /usr/libexec/mysqld: ready for connections.

Version: '5.0.54-log' socket: '/var/lib/mysql/mysql.sock' port: 3306
Source distribution

Number of processes running now: 0

080212 20:45:03 mysqld restarted

080212 20:45:04 InnoDB: Started; log sequence number 0 43743

080212 20:45:04 [Note] Recovering after a crash using mysql-bin

080212 20:45:08 mysqld ended

080212 21:08:21 mysqld started

080212 21:08:22 InnoDB: Started; log sequence number 0 43743

080212 21:08:22 [Note] Recovering after a crash using mysql-bin

080212 21:08:23 [Note] Starting crash recovery...

080212 21:08:23 [Note] Crash recovery finished.

080212 21:08:23 [Note] /usr/libexec/mysqld: ready for connections.

Version: '5.0.54-log' socket: '/var/lib/mysql/mysql.sock' port: 3306
Source distribution

[rootAlpion ~]# date

Tue Feb 12 21:09:19 IST 2008

[rootAlpion ~]#

Internal Virus Database is out-of-date.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.16.4/1146 - Release Date: 22/11/2007
18:55

--
Krishna Chandra Prajapati
MySQL DBA,
Ed Ventures e-Learning Pvt.Ltd.
1-8-303/48/15, Sindhi Colony
P.G.Road, Secunderabad.
Pin Code: 500003
Office Number: 040-66489771
Mob: 9912924044
URL: HYPERLINK "http://ed-ventures-online.com"ed-ventures-online.com
Email-id: HYPERLINK "mailto:prajapatikcgmail.com"prajapatikcgmail.com

Internal Virus Database is out-of-date.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.16.4/1146 - Release Date: 22/11/2007
18:55

Internal Virus Database is out-of-date.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.16.4/1146 - Release Date: 22/11/2007
18:55
 

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]