Bug #18296 | MySQL 5 terminated unexpectedly | ||
---|---|---|---|
Submitted: | 17 Mar 2006 8:59 | Modified: | 17 Mar 2006 12:10 |
Reporter: | SASANKA PANCHAMUKHI | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0 | OS: | Windows (winXP SP2) |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[17 Mar 2006 8:59]
SASANKA PANCHAMUKHI
[17 Mar 2006 12:10]
MySQL Verification Team
Thank you for the bug report. We need more information for to try to repeat the behavior reported on our side. Which exactly server version are you using? If a server prior to 5.0.19 can you try to upgrade and to test?. If the issue continues, then verify if the error log shows some messages which can point the cause of the crash, the error log is a file you can find on your \data directory by default it is the host_name.err or you can search on your Windows events application if there is some error or warning message. Also you can try to start the server as standalone: mysqld-nt --standalone --console opening a command prompt screen and to change to the \bin directory of your installation. When you get the message error see if some error message was showed by the server. Thanks in advance.