PDA

Click to See Complete Forum and Search --> : The MySql service terminated unexpectedly. It has done this 1 time(s). The followin

KABOOM
08-29-2002, 02:01 AM
Does anyone else get this?

I'm using Windows 2000 as a testing server before I upload my stuff to
Linux server and it looks like MySQL is crashing my computer as it leaves
the following message in the Event Viewer:
"The MySql service terminated unexpectedly. It has done this 1 time(s).
The following corrective action will be taken in 0 milliseconds: No
action."

How do I fix this?

Here's some more specifics on the stuff that i'm running:
Windows 2000 Professional SP3
MySQL v3.23.47
Apache v1.3
Not sure AMD XP 2000 CPU

I'm not sure if PHPTriad is buggy (which is what I used - yes, I know, I cheated). I used v2.2


Thanks,
KABOOM!
which version of PHP i'm running but it is at least v4+
piersk
08-29-2002, 05:28 AM
Since you have Win2k, Im presuming that you are running MySQL as a service. Try re-installing it and run it as a local user.
dRiFT
09-25-2002, 07:56 AM
Yeah I regularly get exactly the same thing on a busy Win2k(Server) box running the latest version of mySQL(3.23.52). The service crashes randomly or so it seems. This also occured with the previous version which I'd hoped installing the latest version would fix to some degree. It's being ran using the Local System account.

I've tried logging all server activity and looking at what happens shortly before a crash, but there's nothing in common with each one. Also all tables are error-free according to CHECK TABLE.

It's a bit of a mysterious problem...
dotwebbie
09-26-2002, 12:13 PM
And no other errors are in the event viewer?
dRiFT
09-26-2002, 12:55 PM
Nope, that's it :/
Just the error message that KABOOM reported.
dotwebbie
09-26-2002, 01:19 PM
What versions does phptriad use of apache, php, and mysql?
dRiFT
11-01-2002, 07:42 AM
Upgraded again to latest mySQL version(3.23.53), using a new ini based on the 'medium' template. Still get exactly the same problem, random shutdowns of the service with no common queries before shutdown. As said before the tables are all error-free according to check table...maybe they should be checked more thoroughly using myisamchk?
dotwebbie
11-01-2002, 09:18 AM
It is certainly worth the try.
Mr.Rostor
11-02-2002, 02:56 PM
Hi, I've got the same error on my web server, I don't know if you belive me but it was done by an old version of the intel nic card.

I solve it by installing the latest driver and the problems never comes again.
dRiFT
11-27-2002, 05:35 AM
Seems like we've found the problem, or at least the query which trips mySQL up. It's a weird one because it doesn't happen all of the time but I'm confident that this query was to blame as our database recently crashed once every 10 or 15mins and after removing the guilty script it's now been up for 18 hours.

...anywayz...looks like it's a problem with full text searching using MATCH.
dotwebbie
11-27-2002, 01:05 PM
dRiFT: have you checked the MySQL bug reports? I haven't heard of this problem before . . .
dRiFT
11-28-2002, 06:35 AM
There's some reports of boolean match problems in version 4, but nothing in 3 as far as I can tell. Uptime now 1 day and 19 hours.
dotwebbie
11-29-2002, 10:09 PM
Hm. Maybe that is what broke the thing. :( Let me/us know if you find anything.