- Original Message - From: "Heikki Tuuri"
<[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Friday, December 16, 2005 3:46 PM
Subject: Re: CPU 100% + crashes ...
Dilipan,
thank you.
I think there indeed is a slight unprotected access in:
> 0x8158a17 inn
fwrite(str, 1, len, f);
if (dyn_str)
{
my_free(dyn_str, MYF(0));
}
...
"
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Fri
Dilipan,
thank you.
I think there indeed is a slight unprotected access in:
> 0x8158a17 innobase_mysql_print_thd + 471
We will investigate if it has been fixed in 4.1.xx.
Again, SHOW INNODB STATUS\G shows a very light load inside InnoDB. You
would get more informative output if you would wai
can you please post the complete .err log that also contains
information about the crashes. If there are stack traces, please
resolve them.
-
Hello.
> server version: 4.0.18-log ( I know it's old but we can't update for
>the moment )
MySQL shouldn't die even under huge load, it is bad that you can't
update, and work with old version which has lots of bugs. Do you have
a stack trace in the error log? Please, resolve and send it
Dilipan,
can you please post the complete .err log that also contains information
about the crashes. If there are stack traces, please resolve them.
The workload inside InnoDB does not look that big if what you have posted is
a typical SHOW INNODB STATUS\G. Is that the case?
What does 'top'
ECTED]
Subject: Re: CPU 100%
If you find an answer, I would really like to hear about it. I have
been working on this for months. No one seems to have a clear answer,
although several people have reported curing it by either adding your
server to c:\WINNT\system32\drivers\etc\hosts or settin
If you find an answer, I would really like to hear about it. I have
been working on this for months. No one seems to have a clear answer,
although several people have reported curing it by either adding your
server to c:\WINNT\system32\drivers\etc\hosts or setting the mysql
service up to run