AIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Friday, October 07, 2005 10:38 PM
Subject: Re: crashes in InnoDB with MySQL 4.1.14 (semaphore wait timeout)
Heikki Tuuri wrote:
Deva,
it is probably this insert operation that is stuck, and is holding an
S-latch of an index tree in emai
Heikki Tuuri wrote:
Deva,
it is probably this insert operation that is stuck, and is holding an
S-latch of an index tree in emails_history_30_30:
---TRANSACTION 0 1856588555, ACTIVE 858 sec, process no 1792, OS thread
id 2445845440 inserting, thread declared inside InnoDB 318
mysql tables in
- Original Message -
From: "Devananda" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, October 06, 2005 11:02 PM
Subject: Re: crashes in InnoDB with MySQL 4.1.14 (semaphore wait timeout)
Heikki Tuuri wrote:
Deva,
please post those transactions which have
abase.myodbc
Sent: Thursday, October 06, 2005 10:14 AM
Subject: Re: crashes in InnoDB with MySQL 4.1.14 (semaphore wait timeout)
Heikki Tuuri wrote:
Deva,
please post the complete output except the transaction data.
Regards,
Heikki
Please let me know if there is any
c
Sent: Thursday, October 06, 2005 10:14 AM
Subject: Re: crashes in InnoDB with MySQL 4.1.14 (semaphore wait timeout)
Heikki Tuuri wrote:
Deva,
please post the complete output except the transaction data.
Regards,
Heikki
Please let me know if there is any additional data I can provide to h
Heikki Tuuri wrote:
Deva,
please post the complete output except the transaction data.
Regards,
Heikki
Please let me know if there is any additional data I can provide to help
resolve this.
=
051005 7:18:17 INNODB MONITOR OUTPUT
==
Deva,
please post the complete output except the transaction data.
Regards,
Heikki
- Original Message -
From: "Devananda" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, October 05, 2005 7:05 PM
Subject: Re: crashes in InnoDB with MySQL 4
Devananda wrote:
One of our servers which is configured primarily for InnoDB has crashed
in the same fashion three times in the past 48 hours. I've been going
over the error log, and I would like to know if anyone else has seen
similar errors, or can give me some pointers to work out this probl
