9 messages in com.mysql.lists.win32Re: MySQL Pegs @ 100% cpu and stays| From | Sent On | Attachments |
|---|---|---|
| Martin Noreke | 19 Jun 2002 14:05 | |
| Gelu Gogancea | 19 Jun 2002 14:36 | |
| Martin Noreke | 19 Jun 2002 14:52 | |
| Gelu Gogancea | 19 Jun 2002 15:37 | |
| Martin Noreke | 19 Jun 2002 15:41 | |
| Kevin Higgins | 19 Jun 2002 16:27 | |
| Eduardo Silva | 19 Jun 2002 21:28 | |
| Grigoriy Puzankin | 20 Jun 2002 00:00 | |
| Gelu Gogancea | 20 Jun 2002 03:14 |
| Subject: | Re: MySQL Pegs @ 100% cpu and stays![]() |
|---|---|
| From: | Martin Noreke (mar...@noreke.com) |
| Date: | 06/19/2002 02:52:27 PM |
| List: | com.mysql.lists.win32 |
Hi Gelu,
The tables are pratically non existent. Entire directory of tables is less than 500Kb. Problem occurs after having left the daemon running in background for a while. No data access in progress. Even happend without anyone within 5 yds of the machine one time...
/ Martin
On Thu, 20 Jun 2002 00:36:46 +0300 "Gelu Gogancea" <gge...@arctic.ro> wrote:
Hi, You have huge tables ? This behaviour begin imediatly after you start mysql daemon?.... or... after you save data from your application?
Regards,
Gelu
_____________________________________________________ G.NET SOFTWARE COMPANY
Permanent e-mail address : gg...@gonetsoftware.com gelu...@yahoo.com
----- Original Message ----- From: "Martin Noreke" <mar...@noreke.com> To: <win...@lists.mysql.com> Sent: Thursday, June 20, 2002 12:05 AM Subject: MySQL Pegs @ 100% cpu and stays
Hi Everyone,
We have a peculiar situation here at work. MySQL seems to peg itself at 100% CPU every so often (has happened about 4-5 times) and decides to stay there. Won't quit from the task manager or any other way. Result is needing to pull the power plug.
We have had this problem on XP (possibly on Win2k & NT, still tracking this down across 2 continents, fun fun fun...) and using MySQL 3.23.47 MAX.
The situation is that we use MySQL to store data from one of our apps. It is a one user setup, base install except for using the MAX execuatble so we have access to the dynamic link to databases.
The problem occurs when no one is accessing the database, and it gets lonely or something... :) A complete lock up of the system and I have no idea what could be causing it.
Any ideas on how to take care of this out there?
/ Martin Noreke nor...@tapestrysolutions.com
-- Martin Noreke <mar...@noreke.com>
-- Martin Noreke <mar...@noreke.com>




