Search found 7287 matches: mysql can't start

Searched query: +mysql +can't +start

Return to advanced search

Re: Apache wont start

I'm having a similar problem. Apache wasn't working, so I tried turning off all of my firewalls and antivirus. Still didn't work. Then I tried changing the port from 80 to 8080, as an online tutorial suggested this. It still doesn't work:

9:08:57 PM [main] Initializing Control Panel
9:08:57 PM [main] Windows Version: Windows 8 Pro 64-bit
9:08:57 PM [main] XAMPP Version: 1.8.2
9:08:57 PM [main] Control Panel Version: 3.2.1 [ Compiled: May 7th 2013 ]
9:08:57 PM [main] Running with Administrator rights - good!
9:08:57 PM [main] XAMPP Installation Directory: "c:\xampp\"
9:08:57 PM [main] Checking for prerequisites
9:08:58 PM [main] All prerequisites found
9:08:58 PM [main] Initializing Modules
9:08:58 PM [Apache] Problem detected!
9:08:58 PM [Apache] Port 8080 in use by "Unable to open process" with PID 4!
9:08:58 PM [Apache] Apache WILL NOT start without the configured ports free!
9:08:58 PM [Apache] You need to uninstall/disable/reconfigure the blocking application
9:08:58 PM [Apache] or reconfigure Apache and the Control Panel to listen on a different port
9:08:58 PM [mysql] XAMPP MySQL is already running on port 3306
9:08:58 PM [Tomcat] Problem detected!
9:08:58 PM [Tomcat] Port 8080 in use by "Unable to open process"!
9:08:58 PM [Tomcat] Tomcat WILL NOT start without the configured ports free!
9:08:58 PM [Tomcat] You need to uninstall/disable/reconfigure the blocking application
9:08:58 PM [Tomcat] or reconfigure Tomcat and the Control Panel to listen on a different port
9:08:58 PM [main] Starting Check-Timer
9:08:58 PM [main] Control Panel Ready

I will post my error file as soon as I figure out how to find it. Currently, my log files don't seem to have any content. When I click "log" it just says "do you want to create a blank document?" I'm running Windows 8.1

Thanks for any help.
by bjm70e
15. January 2014 04:10
 
Forum: XAMPP for Windows
Topic: Apache wont start
Replies: 8
Views: 6869

Xammp mysql port blocked

I got xampp and created a MySQL. I had to delete the xampp folder. Now that I regot it when I try to start MySQL it says that the port 3306 is blocked. Can anyone help me unblock this port? Thanks!
by mrpotsticker
14. January 2014 22:21
 
Forum: XAMPP for Windows
Topic: Xammp mysql port blocked
Replies: 2
Views: 1378

Apache HTTP Server funktioniert nicht mehr

Hallo,
immer wenn ich den Adminbereich des Webshops localhost/oxid/admin starten will bekomme ich die Fehlermeldung "Apache HTTP Server funktioniert nicht mehr" -"Programm schließen". Das passiert nur beim Aufruf dieser Seite. Ist plötzlich aufgetreten, d.h. vorher konnte ich die Seite immer problemlos aufrufen.

XAMPP Control Fenster:
21:59:39 [main] Starting Check-Timer
21:59:39 [main] Control Panel Ready
21:59:44 [Apache] Attempting to stop Apache (PID: 4832)
21:59:44 [Apache] Attempting to stop Apache (PID: 828)
21:59:44 [Apache] Status change detected: stopped
21:59:46 [Apache] Attempting to start Apache app...
21:59:46 [Apache] Status change detected: running
21:59:50 [mysql] Attempting to start MySQL app...
21:59:50 [mysql] Status change detected: running

Apache HTTP Error LOG:
[Sun Jan 12 22:05:06.710904 2014] [mpm_winnt:notice] [pid 6748:tid 260] AH00428: Parent: child process 1820 exited with status 3221225725 -- Restarting.
[Sun Jan 12 22:05:07.756106 2014] [ssl:warn] [pid 6748:tid 260] AH01909: RSA certificate configured for www.example.com:443 does NOT include an ID which matches the server name
[Sun Jan 12 22:05:07.880906 2014] [mpm_winnt:notice] [pid 6748:tid 260] AH00455: Apache/2.4.4 (Win32) OpenSSL/0.9.8y PHP/5.4.19 configured -- resuming normal operations
[Sun Jan 12 22:05:07.880906 2014] [mpm_winnt:notice] [pid 6748:tid 260] AH00456: Server built: Feb 23 2013 13:07:34
[Sun Jan 12 22:05:07.880906 2014] [core:notice] [pid 6748:tid 260] AH00094: Command line: 'c:\\users\\koch001c\\software\\xampp\\apache\\bin\\httpd.exe -d C:/Users/koch001c/Software/xampp/apache'
[Sun Jan 12 22:05:07.896506 2014] [mpm_winnt:notice] [pid 6748:tid 260] AH00418: Parent: Created child process 6376
[Sun Jan 12 22:05:08.910508 2014] [ssl:warn] [pid 6376:tid 272] AH01909: RSA certificate configured for www.example.com:443 does NOT include an ID which matches the server name
[Sun Jan 12 22:05:09.955710 2014] [ssl:warn] [pid 6376:tid 272] AH01909: RSA certificate configured for www.example.com:443 does NOT include an ID which matches the server name
[Sun Jan 12 22:05:10.111710 2014] [mpm_winnt:notice] [pid 6376:tid 272] AH00354: Child: Starting 150 worker threads.

Setup_XAMPP.bat:
"Sorry... nothing to do".

Hat jemand eine Idee was der Fehler sein könnte?
Danke & Gruß,
Chris
by chris1941
12. January 2014 22:08
 
Forum: XAMPP für Windows
Topic: Apache HTTP Server funktioniert nicht mehr
Replies: 2
Views: 2068

MySql will not start

Hej!

I installed XAMPP yesterday (Control Panel 3.2.1), but I can not get MySql started. Apache is running fine. I installed XAMPP on my C drive in Windows 7. I got the following error log

