Re: InnoDB Crash

2010-10-12 Thread Willy Mularto
I got the solution. I stop the ib* files in MySQL datadir and start the server. Now everything is back to normal. Thanks. sangprabv sangpr...@gmail.com http://www.petitiononline.com/froyo/ On Oct 12, 2010, at 11:00 PM, Suresh Kuna wrote: > Hey Willy - Install the new binaries and start mysq

Re: InnoDB Crash

2010-10-12 Thread Suresh Kuna
Hey Willy - Install the new binaries and start mysql with new binary as basedir and see whether innodb has enabled or not. Check the error log why the innodb is getting disabled, make a copy of it here too. On Tue, Oct 12, 2010 at 2:57 PM, Willy Mularto wrote: > Hi List, > Last night accidentall

Re: innodb crash

2008-02-13 Thread Ananda Kumar
Check the permission on mysql database realted files, it shoud be owned by mysql user. regards anandkl On Feb 13, 2008 4:42 PM, Saravanan <[EMAIL PROTECTED]> wrote: > Hi List, > > I got crash when i was creating procedure and it listed the following > error > > *** glibc detected *** /usr/local/

Re: InnoDB Crash RECOVERY HELP (Urgent)

2006-09-21 Thread Eric Bergen
The error message says to go to http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html to learn how to set the different recovery options for innodb. On 9/21/06, Sayed Hadi Rastgou Haghi <[EMAIL PROTECTED]> wrote: Dear all, our DB server crashed and when I try to start Mysql /etc/init.d/my

Re: Innodb crash on failed read disk

