Page 1 of 1

MYSQL keeps crashing [Solved]

PostPosted: 28. February 2013 17:15
by jsrip2012
I have a problem, where because it gets so annoying ive had to reinstall xampp 3 times already. The first time apache used to crash when I pressed start with an error saying the port may be blocked etc, I looked on the forums and couldn't find anything, so I reinstalled xampp reluctantly and then once I had reinstalled it about 4 months later, apache kept crashing on pressing start again and I reinstalled it again and now (after 4 days of reinstalling), the same happens to MySQL but when I try to check the error logs there is limited information. This is what I got:
130228 15:52:32 [Note] Plugin 'FEDERATED' is disabled.
130228 15:52:32 InnoDB: The InnoDB memory heap is disabled
130228 15:52:32 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130228 15:52:32 InnoDB: Compressed tables use zlib 1.2.3
130228 15:52:32 InnoDB: Initializing buffer pool, size = 16.0M
130228 15:52:32 InnoDB: Completed initialization of buffer pool
130228 15:52:32 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130228 15:52:32 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...
130228 15:52:34 InnoDB: Waiting for the background threads to start
130228 15:52:35 InnoDB: 1.1.8 started; log sequence number 3496542
130228 15:52:35 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
130228 15:52:35 [Note] - '0.0.0.0' resolves to '0.0.0.0';
130228 15:52:35 [Note] Server socket created on IP: '0.0.0.0'.
130228 15:52:41 [Note] Plugin 'FEDERATED' is disabled.
130228 15:52:41 InnoDB: The InnoDB memory heap is disabled
130228 15:52:41 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130228 15:52:41 InnoDB: Compressed tables use zlib 1.2.3
130228 15:52:41 InnoDB: Initializing buffer pool, size = 16.0M
130228 15:52:41 InnoDB: Completed initialization of buffer pool
130228 15:52:41 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130228 15:52:41 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...
130228 15:52:42 InnoDB: Waiting for the background threads to start
130228 15:52:43 InnoDB: 1.1.8 started; log sequence number 3496542
130228 15:52:43 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
130228 15:52:43 [Note] - '0.0.0.0' resolves to '0.0.0.0';
130228 15:52:43 [Note] Server socket created on IP: '0.0.0.0'.
130228 15:52:55 [Note] Plugin 'FEDERATED' is disabled.
130228 15:52:55 InnoDB: The InnoDB memory heap is disabled
130228 15:52:55 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130228 15:52:55 InnoDB: Compressed tables use zlib 1.2.3
130228 15:52:55 InnoDB: Initializing buffer pool, size = 16.0M
130228 15:52:55 InnoDB: Completed initialization of buffer pool
130228 15:52:55 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130228 15:52:55 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...
130228 15:52:57 InnoDB: Waiting for the background threads to start
130228 15:52:58 InnoDB: 1.1.8 started; log sequence number 3496542
130228 15:52:58 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
130228 15:52:58 [Note] - '0.0.0.0' resolves to '0.0.0.0';
130228 15:52:58 [Note] Server socket created on IP: '0.0.0.0'.
130228 15:53:09 [Note] Plugin 'FEDERATED' is disabled.
130228 15:53:09 InnoDB: The InnoDB memory heap is disabled
130228 15:53:09 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130228 15:53:09 InnoDB: Compressed tables use zlib 1.2.3
130228 15:53:09 InnoDB: Initializing buffer pool, size = 16.0M
130228 15:53:09 InnoDB: Completed initialization of buffer pool
130228 15:53:09 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130228 15:53:09 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...
130228 15:53:10 InnoDB: Waiting for the background threads to start
130228 15:53:11 InnoDB: 1.1.8 started; log sequence number 3496542
130228 15:53:11 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
130228 15:53:11 [Note] - '0.0.0.0' resolves to '0.0.0.0';
130228 15:53:11 [Note] Server socket created on IP: '0.0.0.0'.

So I don't know what to do and today I was going to backup my databases as I have users details etc on them and I thought it would be easy, just export them and done and now I have this error and I need it back online ASAP!

Thanks for any help in advance

Re: MYSQL keeps crashing

PostPosted: 01. March 2013 14:51
by JonB
Is the server actually running a script/application when it crashes, or does it crash on startup.??/

Re: MYSQL keeps crashing

PostPosted: 01. March 2013 16:47
by jsrip2012
Yes Tomcat starts automatically as I have sysaid helpdesk running on it so that auto starts, and apache is also running

Re: MYSQL keeps crashing

PostPosted: 01. March 2013 17:05
by JonB
I'm betting your problem is really a code crash.

Re: MYSQL keeps crashing

PostPosted: 01. March 2013 17:12
by jsrip2012
How would I fix this?

Re: MYSQL keeps crashing

PostPosted: 01. March 2013 17:42
by JonB
For starters, I would look to the developers of the package you are running.

A method for testing if there is a MySQL problem would be to install something like Wordpress (temporarily) and make sure it runs reliably. If it (wordpress) does run right, 90% chance the app is causing the crash. I would also look at the my.ini/my.cnf recommendations for the package. You could be hitting memory allocation issues, etc.

Good Luck

Re: MYSQL keeps crashing

PostPosted: 01. March 2013 18:16
by jsrip2012
Well I can't really as the server crashes on startup, I press on Apache and it starts, tomcat auto starts and then when I click on MySQL it stays open for 3 seconds then comes up with an error

Re: MYSQL keeps crashing

PostPosted: 01. March 2013 19:55
by JonB
Disable this:

Yes Tomcat starts automatically as I have sysaid helpdesk running on it so that auto starts

Re: MYSQL keeps crashing

PostPosted: 03. March 2013 03:23
by jsrip2012
Disabled it and still no luck

However I have now got it working by installing MySQL separately by downloading the community edition and it works

thanks for all your help