140111 18:51:52 [Note] Plugin 'FEDERATED' is disabled.
140111 18:51:52 InnoDB: The InnoDB memory heap is disabled
140111 18:51:52 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140111 18:51:52 InnoDB: Compressed tables use zlib 1.2.3
140111 18:51:52 InnoDB: Initializing buffer pool, size = 16.0M
140111 18:51:52 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist:
InnoDB: a new database to be created!
140111 18:51:52 InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
140111 18:51:52 InnoDB: Log file C:\xampp\mysql\data\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
140111 18:51:53 InnoDB: Log file C:\xampp\mysql\data\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
140111 18:51:54 InnoDB: Waiting for the background threads to start
140111 18:51:55 InnoDB: 5.5.34 started; log sequence number 0
140111 18:51:55 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140111 18:51:55 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140111 18:51:55 [Note] Server socket created on IP: '0.0.0.0'.
140111 18:51:55 [ERROR] Event Scheduler: Failed to open table mysql.event
140111 18:51:55 [ERROR] Event Scheduler: Error while loading from disk.
140111 18:51:55 [Note] Event Scheduler: Purging the queue. 0 events
140111 18:51:55 [ERROR] Aborting

140111 18:51:55 InnoDB: Starting shutdown...
140111 18:51:55 InnoDB: Shutdown completed; log sequence number 1595675
140111 18:51:55 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete


Can anyone help?
by Ingolopolos
12. January 2014 12:30
 
Forum: XAMPP for Windows
Topic: MySql will not start
Replies: 0
Views: 1374

Re: Password Help for MySql with Xampp

nstreet wrote:I try to follow the book:
>C:\mysql\bin\mysql -u root -p


Without any knowledge about MySQL rights this is quite dangerous.

nstreet wrote:I then get an area to change the password.


What do you mean by "area"?? You simply get a prompt of the MySQL Interpreter, nothing else.

nstreet wrote:When I create a password I get: Error 1045 (2800) Access Denied for user 'root@localhost' (using password: yes)


No, no, not so quick.

a) What did you enter precisely to the MySQL prompt (in order to create a passwort)?

b) When (exactly) did you receive that error message?


Maybe you already destroyed your Xampp installation with these few steps, if you do not remember by 100% what you entered there, you ruined your root account of MySQL.

nstreet wrote:1) Why a password needs to be set up?


There is no need, who tells you so? Ask him! Xampp comes without password and it is ready to run out of the box. Passwords are needed for multiuser environments and or online environments to prevent other people to overtake the control of your server. But this is not a threat on a private single user PC.

nstreet wrote:2) How to actually, basically, set up the password.


Obviously, when you say "the password", you actually mean the passwort of the User "root" from the MySQL Installation. Beware: MySQL Users are not the same users as windows users! This is a completely different context.

The one and only administration tool for you (running Xampp) is "PhpMyAdmin", which is part of the Xampp Installation and there is a link in the Xampp Menu to run it in your browser. DO NOT RUN MYSQL Interpreter natively without any knowledge of what you are doing there!

nstreet wrote:Some explanation suggest I go to a web browser and in the address bar search localhost.


Ouch!! That means that you either did not install Xampp correctly or did not start Apache. You have to start Apache (and MySQL) in the Xampp Control Dialog.

It seems, you have no idea what Xampp does and what it is good for. You should not go for any passwords (this is for advanced users only), as long as you have no idea about using Xampp.
by Nobbie
10. January 2014 11:15
 
Forum: XAMPP for Windows
Topic: Password Help for MySql with Xampp
Replies: 4
Views: 3493

Re: MySQL shutdown unexpectyedly

Deleted my previous post in favor of this one: I realized there's a debug mode.

6:25:55 PM [main] Initializing Control Panel
6:25:55 PM [main] Windows Version: Windows 7 Home Premium SP1 64-bit
6:25:55 PM [main] XAMPP Version: 1.8.3
6:25:55 PM [main] Control Panel Version: 3.2.1 [ Compiled: May 7th 2013 ]
6:25:55 PM [main] Running with Administrator rights - good!
6:25:55 PM [main] XAMPP Installation Directory: "c:\xampp\"
6:25:55 PM [main] Checking for prerequisites
6:25:55 PM [main] All prerequisites found
6:25:55 PM [main] Initializing Modules
6:25:55 PM [Apache] Initializing module...
6:25:55 PM [Apache] Checking for module existence...
6:25:55 PM [Apache] Checking for required tools...
6:25:55 PM [Apache] Checking for service (name="Apache2.4"): Service installed
6:25:55 PM [Apache] Service Path: "C:\xampp\apache\bin\httpd.exe" -k runservice
6:25:55 PM [Apache] Checking default ports...
6:25:55 PM [mysql] Initializing module...
6:25:55 PM [mysql] Checking for module existence...
6:25:55 PM [mysql] Checking for required tools...
6:25:55 PM [mysql] Checking for service (name="mysql"): Service installed
6:25:55 PM [mysql] Service Path: C:\xampp\mysql\bin\mysqld.exe --defaults-file=c:\xampp\mysql\bin\my.ini mysql
6:25:55 PM [mysql] Checking default ports...
6:25:55 PM [main] The FileZilla module is disabled
6:25:55 PM [main] The Mercury module is disabled
6:25:55 PM [main] The Tomcat module is disabled
6:25:55 PM [main] Enabling autostart for module "Apache"
6:25:55 PM [main] Enabling autostart for module "MySQL"
6:25:55 PM [main] Starting Check-Timer
6:25:55 PM [main] Control Panel Ready
6:25:56 PM [Apache] Autostart active: starting...
6:25:56 PM [Apache] Checking default ports...
6:25:56 PM [Apache] Attempting to start Apache service...
6:25:56 PM [Apache] Executing "net start "Apache2.4""
6:25:56 PM [Apache] Status change detected: running
6:25:56 PM [mysql] Autostart active: starting...
6:25:56 PM [mysql] Checking default ports...
6:25:56 PM [mysql] Attempting to start MySQL service...
6:25:56 PM [mysql] Executing "net start "mysql""
6:25:57 PM [mysql] Status change detected: running
6:26:02 PM [mysql] Status change detected: stopped
6:26:02 PM [mysql] Error: MySQL shutdown unexpectedly.
6:26:02 PM [mysql] This may be due to a blocked port, missing dependencies,
6:26:02 PM [mysql] improper privileges, a crash, or a shutdown by another method.
6:26:02 PM [mysql] Press the Logs button to view error logs and check
6:26:02 PM [mysql] the Windows Event Viewer for more clues
6:26:02 PM [mysql] If you need more help, copy and post this
6:26:02 PM [mysql] entire log window on the forums
6:26:04 PM [mysql] Return code: 0
6:26:04 PM [Apache] Return code: 0
by starburstq
08. January 2014 02:26
 