2005-07-10 Thread Per Andreas Buer
Ady Wicaksono <[EMAIL PROTECTED]> writes: > Dear All > > I use RedHat 9 with 2,5 Gbyte RAM, Intel(R) Xeon(TM) CPU 2.80GHz > (Hyperthread), > filesystem ext3 standar linux journaling filesystem. > > Today my DB is crash :(, here is the log. Could it be that our stacks and your heaps might have m

(More Data) Re: Innodb crash on failed read disk

2005-07-05 Thread Ady Wicaksono
Seems that i have a bad block :( # badblocks -sv /dev/sda3 Checking for bad blocks in read-only mode From block 0 to 10241437 Checking for bad blocks (read-only test): 102414360/ 10241437 done Pass completed, 1 bad blocks found. Ady Wicaksono wrote: Dear All I use RedHat 9 with 2,5 Gbyte RA

Re: InnoDB crash and runaway rollback - help pls

2005-02-08 Thread Heikki Tuuri
Tobias, - Alkuperäinen viesti - Lähettäjä: "Tobias Asplund" <[EMAIL PROTECTED]> Vastaanottaja: "Heikki Tuuri" <[EMAIL PROTECTED]> Kopio: Lähetetty: Tuesday, February 08, 2005 7:46 PM Aihe: Re: InnoDB crash and runaway rollback - help pls On Tue, 8 F

Re: InnoDB crash and runaway rollback - help pls

2005-02-08 Thread Tobias Asplund
On Tue, 8 Feb 2005, Heikki Tuuri wrote: > You should upgrade to 4.1.9. That version commits ALTER TABLE at every 10 > 000 rows, and a runaway rollback can no longer happen. This is very nice! Are there any plans for the same with INSERT ... SELECT -type statements? -- MySQL General Mailing List

Re: InnoDB crash and runaway rollback - help pls

2005-02-08 Thread Heikki Tuuri
Devananda, the ALTER TABLE creates a temporary table #sql... The rollback is running in that table. The manual contains instructions on how to rename and drop such table. You should upgrade to 4.1.9. That version commits ALTER TABLE at every 10 000 rows, and a runaway rollback can no longer hap

Re: InnoDB crash issue

2004-10-19 Thread Heikki Tuuri
Ian, FILE I/O I/O thread 0 state: waiting for i/o request (insert buffer thread) I/O thread 1 state: waiting for i/o request (log thread) I/O thread 2 state: waiting for i/o request (read thread) I/O thread 3 state: waiting for i/o request (write thread) Pending normal aio reads: 0, aio w

Re: Innodb crash under Win2000

2003-09-10 Thread Heikki Tuuri
- From: ""Heikki Tuuri"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Tuesday, September 09, 2003 2:47 PM Subject: Re: Innodb crash under Win2000 > Rafa, > > is this the server you suspected to have some hardware problem? > > Pleas

Re: Innodb crash under Win2000

2003-09-09 Thread Heikki Tuuri
Rafa, is this the server you suspected to have some hardware problem? Please send me the whole .err log for analysis. Best regards, Heikki Innobase Oy http://www.innodb.com InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for MySQL Order

Re: InnoDB crash - recover + bug

2003-08-14 Thread Heikki Tuuri
Mads, - Original Message - From: "Mads Jørgensen" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Thursday, August 07, 2003 3:42 PM Subject: InnoDB crash - recover + bug > Greetings all. > > I have a bit of a problem here, a database i'm administering was somehow = > corrup

RE: InnoDB crash - recover + bug

2003-08-14 Thread Mads Jørgensen
>> Greetings all. >> >> I have a bit of a problem here, a database i'm administering was somehow = >> corrupted, and i'm unable to recover it in any way. > >what happened? A power outage? You deleted the ib_logfiles? Modified my.cnf? >Hard disk broke? Thats the weird thing, nothing abnormal happen

RE: InnoDB crash - recover + bug

2003-08-07 Thread Heikki Tuuri
from a running server, which very probably creates corrupt backups? Best regards, Heikki Innobase Oy http://www.innodb.com InnoDB - transactions, foreign keys, and a hot backup tool for MySQL Order MySQL support from http://www.mysql.com/support/index.html ... Subject: RE: InnoDB

Re: InnoDB crash report; fatal failure on restarts too!

2003-03-07 Thread Ask Bjoern Hansen
On Thu, 6 Mar 2003, Jeremy Zawodny wrote: > > I am running RedHat 7.3, mostly using InnoDB's. I am using the > > MySQL-Max rpms (4.0.11) from mysql.com. > > > > Earlier today it crashed, and while trying to start up again it > > crashed again. Now I can't start the server with the InnoDB tables.

Re: InnoDB crash report; fatal failure on restarts too!

2003-03-07 Thread Heikki Tuuri
AIL PROTECTED]> To: "Zak Greant" <[EMAIL PROTECTED]> Cc: "Heikki Tuuri" <[EMAIL PROTECTED]> Sent: Friday, March 07, 2003 3:12 AM Subject: Re: InnoDB crash report; fatal failure on restarts too! > On Thu, 6 Mar 2003, Zak Greant wrote: > > A quick update.

Re: InnoDB crash report; fatal failure on restarts too!

2003-03-07 Thread Jeremy Zawodny
On Thu, Mar 06, 2003 at 04:24:10PM -0800, Ask Bjoern Hansen wrote: > > I am running RedHat 7.3, mostly using InnoDB's. I am using the > MySQL-Max rpms (4.0.11) from mysql.com. > > Earlier today it crashed, and while trying to start up again it > crashed again. Now I can't start the server with

Re: InnoDB Crash [more info]

2003-02-21 Thread Heikki Tuuri
copies pointers to fields in ibuf_rec, and we must - Original Message ----- From: "Heikki Tuuri" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, February 21, 2003 10:35 PM Subject: Re: InnoDB Crash [more info] > Michael

Re: InnoDB Crash [more info]

2003-02-21 Thread Heikki Tuuri
Michael, how do I send you email? A 'Spamcop' seems to block email to you. Regards, Heikki - Original Message - From: "Heikki Tuuri" <[EMAIL PROTECTED]> To: ""Michael T. Babcock"" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Se

Re: InnoDB Crash [more info]

2003-02-21 Thread Heikki Tuuri
2.4.20. Regards, Heikki Innobase Oy sql query - Original Message - From: ""Michael T. Babcock"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Friday, February 21, 2003 9:23 PM Subject: Re: InnoDB Crash [more info] > Michael T. Babcock wrot

Re: InnoDB Crash [more info]

2003-02-21 Thread Michael T. Babcock
Michael T. Babcock wrote: I've got a nice MySQL crash that happened during the night last night and I can't seem to get it to come back online for me without --skip-innodb. Follow-up with mysql's bug report: MySQL support: none Synopsis:InnoDB Crashing on Startup Severity:critical P

Re: InnoDB crash?

2002-12-10 Thread Heikki Tuuri
Ervin, - Original Message - From: "Ervin Gerke" <[EMAIL PROTECTED]> To: "'Heikki Tuuri'" <[EMAIL PROTECTED]> Sent: Tuesday, December 10, 2002 8:53 PM Subject: RE: InnoDB crash? > Heikki, > > That's all mysqld reported in err log.

Re: InnoDB crash?

2002-12-10 Thread Heikki Tuuri
Ervin, the assertion in page0page.c line 450 means InnoDB could not move index records from a page to another page though it always checks that there should be enough space. I have not seen this assertion fail before. Did mysqld print a srack trace to the .err log? Can you send me the whole error

RE: InnoDB crash?

2002-12-10 Thread Simon Green
Have you looked if there is a problem with page0page.c ? Simon -Original Message- From: Ervin Gerke [mailto:[EMAIL PROTECTED]] Sent: 10 December 2002 12:07 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: InnoDB crash? Got this one after a power failure. My system is Redhat 7.3, ker

Re: InnoDB crash repeated under 3.23.51...

2002-05-29 Thread Heikki Tuuri
Jeremy, I think this happens because the InnoDB transaction handle has already been freed in end_thread when MySQL still writes one log item for the connection. Please test the following patch. Replace the function innobase_close_connection with the one below. I forgot to set innobase_tid to NULL

Re: InnoDB crash repeated under 3.23.51...

2002-05-29 Thread Jeremy Zawodny
On Wed, May 29, 2002 at 12:13:49AM -0700, Jeremy Zawodny wrote: > Heikki, > > After a good 6-8 hours of runnning, the server just restarted itself > (running the most recent build from the 3.23.xx tree, as you > suggested). Just for the record, it happened again. So it's reproducable to a dregr

Re: InnoDB crash on 3.23.49a...

2002-05-28 Thread Jeremy Zawodny
On Tue, May 28, 2002 at 01:16:28PM -0700, Jeremy Zawodny wrote: > On Tue, May 28, 2002 at 10:59:45PM +0300, Heikki Tuuri wrote: > > Jeremy, > > > > can you build your own 3.23.51? There is actually the same memory > > overwrite bug in gethostname_r of glibc/Linux in .49a as in .50. > > I'll inst

Re: InnoDB crash on 3.23.49a...

2002-05-28 Thread Heikki Tuuri
gt; Cc: <[EMAIL PROTECTED]> Sent: Tuesday, May 28, 2002 11:18 PM Subject: Re: InnoDB crash on 3.23.49a... > On Tue, May 28, 2002 at 10:59:45PM +0300, Heikki Tuuri wrote: > > Jeremy, > > > > can you build your own 3.23.51? There is actually the same memory overwrit

Re: InnoDB crash on 3.23.49a...

2002-05-28 Thread Jeremy Zawodny
On Tue, May 28, 2002 at 10:59:45PM +0300, Heikki Tuuri wrote: > Jeremy, > > can you build your own 3.23.51? There is actually the same memory overwrite > bug in gethostname_r of glibc/Linux in .49a as in .50. Come to think of it, if that's what caused the problem, wouldn't this "solve" it for no

Re: InnoDB crash on 3.23.49a...

2002-05-28 Thread Jeremy Zawodny
On Tue, May 28, 2002 at 10:59:45PM +0300, Heikki Tuuri wrote: > Jeremy, > > can you build your own 3.23.51? There is actually the same memory > overwrite bug in gethostname_r of glibc/Linux in .49a as in .50. I'll install 3.23.51 tonight. I have been doing daily builds of the 3.23 and 4.0 tree

Re: InnoDB crash on 3.23.49a...

2002-05-28 Thread Heikki Tuuri
Jeremy, can you build your own 3.23.51? There is actually the same memory overwrite bug in gethostname_r of glibc/Linux in .49a as in .50. If you build mysqld yourself you can run it inside gdb and do bt full when it crashes. That might help in tracing the bug. The assertion failure below means