mysqld is restarting, a lot. So I put it into debug mode, got 200KB+ trace file, and
then took mysqld out of debug mode. Now I'm trying to analyze the trace file. The best
clue I'm finding are these lines:
vio_read: error: Got error 35 during read
vio_read: error: Got error 4 during read
On Thu, Aug 30, 2001 at 05:01:14PM -0700, Rodney Broom wrote:
mysqld is restarting, a lot. So I put it into debug mode, got 200KB+
trace file, and then took mysqld out of debug mode. Now I'm trying
to analyze the trace file. The best clue I'm finding are these
lines:
vio_read: error:
From: s. keeling [EMAIL PROTECTED]
vio_read: error: Got error 35 during read
Error code 35: Resource deadlock avoided
That fits with with the SIG 11 that I'm seeing in the error log.
vio_read: error: Got error 4 during read
Error code 4: Interrupted system call
That must be
Try fixing all tables/indexes.
-Original Message-
From: s. keeling [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 30, 2001 5:55 PM
To: mysql_mailing list
Subject: Re: Debugging: Analysis
On Thu, Aug 30, 2001 at 05:01:14PM -0700, Rodney Broom wrote:
mysqld is restarting, a lot
From: Bill Blowitz [EMAIL PROTECTED]
Try fixing all tables/indexes.
Actually, I started with
% myisamchk -Ber ...
on all tables that -e said needed to be fixed.
---
Rodney Broom
Programmer: Desert.Net
-
Before posting,
[mailto:[EMAIL PROTECTED]]
Sent: Friday, 31 August 2001 11:32 AM
To: [EMAIL PROTECTED]
Subject: Re: Debugging: Analysis
From: Bill Blowitz [EMAIL PROTECTED]
Try fixing all tables/indexes.
Actually, I started with
% myisamchk -Ber ...
on all tables that -e said needed to be fixed.
---
Rodney