Forum: XAMPP for Windows
Topic: MySQL shutdown unexpectyedly
Replies: 3
Views: 3310

Re: MySQL shutdown unexpectyedly

starburstq wrote:...
Attempting to start MySQL service...
5:55:47 PM [mysql] Status change detected: running
5:55:52 PM [mysql] Status change detected: stopped
5:55:52 PM [mysql] Error: MySQL shutdown unexpectedly.
5:55:52 PM [mysql] This may be due to a blocked port, missing dependencies,
5:55:52 PM [mysql] improper privileges, a crash, or a shutdown by another method.
5:55:52 PM [mysql] Press the Logs button to view error logs and check
5:55:52 PM [mysql] the Windows Event Viewer for more clues
5:55:52 PM [mysql] If you need more help, copy and post this
5:55:52 PM [mysql] entire log window on the forums
...

There's more in that window than this. If you don't see any specific error message, run the control panel with admin rights, and attempt to start. Then copy/paste entire log window (not just the snippet).
by JJ_Tagy
08. January 2014 02:06
 
Forum: XAMPP for Windows
Topic: MySQL shutdown unexpectyedly
Replies: 3
Views: 3310

MySQL shutdown unexpectyedly

Just installed XAMPP Control Panel. Got Apache running, but MySQL doesn't seem to want to play nice. Any help would be appreciated.

Here's the output:

Attempting to start MySQL service...
5:55:47 PM [mysql] Status change detected: running
5:55:52 PM [mysql] Status change detected: stopped
5:55:52 PM [mysql] Error: MySQL shutdown unexpectedly.
5:55:52 PM [mysql] This may be due to a blocked port, missing dependencies,
5:55:52 PM [mysql] improper privileges, a crash, or a shutdown by another method.
5:55:52 PM [mysql] Press the Logs button to view error logs and check
5:55:52 PM [mysql] the Windows Event Viewer for more clues
5:55:52 PM [mysql] If you need more help, copy and post this
5:55:52 PM [mysql] entire log window on the forums

And here's the log:

2013-12-24 16:53:59 2884 [Note] Plugin 'FEDERATED' is disabled.
2013-12-24 16:54:00 b5c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-12-24 16:54:00 2884 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-24 16:54:00 2884 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-24 16:54:00 2884 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-24 16:54:00 2884 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-24 16:54:00 2884 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-24 16:54:00 2884 [Note] InnoDB: Completed initialization of buffer pool
2013-12-24 16:54:00 2884 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-24 16:54:01 2884 [Warning] InnoDB: Resizing redo log from 2*3072 to 2*320 pages, LSN=1625987
2013-12-24 16:54:01 2884 [Warning] InnoDB: Starting to delete and rewrite log files.
2013-12-24 16:54:01 2884 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2013-12-24 16:54:01 2884 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2013-12-24 16:54:01 2884 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2013-12-24 16:54:01 2884 [Warning] InnoDB: New log files created, LSN=1625987
2013-12-24 16:54:01 2884 [Note] InnoDB: 128 rollback segment(s) are active.
2013-12-24 16:54:01 2884 [Note] InnoDB: Waiting for purge to start
2013-12-24 16:54:01 2884 [Note] InnoDB: 5.6.14 started; log sequence number 1625987
2013-12-24 16:54:02 2884 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: a9f27fcc-6cf6-11e3-8964-842b2b9bacef.
2013-12-24 16:54:02 2884 [Note] Server hostname (bind-address): '*'; port: 3306
2013-12-24 16:54:02 2884 [Note] IPv6 is available.
2013-12-24 16:54:02 2884 [Note] - '::' resolves to '::';
2013-12-24 16:54:02 2884 [Note] Server socket created on IP: '::'.
2013-12-24 16:54:02 2884 [Note] Event Scheduler: Loaded 0 events
2013-12-24 16:54:02 2884 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.14' socket: '' port: 3306 MySQL Community Server (GPL)
2013-12-24 17:59:36 2884 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown

2013-12-24 17:59:36 2884 [Note] Giving 0 client threads a chance to die gracefully
2013-12-24 17:59:36 2884 [Note] Event Scheduler: Purging the queue. 0 events
2013-12-24 17:59:36 2884 [Note] Shutting down slave threads
2013-12-24 17:59:36 2884 [Note] Forcefully disconnecting 0 remaining clients
2013-12-24 17:59:36 2884 [Note] Binlog end
2013-12-24 17:59:36 2884 [Note] Shutting down plugin 'partition'
2013-12-24 17:59:36 2884 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2013-12-24 17:59:36 2884 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2013-12-24 17:59:36 2884 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2013-12-24 17:59:36 2884 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2013-12-24 17:59:36 2884 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
...
by starburstq
08. January 2014 02:01
 
Forum: XAMPP for Windows
Topic: MySQL shutdown unexpectyedly
Replies: 3
Views: 3310

Re: Probleme mySQL Win7

Altrea wrote:MySQL verwendet seit Version 5.5 (genauer gesagt irgendwo seit der nie als Stable veröffentlichten Version 5.4.X) InnoDB as Default Strorage Engine. Das war einer der ersten Maßnahmen, die Oracle nach der Übernahme von Sun Microsystems vorgenommen hat.


Ah - da war ich gestern nicht hartnäckig genug, selbstverständlich habe ich erst mal nachgeschaut und bin von Google (erster Treffer) auf dev.mysql.com geleitet worden, dort aber auf die Refpage von 5.1 - und da steht natürlich immer noch MyISAM als Default.

