Apache Friends Support Forum

Hi, i was running a game server on Xampp, , after few seconds my Mysql auto stopped without any reason, and without errors.
This happened some times, first time two days ago yesterday it happened also.

I want to know why this happen, and if there's a solution so it never closes.
PS.: I've tried to reinstall Xampp but Mysql still crashes..

Thanks!!

Hi, my Mysql constanly crashes, when my server do a save or something that consomes much memory.
I want to know if there's a way to increase the Mysql Memory limit, or if there's another solution so my mysql don't crash.

Thanks.

Missing support info - what XAMPP version and which Windows OS?
Assuming latest stable XAMPP version and Windows XP.

Look in the \xampp\mysql\data\*.err log file for clues.

MySQL settings are in the \xampp\mysql\my.ini file.

Before editing the file make a backup first, then after editing save the file and restart MySQL.

Sorry for the missing informations.
I use Windows Server 2003 and Xampp 1.7.2, and i have 4GB Ram.
Here's the log of the last error:

091222 19:59:15 InnoDB: Operating system error number 995 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/ ... codes.html
InnoDB: File name C:\xampp\mysql\data\ibdata1
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.
091222 19:59:16 [Note] Plugin 'FEDERATED' is disabled.
091222 19:59:16 [Note] PrimeBase XT (PBXT) Engine 1.0.08 RC loaded...
091222 19:59:16 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
091222 19:59:16 [Note] The server was not shutdown correctly, recovery required
InnoDB: Log scan progressed past the checkpoint lsn 0 1680636023
091222 19:59:16 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 0 1682465490
091222 19:59:19 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
091222 19:59:20 InnoDB: Started; log sequence number 0 1682465490
091222 19:59:20 [Note] Event Scheduler: Loaded 0 events
091222 19:59:20 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.1.37' socket: '' port: 3306 Source distribution

It says "ready for connections" on the last lines because i've configured Windows Services to auto restart mysql service if it crashes.

Thanks.

Here's the log of the last error:
Code: Select all
091222 19:59:15 InnoDB: Operating system error number 995 in a file operation.

That's a bug in MySQL.

Is there something i can do to solve this bug?
I tried to search on internet, but i didn't find nothing about a fix...

Thanks.

Is there something i can do to solve this bug?

Waiting for MySQL 5.1.42 or compile MySQL yourself.

I tried to search on internet,

I guess the MySQL bugtracker is a better place then the internet (regardless which search engine you are using)...
(... if you have a problem with MySQL)

Here are some details I could glean about your issues from the Internet that may help with understanding your problem a little better perhaps.

091222 19:59:15 InnoDB: Operating system error number 995 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/ ... codes.html
InnoDB: File name C:\xampp\mysql\data\ibdata1
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.

Seems that this was a reported MySQL bug that was supposed to have been patched in 2008 for later MySQL releases after the bug had been reproduced and recognized and is currently being pushed into 5.1.42 - current XAMPP MySQL version is 5.1.37
http://bugs.mysql.com/bug.php?id=3139

Perhaps you can read this bug report and see that it may also be related to a hardware problem on your PC namely a drive issue

bug report 3139 wrote:For others, we've seen that these sometimes show up when there's an increase in hard drive S.M.A.R.T. counters, implying a hard drive root cause.

So in conclusion you may be having some sort of i/o issues with your hard drive and may be an indication of imminent failure perhaps.

Link to the System error code 995 but typical MS, it does not tell you much:
http://msdn.microsoft.com/en-us/library/ms681388(VS.85).aspx

Link to Internet searches for similar issues to yours:
Operating system error number 995
File operation call: 'Windows aio'

Sorry I can't be of more help on this.

Ok... I'll wait for Mysql 5.1.42.

Thanks for the links and for all the help!!!

Apache Friends Support Forum

Mysql crash suddenly.

Mysql crash suddenly.

Increse Mysql Memory

Re: Mysql crash suddenly.

Re: Mysql crash suddenly.

Re: Mysql crash suddenly.

Re: Mysql crash suddenly.

Re: Mysql crash suddenly.

Re: Mysql crash suddenly.

Re: Mysql crash suddenly.