At 11:07 AM 3/23/2005, V. M. Brasseur wrote:
You say it usually crashes near the same record? Could you post the
record information and also the query which is being run?
Also, is there any information in your hostname.err file? If mysqld is
bailing (and it appears that it is), it ought to be
"Lost connection to MySQL server during query"
The last time I saw this mysqld was segfaulting on a specific query. The
solution was to run an extended repair on the tables in question.
http://dev.mysql.com/doc/mysql/en/repair-table.html
I would reccommend against doing this until after hours as
mos <[EMAIL PROTECTED]> wrote on 03/23/2005 12:04:59 PM:
> I have a compiled application that accesses a dedicated MySQL 4.1.1
server
> with MyISAM tables on Win XP. For some reason when the application is in
a
> loop doing simple single table Select statements, the MySQL server after
48
> s
You say it usually crashes near the same record? Could you post the
record information and also the query which is being run?
Also, is there any information in your hostname.err file? If mysqld is
bailing (and it appears that it is), it ought to be writing something
useful to the error log.
I have a compiled application that accesses a dedicated MySQL 4.1.1 server
with MyISAM tables on Win XP. For some reason when the application is in a
loop doing simple single table Select statements, the MySQL server after 48
seconds of processing will upchuck with the error "Can't connect to My