Altrea wrote:Das hat damals sogar zu einem mehr oder weniger großen Aufschrei in der Entwicklerszene geführt, weil InnoDB zu diesem Zeitpunkt noch weit davon entfernt war besonders performant zu sein (Dies hat sich zum Glück in weiten Teilen mitlerweile verbessert, was auch nicht zuletzt auf die Arbeit der MariaDB Programmierer zurückgeht).

Die offizielle Begründung für den Wechsel kannst du hier nachlesen.
http://dev.mysql.com/doc/refman/5.5/en/ ... lt-se.html


Dass das Geschrei gegeben hat, kann ich mir lebhaft vorstellen. Ich habe jetzt die neuere Doku gelesen, die hanebüchene Begründung, man habe "festgestellt", dass die meisten(!) Anwender sowieso auf InnoDB umschwenken, halte ich für frei erfunden. Ich weiß nicht, was in Wirklichkeit die Hintergründe sind, aber ich kenne wirklich viele MySQL Installationen (fast alle Foren laufen ja darauf), es gibt kaum InnoDB Installationen. Da InnoDB (wie Du ja auch schreibst und die Erfahrung habe ich auch gemacht) früher teilweise elend lahm war, war das keine Option. Sowieso haben sich viele Anwender mangels Kenntnis überhaupt darum geschert, das ist doch wie hier bei Xampp, man nimmt was man kriegt. Fertig.

Du siehst es ja selbst hier: seit dem wir mit InnoDB ausliefern, ist jede zweite Fehlermeldung ein InnoDB Problem - zum Kotzen ist das! Ich habe da keinen Bock mehr drauf, ich werde die Fragen nicht mehr beantworten.

Altrea wrote:Ein Umkonfigurieren der default-storage-engine würde dieses Problem hier leider auch nicht verhindern, da die betreffenden InnoDB Dateien dennoch beim ersten Start nach XAMPP Installation angelegt werden müssten und man in dasselbe Problem laufen würde. Man müsste InnoDB zusätzlich über den Schalter skip-innodb komplett deaktivieren


Ja - warum nicht. Bzw. wenn man schon auf der Befehlszeile für mysqld.exe die Option für die Default Storage Engine angibt, dann müßte mysql doch völlig ohne InnoDB auskommen?! Das wäre durchaus sinnvoll. Xampp will eine unkomplizierte Entwicklungsumgebung darstellen, da brauche ich keine komplexe Transaktionsunterstützung. Ist es nicht sogar so, dass der FULLTEXT Index nur von MyISAM unterstützt (ich habe mich jahrelang nicht mehr mit beschäftigt, bin mir aber ziemlich sicher, dass das ein reines MyISAM Feature war/ist)? Das benutzen viele namhafte Forenscripts.

Das könnte übrigens auch erklären, warum typo3 so wahnsinnig lahm ist - das liegt mit ziemlicher Sicherheit auch an InnoDB.

Ich finde schon, dass das absolute eine Überlegung wert wäre, Xampp so vorzukonfigurieren, dass InnoDB nicht Default ist. Ich werde jedenfalls keine MySQL-Anfragen mehr beantworten, wenn erkennbar ist, dass es wieder einmal am InnoDB Umfeld liegt. Das nervt nur noch.
by Nobbie
07. January 2014 11:19
 
Forum: XAMPP für Windows
Topic: Probleme mySQL Win7
Replies: 16
Views: 9179

Re: Xampp lite, Mysql wont start on 3TB xHDD

Hi Sally,

Maybe one of these Workaround will work:
viewtopic.php?f=16&t=67577#p232773

best wishes,
Altrea
by Altrea
07. January 2014 08:32
 
Forum: XAMPP for Windows
Topic: Xampp lite, Mysql wont start on 3TB xHDD
Replies: 1
Views: 1923

Re: Probleme mySQL Win7

Nobbie wrote:a) wo wird im Xampp Umfeld die Default Storage Engine auf "InnoDB" gesetzt? Die Default Einstellung (wenn nichts gesetzt ist), lautet MyISAM. Da aber InnoDB gesetzt wird, muss das irgendwo explizit geschehen - ich sehe es aber nicht. In my.ini steht gar nichts, ich finde es auch an keiner anderen Stelle.

b) wieso wird es (und seit wann? das war nicht immer so) auf "InnoDB" gesetzt?

MySQL verwendet seit Version 5.5 (genauer gesagt irgendwo seit der nie als Stable veröffentlichten Version 5.4.X) InnoDB as Default Strorage Engine. Das war einer der ersten Maßnahmen, die Oracle nach der Übernahme von Sun Microsystems vorgenommen hat.

Das hat damals sogar zu einem mehr oder weniger großen Aufschrei in der Entwicklerszene geführt, weil InnoDB zu diesem Zeitpunkt noch weit davon entfernt war besonders performant zu sein (Dies hat sich zum Glück in weiten Teilen mitlerweile verbessert, was auch nicht zuletzt auf die Arbeit der MariaDB Programmierer zurückgeht).

Die offizielle Begründung für den Wechsel kannst du hier nachlesen.
http://dev.mysql.com/doc/refman/5.5/en/ ... lt-se.html

XAMPP hat diese Voreinstellung schlichtweg mitübernommen.
Nobbie wrote:c) das ist aus meiner Sicht eine schwere Fehlentscheidung. InnoDB ist ein Datenbanktreiber für hochproduktive Multiuser-Umgebungen mit Transaktionen und Rollback - also das diametrale Gegenteil dessen, was Xampp eigentlich ist. Xampp ist eine Single User Development Plattform. Einen skurrileren Widerspruch kann man kaum konstruieren.

Ganz so negativ wie du sehe ich InnoDB dann doch nicht, aber es ist schon richtig, es wirkt irgendwie wie mit Kanonen auf Spatzen geschossen :lol:

Ein Umkonfigurieren der default-storage-engine würde dieses Problem hier leider auch nicht verhindern, da die betreffenden InnoDB Dateien dennoch beim ersten Start nach XAMPP Installation angelegt werden müssten und man in dasselbe Problem laufen würde. Man müsste InnoDB zusätzlich über den Schalter skip-innodb komplett deaktivieren, das müsste in diesem Fall funktionieren. XAMPP selbst wird mit keiner einzigen InnoDB Tabelle ausgeliefert. Das wäre aber eine sehr radikale Vorgehensweise die ich als generelle Empfehlung zur Problemumgehung nicht geben wollen würde.

Interessant an der ganzen Problematik zu wissen wäre, ob MySQL zwar berechtigt ist die Dateien initial anzulegen, aber nicht mit Nullen aufzufüllen oder das Problem vorher schon zu suchen ist (also existieren die Dateien indata1, ib_logfile0,, ib_logfile1 in \xampp\mysql\data\? Wenn ja welche Größe haben die Dateien?).
Bei einer ganz frischen XAMPP Installation existieren die InnoDB Dateien noch garnicht und werden erst beim ersten Starten erzeugt. Die mysql_error.log Datei müsste also beim allerersten Start Einträge wie diese hier für mehrere Dateien enthalten:
Code: Select all
InnoDB: The first specified data file H:\xampp\mysql\data\ibdata1 did not exist:
InnoDB: a new database to be created!
140107  6:19:00  InnoDB: Setting file H:\xampp\mysql\data\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...

Ich bin auch kein Experte was diese Schreibzugriffe betrifft. Vielleicht werden dort irgendwelche low-level Methoden verwendet, die durch Sicherheitseinrichtungen oder Treiber schlicht unterbunden werden oder nicht zur Verfügung stehen.
by Altrea
07. January 2014 04:41
 
Forum: XAMPP für Windows
Topic: Probleme mySQL Win7
Replies: 16
Views: 9179

Re: [BUGS] XAMPP 1.8.2-3 & 1.8.3-2 issues

Bug Report
mysql_error.log wrote:{YYYY-mm-dd HH:ii:ss} [Note] Plugin 'FEDERATED' is disabled.
{YYYY-mm-dd HH:ii:ss} InnoDB: The InnoDB memory heap is disabled
{YYYY-mm-dd HH:ii:ss} InnoDB: Mutexes and rw_locks use Windows interlocked functions
{YYYY-mm-dd HH:ii:ss} InnoDB: Compressed tables use zlib 1.2.3
{YYYY-mm-dd HH:ii:ss} InnoDB: Initializing buffer pool, size = 16.0M
{YYYY-mm-dd HH:ii:ss} InnoDB: Completed initialization of buffer pool
InnoDB: Error: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1
{YYYY-mm-dd HH:ii:ss} InnoDB: Could not open or create data files.
{YYYY-mm-dd HH:ii:ss} InnoDB: If you tried to add new data files, and it failed here,
{YYYY-mm-dd HH:ii:ss} InnoDB: you should now edit innodb_data_file_path in my.cnf back
{YYYY-mm-dd HH:ii:ss} InnoDB: to what it was, and remove the new ibdata files InnoDB created
{YYYY-mm-dd HH:ii:ss} InnoDB: in this failed attempt. InnoDB only wrote those files full of
{YYYY-mm-dd HH:ii:ss} InnoDB: zeros, but did not yet use them in any way. But be careful: do not
{YYYY-mm-dd HH:ii:ss} InnoDB: remove old data files which contain your precious data!
{YYYY-mm-dd HH:ii:ss} [ERROR] Plugin 'InnoDB' init function returned error.
{YYYY-mm-dd HH:ii:ss} [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
{YYYY-mm-dd HH:ii:ss} [ERROR] Unknown/unsupported storage engine: InnoDB
{YYYY-mm-dd HH:ii:ss} [ERROR] Aborting
{YYYY-mm-dd HH:ii:ss} [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete


Reproducible Testcase
None yet.
Possible issue related parameters: (external) harddiks >2TB, missing write permissions, third party security software or windows security functions

Affected XAMPP versions
All XAMPP versions!?
Issue is reported for XAMPP 1.8.2-X and XAMPP 1.8.3-X full as well as lite portable versions
search.php?keywords=%22space+header+page%22&terms=all&author=&sc=1&sf=all&sr=posts&sk=t&sd=d&st=0&ch=300&t=0&submit=Suche

Solutions / Workarounds (unconfirmed)

Workaround 1: Adding setting innodb_flush_method=normal to my.ini
  • Open with plain text editor \xampp\mysql\bin\my.ini
  • at the end of the innodb_ parameters inside the [mysqld] block in add
    Code: Select all
    innodb_flush_method=normal
  • save the file

Workaround 2: Changing default-storage-engine to MyISAM and disabling InnoDB completely
  • Open with plain text editor \xampp\mysql\bin\my.ini
  • search the following line
    Code: Select all
    [mysqld]
  • after that line add the following line
    Code: Select all
    default-storage-engine=MyISAM
  • search the following line
    Code: Select all
    #skip-innodb
  • change that line to
    Code: Select all
    skip-innodb
  • save the file

References
by Altrea
06. January 2014 18:42
 
Forum: XAMPP for Windows
Topic: [BUGS] XAMPP 1.8.2-3 & 1.8.3-2 issues
Replies: 4
Views: 15532

Re: Probleme mySQL Win7

Nur um ein Festplatten Block Größen Problem auszuschließen, bitte versuche einmal folgenden fix:

  • im Editor öffne die Datei \xampp\mysql\bin\my.ini
  • Suche die ganzen innodb_ Definitionen im [mysqld] Block
  • Am Ende dieser ganzen innodb Anweisungen füge folgende Zeile hinzu
    Code: Select all
    innodb_flush_method=normal
  • Speichere die Datei
  • versuche MySQL zu starten

Die offizielle MySQL Dokumentation über diesen Parameter schreibt zwar, dass er auf Windows Systemen keine Auswirkung hat da er einen fixen, nicht änderbaren Wert hat.
Mehrere Erfahrungswerte anderer lassen aber etwas anderes vermuten:
http://superuser.com/questions/653953/c ... rnal-drive
http://bugs.mysql.com/bug.php?id=28913
by Altrea
06. January 2014 17:05
 
Forum: XAMPP für Windows
Topic: Probleme mySQL Win7
Replies: 16
Views: 9179

Re: Probleme mySQL Win7

Vielen Dank, daß Ihr Euch mit meinem Problem beschäftigt!

Hier erst mal die Datei "my.ini"
    # Example MySQL config file for small systems.
    #
    # This is for a system with little memory (<= 64M) where MySQL is only used
    # from time to time and it's important that the mysqld daemon
    # doesn't use much resources.
    #
    # You can copy this file to
    # H:/xampp/mysql/bin/my.cnf to set global options,
    # mysql-data-dir/my.cnf to set server-specific options (in this
    # installation this directory is H:/xampp/mysql/data) or
    # ~/.my.cnf to set user-specific options.
    #
    # In this file, you can use all long options that a program supports.
    # If you want to know which options a program supports, run the program
    # with the "--help" option.

    # The following options will be passed to all MySQL clients
    [client]
    # password = your_password
    port = 3306
    socket = "H:/xampp/mysql/mysql.sock"


    # Here follows entries for some specific programs

    # The MySQL server
    [mysqld]
    port= 3306
    socket = "H:/xampp/mysql/mysql.sock"
    basedir = "H:/xampp/mysql"
    tmpdir = "H:/xampp/tmp"
    datadir = "H:/xampp/mysql/data"
    pid_file = "mysql.pid"
    # enable-named-pipe
    key_buffer = 16M
    max_allowed_packet = 1M
    sort_buffer_size = 512K
    net_buffer_length = 8K
    read_buffer_size = 256K
    read_rnd_buffer_size = 512K
    myisam_sort_buffer_size = 8M
    log_error = "mysql_error.log"

    # Change here for bind listening
    # bind-address="127.0.0.1"
    # bind-address = ::1 # for ipv6

    # Where do all the plugins live
    plugin_dir = "H:/xampp/mysql/lib/plugin/"

    # Don't listen on a TCP/IP port at all. This can be a security enhancement,
    # if all processes that need to connect to mysqld run on the same host.
    # All interaction with mysqld must be made via Unix sockets or named pipes.
    # Note that using this option without enabling named pipes on Windows
    # (via the "enable-named-pipe" option) will render mysqld useless!
    #
    # commented in by lampp security
    #skip-networking
    skip-federated

    # Replication Master Server (default)
    # binary logging is required for replication
    # log-bin deactivated by default since XAMPP 1.4.11
    #log-bin=mysql-bin

    # required unique id between 1 and 2^32 - 1
    # defaults to 1 if master-host is not set
    # but will not function as a master if omitted
    server-id = 1

    # Replication Slave (comment out master section to use this)
    #
    # To configure this host as a replication slave, you can choose between
    # two methods :
    #
    # 1) Use the CHANGE MASTER TO command (fully described in our manual) -
    # the syntax is:
    #
    # CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
    # MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
    #
    # where you replace <host>, <user>, <password> by quoted strings and
    # <port> by the master's port number (3306 by default).
    #
    # Example:
    #
    # CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
    # MASTER_USER='joe', MASTER_PASSWORD='secret';
    #
    # OR
    #
    # 2) Set the variables below. However, in case you choose this method, then
    # start replication for the first time (even unsuccessfully, for example
    # if you mistyped the password in master-password and the slave fails to
    # connect), the slave will create a master.info file, and any later
    # change in this file to the variables' values below will be ignored and
    # overridden by the content of the master.info file, unless you shutdown
    # the slave server, delete master.info and restart the slaver server.
    # For that reason, you may want to leave the lines below untouched
    # (commented) and instead use CHANGE MASTER TO (see above)
    #
    # required unique id between 2 and 2^32 - 1
    # (and different from the master)
    # defaults to 2 if master-host is set
    # but will not function as a slave if omitted
    #server-id = 2
    #
    # The replication master for this slave - required
    #master-host = <hostname>
    #
    # The username the slave will use for authentication when connecting
    # to the master - required
    #master-user = <username>
    #
    # The password the slave will authenticate with when connecting to
    # the master - required
    #master-password = <password>
    #
    # The port the master is listening on.
    # optional - defaults to 3306
    #master-port = <port>
    #
    # binary logging - not required for slaves, but recommended
    #log-bin=mysql-bin


    # Point the following paths to different dedicated disks
    #tmpdir = "H:/xampp/tmp"
    #log-update = /path-to-dedicated-directory/hostname

    # Uncomment the following if you are using BDB tables
    #bdb_cache_size = 4M
    #bdb_max_lock = 10000

    # Comment the following if you are using InnoDB tables
    #skip-innodb
    innodb_data_home_dir = "H:/xampp/mysql/data"
    innodb_data_file_path = ibdata1:10M:autoextend
    innodb_log_group_home_dir = "H:/xampp/mysql/data"
    #innodb_log_arch_dir = "H:/xampp/mysql/data"
    ## You can set .._buffer_pool_size up to 50 - 80 %
    ## of RAM but beware of setting memory usage too high
    innodb_buffer_pool_size = 16M
    innodb_additional_mem_pool_size = 2M
    ## Set .._log_file_size to 25 % of buffer pool size
    innodb_log_file_size = 5M
    innodb_log_buffer_size = 8M
    innodb_flush_log_at_trx_commit = 1
    innodb_lock_wait_timeout = 50

    ## UTF 8 Settings
    #init-connect=\'SET NAMES utf8\'
    #collation_server=utf8_unicode_ci
    #character_set_server=utf8
    #skip-character-set-client-handshake
    #character_sets-dir="H:/xampp/mysql/share/charsets"

    [mysqldump]
    quick
    max_allowed_packet = 16M

    [mysql]
    no-auto-rehash
    # Remove the next comment character if you are not familiar with SQL
    #safe-updates

    [isamchk]
    key_buffer = 20M
    sort_buffer_size = 20M
    read_buffer = 2M
    write_buffer = 2M

    [myisamchk]
    key_buffer = 20M
    sort_buffer_size = 20M
    read_buffer = 2M
    write_buffer = 2M

    [mysqlhotcopy]
    interactive-timeout


Die Antwort zur Frage zum LW H:
An meinen McMini habe ich eine 3TB WD MyBook angeschlossen und die habe ich in mehrere Partitionen unterteilt, eine lautet also H: und hat eine Größe von 100 GB
Und auf H: habe ich einen Ordner (Xapp-Install) mit der downgeladenen Installationsdatei. Von dieser habe ich das Installationspaket gestartet und auf der gleichen Partition in den Pfad "Xampp" installieren lassen.

Die Installationsroutine läuft ohne Probleme ab und läßt dann das Control-Panel starten.
Hier habe ich probiert direkt zu starten, erst Apache, geht ohne Probleme, dann MySQL. Dabei wird dann im Control-Fenster nur gemeldet "Versuche MySql zu starten", aber mehr passiert nicht. Habe ich die Dienste angeklickt, dann kommt es zur gezeigten Fehlermeldung.

Zur Vervollständigung der Information möchte ich Euch noch mitteilen, daß ich schon probiert habe auf der McMini-eigenen Platte C: Xampp zu installieren. Es zeigte sich das gleiche Fehlerbild und ich wollte eigentlich auch die Resourcen dieser Festplatte schonen, deshalb hatte ich die Auslagerung auf H: gewählt!

Einen weiteren Versuch hatte ich mit der Installationsroutine für win32-1.7.3 unternommen, auch hier habe ich MySQL nicht starten können.

Um dem Problem mit eventuellen Schwierigkeiten zu Administrationsrechten aus dem Weg zu gehen, habe ich einen Tipp aus dem Netzt genutzt und über msconfig UAC abgeschaltet.

Ich hoffe, ich bin auf alle Eure gestellten Fragen eingegangen, zum Schluss noch die Frage von Nobbie, in Bezug auf meine Bemerkung zu meinen Englischkenntnissen. Es ist einfach so, daß ich mich bei englischen Texten nicht mehr auf der sicheren Seite fühle und bei der Interpretation von derartigen Log-Dateien, lieber auf Hilfe von Leuten vertrauen möchte, denen das weniger Schwierigkeiten macht.

Es wäre also sehr schön, wenn ich hier weiter auf Hilfe rechnen dürfte!

Bis dann und mit freundlichem Gruß

Pilot
by Pilot
06. January 2014 14:27
 
Forum: XAMPP für Windows
Topic: Probleme mySQL Win7
Replies: 16
Views: 9179

Re: Help Please, MySql error shutdown unexpectedly

as for the mysql_error.log file here's the content of that file.

2013-12-29 11:22:27 4224 [Note] Plugin 'FEDERATED' is disabled.
2013-12-29 11:22:27 12a0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-12-29 11:22:27 4224 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-29 11:22:27 4224 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-29 11:22:27 4224 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-29 11:22:27 4224 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-29 11:22:27 4224 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-29 11:22:27 4224 [Note] InnoDB: Completed initialization of buffer pool
2013-12-29 11:22:27 4224 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-29 11:22:27 4224 [Note] InnoDB: The log sequence numbers 1625987 and 1625987 in ibdata files do not match the log sequence number 4125032 in the ib_logfiles!
2013-12-29 11:22:27 4224 [Note] InnoDB: Database was not shutdown normally!
2013-12-29 11:22:27 4224 [Note] InnoDB: Starting crash recovery.
2013-12-29 11:22:27 4224 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-29 11:22:28 4224 [Note] InnoDB: Restoring possible half-written data pages
2013-12-29 11:22:28 4224 [Note] InnoDB: from the doublewrite buffer...
2013-12-29 11:22:30 4224 [Note] InnoDB: 128 rollback segment(s) are active.
2013-12-29 11:22:30 4224 [Note] InnoDB: Waiting for purge to start
2013-12-29 11:22:30 4224 [Note] InnoDB: 5.6.14 started; log sequence number 4125032
2013-12-29 11:22:30 4224 [Note] Server hostname (bind-address): '*'; port: 3306
2013-12-29 11:22:30 4224 [Note] IPv6 is available.
2013-12-29 11:22:30 4224 [Note] - '::' resolves to '::';
2013-12-29 11:22:30 4224 [Note] Server socket created on IP: '::'.
2013-12-29 11:22:31 4224 [Note] Event Scheduler: Loaded 0 events
2013-12-29 11:22:31 4224 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.14' socket: '' port: 3306 MySQL Community Server (GPL)


2014-01-02 20:32:34 4060 [Note] Plugin 'FEDERATED' is disabled.
2014-01-02 20:32:34 f7c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-01-02 20:32:34 4060 [Note] InnoDB: The InnoDB memory heap is disabled
2014-01-02 20:32:34 4060 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-01-02 20:32:34 4060 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-01-02 20:32:34 4060 [Note] InnoDB: Not using CPU crc32 instructions
2014-01-02 20:32:34 4060 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-01-02 20:32:34 4060 [Note] InnoDB: Completed initialization of buffer pool
2014-01-02 20:32:34 4060 [Note] InnoDB: Highest supported file format is Barracuda.
2014-01-02 20:32:35 4060 [Note] InnoDB: Log scan progressed past the checkpoint lsn 5354714
2014-01-02 20:32:35 4060 [Note] InnoDB: Database was not shutdown normally!
2014-01-02 20:32:35 4060 [Note] InnoDB: Starting crash recovery.
2014-01-02 20:32:35 4060 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-01-02 20:32:35 4060 [Note] InnoDB: Restoring possible half-written data pages
2014-01-02 20:32:35 4060 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 5354947
2014-01-02 20:32:36 f7c InnoDB: Error: page 193 log sequence number 5358542
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 211 log sequence number 5358669
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 212 log sequence number 5358780
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 219 log sequence number 5358891
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 522 log sequence number 5362467
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 439 log sequence number 5364168
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 375 log sequence number 5378887
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 376 log sequence number 5379257
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 457 log sequence number 5393076
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 4060 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
2014-01-02 20:32:37 4060 [Note] InnoDB: 128 rollback segment(s) are active.
2014-01-02 20:32:37 4060 [Note] InnoDB: Waiting for purge to start
2014-01-02 20:32:37 f7c InnoDB: Error: page 0 log sequence number 5393843
InnoDB: is in the future! Current system log sequence number 5359021.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:37 4060 [Note] InnoDB: 5.6.14 started; log sequence number 5354947
2014-01-02 20:32:37 4060 [Note] Server hostname (bind-address): '*'; port: 3306
2014-01-02 20:32:37 4060 [Note] IPv6 is available.
2014-01-02 20:32:37 4060 [Note] - '::' resolves to '::';
2014-01-02 20:32:37 4060 [Note] Server socket created on IP: '::'.
2014-01-02 20:32:39 4060 [Note] Event Scheduler: Loaded 0 events
2014-01-02 20:32:39 4060 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.14' socket: '' port: 3306 MySQL Community Server (GPL)
2014-01-02 20:38:26 e30 InnoDB: Assertion failure in thread 3632 in file trx0purge.cc line 699
InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: about forcing recovery.
12:38:26 UTC - mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=2
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133774 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
1116da0 mysqld.exe!my_thread_name()
134fc7d mysqld.exe!my_mb_ctype_mb()
117d59c mysqld.exe!xor_string()
117d977 mysqld.exe!xor_string()
117e447 mysqld.exe!xor_string()
117e6f6 mysqld.exe!xor_string()
115a847 mysqld.exe!xor_string()
115aa62 mysqld.exe!xor_string()
75c4336a kernel32.dll!BaseThreadInitThunk()
77219f72 ntdll.dll!RtlInitializeExceptionChain()
77219f45 ntdll.dll!RtlInitializeExceptionChain()
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.


2014-01-02 20:43:47 2848 [Note] Plugin 'FEDERATED' is disabled.
2014-01-02 20:43:47 c24 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-01-02 20:43:47 2848 [Note] InnoDB: The InnoDB memory heap is disabled
2014-01-02 20:43:47 2848 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-01-02 20:43:47 2848 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-01-02 20:43:47 2848 [Note] InnoDB: Not using CPU crc32 instructions
2014-01-02 20:43:47 2848 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-01-02 20:43:47 2848 [Note] InnoDB: Completed initialization of buffer pool
2014-01-02 20:43:47 2848 [Note] InnoDB: Highest supported file format is Barracuda.
2014-01-02 20:43:47 2848 [Note] InnoDB: Log scan progressed past the checkpoint lsn 5416498
2014-01-02 20:43:47 2848 [Note] InnoDB: Database was not shutdown normally!
2014-01-02 20:43:47 2848 [Note] InnoDB: Starting crash recovery.
2014-01-02 20:43:47 2848 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-01-02 20:43:47 2880 [Note] Plugin 'FEDERATED' is disabled.
2014-01-02 20:43:47 cf8 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-01-02 20:43:47 2880 [Note] InnoDB: The InnoDB memory heap is disabled
2014-01-02 20:43:47 2880 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-01-02 20:43:47 2880 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-01-02 20:43:47 2880 [Note] InnoDB: Not using CPU crc32 instructions
2014-01-02 20:43:47 2880 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-01-02 20:43:47 2880 [Note] InnoDB: Completed initialization of buffer pool
2014-01-02 20:43:47 2880 [ERROR] InnoDB: C:\xampp\mysql\data\ibdata1 can't be opened in read-write mode
2014-01-02 20:43:47 2880 [ERROR] InnoDB: The system tablespace must be writable!
2014-01-02 20:43:47 2880 [ERROR] Plugin 'InnoDB' init function returned error.
2014-01-02 20:43:47 2880 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2014-01-02 20:43:47 2880 [ERROR] Unknown/unsupported storage engine: InnoDB
2014-01-02 20:43:47 2880 [ERROR] Aborting

2014-01-02 20:43:47 2880 [Note] Binlog end
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'partition'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_METRICS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_CMPMEM'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_CMP'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_LOCKS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_TRX'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'BLACKHOLE'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'ARCHIVE'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'MRG_MYISAM'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'MyISAM'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'MEMORY'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'CSV'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'sha256_password'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'mysql_old_password'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'mysql_native_password'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'binlog'
2014-01-02 20:43:47 2880 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2014-01-02 20:43:48 2848 [Note] InnoDB: Restoring possible half-written data pages
2014-01-02 20:43:48 2848 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 5440549
2014-01-02 20:43:48 2848 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
2014-01-02 20:43:48 2848 [Note] InnoDB: 128 rollback segment(s) are active.
2014-01-02 20:43:48 2848 [Note] InnoDB: Waiting for purge to start
2014-01-02 20:43:48 1648 InnoDB: Assertion failure in thread 5704 in file trx0purge.cc line 699
InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: about forcing recovery.
12:43:48 UTC - mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133774 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
2014-01-02 20:43:48 2848 [Note] InnoDB: 5.6.14 started; log sequence number 5440549
2014-01-02 20:43:48 2848 [Note] Server hostname (bind-address): '*'; port: 3306
2014-01-02 20:43:48 2848 [Note] IPv6 is available.
2014-01-02 20:43:48 2848 [Note] - '::' resolves to '::';
2014-01-02 20:43:48 2848 [Note] Server socket created on IP: '::'.
be6da0 mysqld.exe!my_thread_name()
e1fc7d mysqld.exe!my_mb_ctype_mb()
c4d59c mysqld.exe!xor_string()
c4d977 mysqld.exe!xor_string()
c4e447 mysqld.exe!xor_string()
c4e6f6 mysqld.exe!xor_string()
c2a86d mysqld.exe!xor_string()
c2aa62 mysqld.exe!xor_string()
7553336a kernel32.dll!BaseThreadInitThunk()
775e9f72 ntdll.dll!RtlInitializeExceptionChain()
775e9f45 ntdll.dll!RtlInitializeExceptionChain()
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2014-01-02 20:43:48 2848 [Note] Event Scheduler: Loaded 0 events
2014-01-02 20:43:48 2848 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.14' socket: '' port: 3306 MySQL Community Server (GPL)


[EDIT by Altrea: shortened the log file contents to the essential parts]
by robiejein
04. January 2014 07:40
 
Forum: XAMPP for Windows
Topic: Help Please, MySql error shutdown unexpectedly
Replies: 6
Views: 7098
PreviousNext

Return to advanced search