Search found 1093 matches: InnoDB

Searched query: +InnoDB

Return to advanced search

Re: mysql kann nicht gestartet werden

Hallo,
Shit happens
besonders bei Windows

Du hast gesagt
hilf doch selbst
: also mach ich mal..

siehe: http://blackbird.si/mysql-corrupted-innodb-tables-recovery-step-by-step-guide/
oder: http://dev.mysql.com/doc/refman/5.0/en/forcing-innodb-recovery.html

mit diesen Infos kannst Du ein aktuelles Backup erstellen und anschließend wieder einspielen. Nix is Lost.
@Nobbie endloses Gelabere wäre uns erspart geblieben, hättest Du uns einfach einen Link genannt und uns so viel Zeit beim Suchen erspart und den den Rat der xampp-Macher, dass uns hier geholfen wird, erfüllt.

Gruß und noch viel Spass mit fröhlicher Plauderei
Rudi
by RudiMBM
08. June 2015 19:29
 
Forum: XAMPP für Windows
Topic: mysql kann nicht gestartet werden
Replies: 14
Views: 760

Re: mysql kann nicht gestartet werden

RudiMBM wrote:3. Das Filesystem ist ok. Was passiert wenn ich trotzdem t innodb_force_recovery > 0 mache.?


Keine Ahnung, ich habe das noch nie gemacht. So wie es klingt, versucht InnoDB dann weiterzumachen.

RudiMBM wrote:Mommentan war ich noch von Mysql begeistert, aber wenn sogar MsAccess eine Repair-Funktion hat?


Jede Repair Funktion hat Grenzen. Von nichts kann man nichts reparieren. Wir wisssen ja nicht, was genau passiert ist. Die wichtigste Repair Funktion sind regelmäßige Backups, das sollte eigentlich einem "Grufty" mit 45 Jahren Berufserfahrung in Fleisch und Blut übergegangen sein...
by Nobbie
08. June 2015 17:15
 
Forum: XAMPP für Windows
Topic: mysql kann nicht gestartet werden
Replies: 14
Views: 760

Re: mysql kann nicht gestartet werden

Wenn Du es selbst nicht übersetzen kannst, gib es einfach bei Google Translator ein:

If the table is not needed, or you can restore it from a backup, then you can remove the .ibd file, and InnoDB will do a normal crash recovery and ignore that table.


bzw. dritter Ratschlag:

If the file system or the disk is broken, and you cannot remove the .ibd file, you can set innodb_force_recovery > 0 in my.cnf and force InnoDB to continue crash recovery here.
by Nobbie
08. June 2015 14:26
 
Forum: XAMPP für Windows
Topic: mysql kann nicht gestartet werden
Replies: 14
Views: 760

Re: mysql kann nicht gestartet werden

habe das Problem auch seit heute:

2015-06-08 13:08:27 5304 [Note] Plugin 'FEDERATED' is disabled.
2015-06-08 13:08:27 1750 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.
2015-06-08 13:08:27 5304 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-06-08 13:08:27 5304 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-08 13:08:27 5304 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-08 13:08:27 5304 [Note] InnoDB: Memory barrier is not used
2015-06-08 13:08:27 5304 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-08 13:08:27 5304 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-08 13:08:27 5304 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-08 13:08:27 5304 [Note] InnoDB: Completed initialization of buffer pool
2015-06-08 13:08:27 5304 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-08 13:08:27 5304 [Note] InnoDB: The log sequence numbers 2324023260 and 2324023260 in ibdata files do not match the log sequence number 2371145018 in the ib_logfiles!
2015-06-08 13:08:27 5304 [Note] InnoDB: Database was not shutdown normally!
2015-06-08 13:08:27 5304 [Note] InnoDB: Starting crash recovery.
2015-06-08 13:08:27 5304 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-08 13:08:27 5304 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd. Cannot open tablespace validierung/validierung which uses space ID: 1 at filepath: .\validierung\validierung.ibd
InnoDB: Error: could not open single-table tablespace file .\validierung\validierung.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
by Ghost108
08. June 2015 12:15
 
Forum: XAMPP für Windows
Topic: mysql kann nicht gestartet werden
Replies: 14
Views: 760

Re: Tabelle zerschossen?

RudiMBM wrote:Na, mit xampp kann man ja phpMyAdmin starten. Dort gibts die neben anderen Funktionen die DB-Copy-Taste.


Welche Taste soll das sein?? Du meinst wahrscheinlich stattdessen den Dialog "Datenbank kopieren"?!

RudiMBM wrote:Interessant wäre für mich auch wie und wo dieser lästige Timeout verlängert werden kann.


Wahrscheinlich ist das die Angabe max_execution_time, die Zahl ist die Zeit Sekunden, wird per Default mit 30 Sekunden ausgeliefert. Kannst Du entweder sehr hoch setzen (3600 wäre eine Stunde) oder gleich auf 0 setzen (Ausnahmefall), dann gibt es gar keinen Timeout. Danach muss Apache neu gestartet werden.

RudiMBM wrote:Also, seitdem kann ich den phpMyAdmin nicht mehr starten und mit mysqld.bat gehts auch nicht.


Gleiches Problem wie in dem anderen Thread - Null Fehlermeldung, Null Beschreibung. Fange ich nichts mit an. Aber aus den Meldungen oben von MySQL vermute ich, dass die komplette Datenhaltung zerschossen ist. MySQL benutzt (leider) seit einigen Releases per Default die Engine InnoDB (vorher MyISAM), und InnoDB bewahrt so gut wie sämtliche Daten in einer einzigen Riesendatei auf. Bei MyISAM war das anders, da entsprach ein Directory einer Datenbank und die Dateien in dem Directory waren die Tabellen. Dadurch dass in InnoDB alles zusammengeklumpt ist, ist beim Kopieren wahrscheinlich durch den Abbruch die ganze Riesendatei zerschossen worden. Ich würde an Deiner Stelle mit den einzelnen Fehlermeldungen aus der Liste oben im Internet suchen, ob es da irgendwelche Repair Optionen gibt. Besser wäre ein Backup einzuspielen und quasi von vorne anzufangen.
by Nobbie
08. June 2015 11:18
 
Forum: XAMPP für Windows
Topic: Tabelle zerschossen?
Replies: 3
Views: 279

Tabelle zerschossen?

Hallo,
was kann ich tun um mysql mit xampp 3.2.1 wieder starten zu können.
Ich hab die Datenbank copieren wollen. Das wurde aber wegen Timeout abgebrochen. Die DB war zudem noch in einem anderen Programm geöffnet.
Seitdem kommt dieser Fehler:

Code: Select all
2015-06-07 10:22:05 3176 [Note] Plugin 'FEDERATED' is disabled.
2015-06-07 10:22:05 c6c 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.
2015-06-07 10:22:05 3176 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-06-07 10:22:05 3176 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-07 10:22:05 3176 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-07 10:22:05 3176 [Note] InnoDB: Memory barrier is not used
2015-06-07 10:22:05 3176 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-07 10:22:05 3176 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-07 10:22:05 3176 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-07 10:22:05 3176 [Note] InnoDB: Completed initialization of buffer pool
2015-06-07 10:22:05 3176 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-07 10:22:05 3176 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 29927796 in the ib_logfiles!
2015-06-07 10:22:05 3176 [Note] InnoDB: Database was not shutdown normally!
2015-06-07 10:22:05 3176 [Note] InnoDB: Starting crash recovery.
2015-06-07 10:22:05 3176 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-07 10:22:05 3176 [Note] InnoDB: Restoring possible half-written data pages
2015-06-07 10:22:05 3176 [Note] InnoDB: from the doublewrite buffer...
2015-06-07 10:22:05 3176 [Note] InnoDB: 128 rollback segment(s) are active.
2015-06-07 10:22:05 3176 [Note] InnoDB: Waiting for purge to start
2015-06-07 10:22:05 3176 [Note] InnoDB: 5.6.21 started; log sequence number 29927796
2015-06-07 10:22:05 3176 [Note] Server hostname (bind-address): '*'; port: 3306
2015-06-07 10:22:05 3176 [Note] IPv6 is available.
2015-06-07 10:22:05 3176 [Note]   - '::' resolves to '::';
2015-06-07 10:22:05 3176 [Note] Server socket created on IP: '::'.
2015-06-07 10:22:05 3176 [Note] Event Scheduler: Loaded 0 events
2015-06-07 10:22:05 3176 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.21'  socket: ''  port: 3306  MySQL Community Server (GPL)

2015-06-07 14:16:45 3176 [Note] Plugin 'FEDERATED' is disabled.
2015-06-07 14:16:45 c6c 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.
2015-06-07 14:16:45 3176 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-06-07 14:16:45 3176 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-07 14:16:45 3176 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-07 14:16:45 3176 [Note] InnoDB: Memory barrier is not used
2015-06-07 14:16:45 3176 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-07 14:16:45 3176 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-07 14:16:45 3176 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-07 14:16:45 3176 [Note] InnoDB: Completed initialization of buffer pool
2015-06-07 14:16:45 3176 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-07 14:16:45 3176 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 34658401 in the ib_logfiles!
2015-06-07 14:16:45 3176 [Note] InnoDB: Database was not shutdown normally!
2015-06-07 14:16:45 3176 [Note] InnoDB: Starting crash recovery.
2015-06-07 14:16:45 3176 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-07 14:16:45 3176 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace vlps/albentb uses space ID: 111 at filepath: .\vlps\albentb.ibd. Cannot open tablespace vlps_save2/albentb which uses space ID: 111 at filepath: .\vlps_save2\albentb.ibd
InnoDB: Error: could not open single-table tablespace file .\vlps_save2\albentb.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.


Gruß Rudi
by RudiMBM
07. June 2015 14:15
 
Forum: XAMPP für Windows
Topic: Tabelle zerschossen?
Replies: 3
Views: 279

Problem with website on localhost

Hi,

I dont know how to solve this problme, i googled but nothing.

So i have few websites developed on my localhost, and they works fine.
I have migrate 1 from web server to localhost so i can do few fixex.
Because my database is to large, i made modification on php.ini file to extend memory

max_execution_time = 259200
max_input_time = 259200
memory_limit = 1000M
upload_max_filesize = 750M
post_max_size = 750M

I have sucessfully uploaded database. But when i want to access that website I have only white blank screen, no html on it.

Here is the log.

Code: Select all
2015-06-03 22:33:50 12604 [Note] Giving 0 client threads a chance to die gracefully
2015-06-03 22:33:50 12604 [Note] Event Scheduler: Purging the queue. 0 events
2015-06-03 22:33:50 12604 [Note] Shutting down slave threads
2015-06-03 22:33:50 12604 [Note] Forcefully disconnecting 0 remaining clients
2015-06-03 22:33:50 12604 [Note] Binlog end
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'partition'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_METRICS'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_CMPMEM'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_CMP'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_LOCKS'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'INNODB_TRX'
2015-06-03 22:33:50 12604 [Note] Shutting down plugin 'InnoDB'
2015-06-03 22:33:50 12604 [Note] InnoDB: FTS optimize thread exiting.
2015-06-03 22:33:50 12604 [Note] InnoDB: Starting shutdown...
2015-06-03 22:33:52 12604 [Note] InnoDB: Shutdown completed; log sequence number 155629309
2015-06-03 22:33:52 12604 [Note] Shutting down plugin 'BLACKHOLE'
2015-06-03 22:33:52 12604 [Note] Shutting down plugin 'ARCHIVE'
2015-06-03 22:33:52 12604 [Note] Shutting down plugin 'MRG_MYISAM'
2015-06-03 22:33:52 12604 [Note] Shutting down plugin 'MyISAM'
2015-06-03 22:33:52 12604 [Note] Shutting down plugin 'MEMORY'
2015-06-03 22:33:52 12604 [Note] Shutting down plugin 'CSV'
2015-06-03 22:33:52 12604 [Note] Shutting down plugin 'sha256_password'
2015-06-03 22:33:52 12604 [Note] Shutting down plugin 'mysql_old_password'
2015-06-03 22:33:52 12604 [Note] Shutting down plugin 'mysql_native_password'
2015-06-03 22:33:52 12604 [Note] Shutting down plugin 'binlog'
2015-06-03 22:33:52 12604 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2015-06-03 22:33:53 3368 [Note] Plugin 'FEDERATED' is disabled.
2015-06-03 22:33:53 12f8 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.
2015-06-03 22:33:53 3368 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-06-03 22:33:53 3368 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-03 22:33:53 3368 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-03 22:33:53 3368 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-03 22:33:53 3368 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-03 22:33:53 3368 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-03 22:33:53 3368 [Note] InnoDB: Completed initialization of buffer pool
2015-06-03 22:33:53 3368 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-03 22:33:54 3368 [Note] InnoDB: 128 rollback segment(s) are active.
2015-06-03 22:33:54 3368 [Note] InnoDB: Waiting for purge to start
2015-06-03 22:33:54 3368 [Note] InnoDB: 5.6.16 started; log sequence number 155629309
2015-06-03 22:33:54 3368 [Note] Server hostname (bind-address): '*'; port: 3306
2015-06-03 22:33:54 3368 [Note] IPv6 is available.
2015-06-03 22:33:54 3368 [Note]   - '::' resolves to '::';
2015-06-03 22:33:54 3368 [Note] Server socket created on IP: '::'.
2015-06-03 22:33:54 3368 [Note] Event Scheduler: Loaded 0 events
2015-06-03 22:33:54 3368 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.16'  socket: ''  port: 3306  MySQL Community Server (GPL)


The rest of websites works fine.
by pavlito
03. June 2015 21:53
 
Forum: phpMyAdmin
Topic: Problem with website on localhost
Replies: 4
Views: 326

Re: MYSQL crash

courcoa wrote:2015-06-02 13:47:08 8044 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-02 13:47:08 8044 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 3353125 in the ib_logfiles!
2015-06-02 13:47:08 8044 [Note] InnoDB: Database was not shutdown normally!
2015-06-02 13:47:08 8044 [Note] InnoDB: Starting crash recovery.

1. Go to xampp\mysql\data\mysql

2. Create a "Backup" folder under data

3. Move those files to your Backup folder
innodb_index_stats.frm
innodb_index_stats.ibd
innodb_table_stats.frm
innodb_table_stats.ibd
slave_master_info.ibd
slave_relay_log_info.frm
slave_relay_log_info.ibd
slave_worker_info.frm
slave_worker_info.ibd
4. now open control panel and click on start under mysql

5. reply back

You can try this method also:

1. Open Xampp -> MySQL -> Configuration.

2. In [mysqld] section, add the following line:
innodb_force_recovery = 1

3. Save the file and try starting MySQL

4. Remove that line which you just added and Save.
by mark.mcdonald
02. June 2015 14:53
 
Forum: XAMPP for Windows
Topic: MYSQL crash
Replies: 2
Views: 247

MYSQL crash

Hello,

i'm really novice and since today MYSQL crash and I have this message in mysql_error.log :

2015-06-02 13:47:07 8044 [Note] Plugin 'FEDERATED' is disabled.
2015-06-02 13:47:07 1fb0 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.
2015-06-02 13:47:07 8044 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-06-02 13:47:07 8044 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-02 13:47:07 8044 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-02 13:47:07 8044 [Note] InnoDB: Memory barrier is not used
2015-06-02 13:47:07 8044 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-02 13:47:07 8044 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-02 13:47:07 8044 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-02 13:47:07 8044 [Note] InnoDB: Completed initialization of buffer pool
2015-06-02 13:47:08 8044 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-02 13:47:08 8044 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 3353125 in the ib_logfiles!
2015-06-02 13:47:08 8044 [Note] InnoDB: Database was not shutdown normally!
2015-06-02 13:47:08 8044 [Note] InnoDB: Starting crash recovery.
2015-06-02 13:47:08 8044 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-02 13:47:08 8044 [Note] InnoDB: Restoring possible half-written data pages
2015-06-02 13:47:08 8044 [Note] InnoDB: from the doublewrite buffer...
2015-06-02 13:47:08 8044 [Note] InnoDB: 128 rollback segment(s) are active.
2015-06-02 13:47:08 8044 [Note] InnoDB: Waiting for purge to start
2015-06-02 13:47:10 8044 [Note] InnoDB: 5.6.24 started; log sequence number 3353125
2015-06-02 13:47:11 8044 [Note] Server hostname (bind-address): '*'; port: 3306
2015-06-02 13:47:11 8044 [Note] IPv6 is available.
2015-06-02 13:47:11 8044 [Note] - '::' resolves to '::';
2015-06-02 13:47:11 8044 [Note] Server socket created on IP: '::'.

Is there somebody to help me, because I don't understand what is the problem and how can I solve it ?
Thanks for all

PS : I'm french so excuse my poor english
by courcoa
02. June 2015 13:04
 
Forum: XAMPP for Windows
Topic: MYSQL crash
Replies: 2
Views: 247

MysQL error

I get this error when trying to start MysQL
2015-06-01 21:56:17 25476 [Note] Plugin 'FEDERATED' is disabled.
2015-06-01 21:56:17 63a0 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.
2015-06-01 21:56:17 25476 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-06-01 21:56:17 25476 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-01 21:56:17 25476 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-01 21:56:17 25476 [Note] InnoDB: Memory barrier is not used
2015-06-01 21:56:17 25476 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-01 21:56:17 25476 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-01 21:56:17 25476 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-01 21:56:17 25476 [Note] InnoDB: Completed initialization of buffer pool
2015-06-01 21:56:17 25476 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-01 21:56:18 25476 [Note] InnoDB: 128 rollback segment(s) are active.
2015-06-01 21:56:18 25476 [Note] InnoDB: Waiting for purge to start
2015-06-01 21:56:18 25476 [Note] InnoDB: 5.6.24 started; log sequence number 1665234
2015-06-01 21:56:18 25476 [Note] Server hostname (bind-address): '*'; port: 3306
2015-06-01 21:56:18 25476 [Note] IPv6 is available.
2015-06-01 21:56:18 25476 [Note] - '::' resolves to '::';
2015-06-01 21:56:18 25476 [Note] Server socket created on IP: '::'.
2015-06-01 21:56:18 25476 [ERROR] Can't start server: Bind on TCP/IP port: No such file or directory
2015-06-01 21:56:18 25476 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2015-06-01 21:56:18 25476 [ERROR] Aborting

2015-06-01 21:56:18 25476 [Note] Binlog end
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'partition'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_METRICS'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_CMPMEM'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_CMP'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_LOCKS'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'INNODB_TRX'
2015-06-01 21:56:18 25476 [Note] Shutting down plugin 'InnoDB'
2015-06-01 21:56:18 25476 [Note] InnoDB: FTS optimize thread exiting.
2015-06-01 21:56:18 25476 [Note] InnoDB: Starting shutdown...
2015-06-01 21:56:19 25476 [Note] InnoDB: Shutdown completed; log sequence number 1665244
2015-06-01 21:56:19 25476 [Note] Shutting down plugin 'BLACKHOLE'
2015-06-01 21:56:19 25476 [Note] Shutting down plugin 'ARCHIVE'
2015-06-01 21:56:19 25476 [Note] Shutting down plugin 'MRG_MYISAM'
2015-06-01 21:56:19 25476 [Note] Shutting down plugin 'MyISAM'
2015-06-01 21:56:19 25476 [Note] Shutting down plugin 'MEMORY'
2015-06-01 21:56:19 25476 [Note] Shutting down plugin 'CSV'
2015-06-01 21:56:19 25476 [Note] Shutting down plugin 'sha256_password'
2015-06-01 21:56:19 25476 [Note] Shutting down plugin 'mysql_old_password'
2015-06-01 21:56:19 25476 [Note] Shutting down plugin 'mysql_native_password'
2015-06-01 21:56:19 25476 [Note] Shutting down plugin 'binlog'
2015-06-01 21:56:19 25476 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2015-06-01 21:57:00 25856 [Note] Plugin 'FEDERATED' is disabled.
2015-06-01 21:57:00 6504 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.
2015-06-01 21:57:00 25856 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-06-01 21:57:00 25856 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-01 21:57:00 25856 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-01 21:57:00 25856 [Note] InnoDB: Memory barrier is not used
2015-06-01 21:57:00 25856 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-01 21:57:00 25856 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-01 21:57:00 25856 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-01 21:57:00 25856 [Note] InnoDB: Completed initialization of buffer pool
2015-06-01 21:57:01 25856 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-01 21:57:01 25856 [Note] InnoDB: 128 rollback segment(s) are active.
2015-06-01 21:57:01 25856 [Note] InnoDB: Waiting for purge to start
2015-06-01 21:57:01 25856 [Note] InnoDB: 5.6.24 started; log sequence number 1665244
2015-06-01 21:57:01 25856 [Note] Server hostname (bind-address): '*'; port: 3306
2015-06-01 21:57:01 25856 [Note] IPv6 is available.
2015-06-01 21:57:01 25856 [Note] - '::' resolves to '::';
2015-06-01 21:57:01 25856 [Note] Server socket created on IP: '::'.
2015-06-01 21:57:01 25856 [ERROR] Can't start server: Bind on TCP/IP port: No such file or directory
2015-06-01 21:57:01 25856 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2015-06-01 21:57:01 25856 [ERROR] Aborting

2015-06-01 21:57:01 25856 [Note] Binlog end
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'partition'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_METRICS'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_CMPMEM'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_CMP'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_LOCKS'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'INNODB_TRX'
2015-06-01 21:57:01 25856 [Note] Shutting down plugin 'InnoDB'
2015-06-01 21:57:01 25856 [Note] InnoDB: FTS optimize thread exiting.
2015-06-01 21:57:01 25856 [Note] InnoDB: Starting shutdown...
2015-06-01 21:57:03 25856 [Note] InnoDB: Shutdown completed; log sequence number 1665254
2015-06-01 21:57:03 25856 [Note] Shutting down plugin 'BLACKHOLE'
2015-06-01 21:57:03 25856 [Note] Shutting down plugin 'ARCHIVE'
2015-06-01 21:57:03 25856 [Note] Shutting down plugin 'MRG_MYISAM'
2015-06-01 21:57:03 25856 [Note] Shutting down plugin 'MyISAM'
2015-06-01 21:57:03 25856 [Note] Shutting down plugin 'MEMORY'
2015-06-01 21:57:03 25856 [Note] Shutting down plugin 'CSV'
2015-06-01 21:57:03 25856 [Note] Shutting down plugin 'sha256_password'
2015-06-01 21:57:03 25856 [Note] Shutting down plugin 'mysql_old_password'
2015-06-01 21:57:03 25856 [Note] Shutting down plugin 'mysql_native_password'
2015-06-01 21:57:03 25856 [Note] Shutting down plugin 'binlog'
2015-06-01 21:57:03 25856 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2015-06-01 21:57:21 26092 [Note] Plugin 'FEDERATED' is disabled.
2015-06-01 21:57:21 65f0 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.
2015-06-01 21:57:21 26092 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-06-01 21:57:21 26092 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-01 21:57:21 26092 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-01 21:57:21 26092 [Note] InnoDB: Memory barrier is not used
2015-06-01 21:57:21 26092 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-01 21:57:21 26092 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-01 21:57:21 26092 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-01 21:57:21 26092 [Note] InnoDB: Completed initialization of buffer pool
2015-06-01 21:57:21 26092 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-01 21:57:21 26092 [Note] InnoDB: 128 rollback segment(s) are active.
2015-06-01 21:57:21 26092 [Note] InnoDB: Waiting for purge to start
2015-06-01 21:57:22 26092 [Note] InnoDB: 5.6.24 started; log sequence number 1665254
2015-06-01 21:57:22 26092 [Note] Server hostname (bind-address): '*'; port: 3306
2015-06-01 21:57:22 26092 [Note] IPv6 is available.
2015-06-01 21:57:22 26092 [Note] - '::' resolves to '::';
2015-06-01 21:57:22 26092 [Note] Server socket created on IP: '::'.
2015-06-01 21:57:22 26092 [ERROR] Can't start server: Bind on TCP/IP port: No such file or directory
2015-06-01 21:57:22 26092 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2015-06-01 21:57:22 26092 [ERROR] Aborting

2015-06-01 21:57:22 26092 [Note] Binlog end
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'partition'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_METRICS'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_CMPMEM'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_CMP'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_LOCKS'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'INNODB_TRX'
2015-06-01 21:57:22 26092 [Note] Shutting down plugin 'InnoDB'
2015-06-01 21:57:22 26092 [Note] InnoDB: FTS optimize thread exiting.
2015-06-01 21:57:22 26092 [Note] InnoDB: Starting shutdown...
2015-06-01 21:57:23 26092 [Note] InnoDB: Shutdown completed; log sequence number 1665264
2015-06-01 21:57:23 26092 [Note] Shutting down plugin 'BLACKHOLE'
2015-06-01 21:57:23 26092 [Note] Shutting down plugin 'ARCHIVE'
2015-06-01 21:57:23 26092 [Note] Shutting down plugin 'MRG_MYISAM'
2015-06-01 21:57:23 26092 [Note] Shutting down plugin 'MyISAM'
2015-06-01 21:57:23 26092 [Note] Shutting down plugin 'MEMORY'
2015-06-01 21:57:23 26092 [Note] Shutting down plugin 'CSV'
2015-06-01 21:57:23 26092 [Note] Shutting down plugin 'sha256_password'
2015-06-01 21:57:23 26092 [Note] Shutting down plugin 'mysql_old_password'
2015-06-01 21:57:23 26092 [Note] Shutting down plugin 'mysql_native_password'
2015-06-01 21:57:23 26092 [Note] Shutting down plugin 'binlog'
2015-06-01 21:57:23 26092 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete
by Ossimestari420
01. June 2015 20:03
 
Forum: MySQL
Topic: MysQL error
Replies: 0
Views: 194

Re: Error with MySQL

InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
by mark.mcdonald
29. May 2015 22:44
 
Forum: XAMPP for Windows
Topic: Error with MySQL
Replies: 4
Views: 566

Re: Error with MySQL

mysql_error.log

Code: Select all
2015-05-29 21:57:11 9592 [Note] Plugin 'FEDERATED' is disabled.
2015-05-29 21:57:11 1b80 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.
2015-05-29 21:57:11 9592 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-29 21:57:11 9592 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-29 21:57:11 9592 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-29 21:57:11 9592 [Note] InnoDB: Memory barrier is not used
2015-05-29 21:57:11 9592 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-29 21:57:11 9592 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-29 21:57:11 9592 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-29 21:57:11 9592 [Note] InnoDB: Completed initialization of buffer pool
2015-05-29 21:57:11 9592 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-29 21:57:11 9592 [Note] InnoDB: 128 rollback segment(s) are active.
2015-05-29 21:57:11 9592 [Note] InnoDB: Waiting for purge to start
2015-05-29 21:57:11 9592 [Note] InnoDB: 5.6.24 started; log sequence number 1665234
2015-05-29 21:57:11 9592 [Note] Server hostname (bind-address): '*'; port: 3306
2015-05-29 21:57:11 9592 [Note] IPv6 is available.
2015-05-29 21:57:11 9592 [Note]   - '::' resolves to '::';
2015-05-29 21:57:11 9592 [Note] Server socket created on IP: '::'.
2015-05-29 21:58:17 5220 [Note] Plugin 'FEDERATED' is disabled.
2015-05-29 21:58:17 648 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.
2015-05-29 21:58:17 5220 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-29 21:58:17 5220 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-29 21:58:17 5220 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-29 21:58:17 5220 [Note] InnoDB: Memory barrier is not used
2015-05-29 21:58:17 5220 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-29 21:58:17 5220 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-29 21:58:17 5220 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-29 21:58:17 5220 [Note] InnoDB: Completed initialization of buffer pool
2015-05-29 21:58:17 5220 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-29 21:58:17 5220 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1665234
2015-05-29 21:58:17 5220 [Note] InnoDB: Database was not shutdown normally!
2015-05-29 21:58:17 5220 [Note] InnoDB: Starting crash recovery.
2015-05-29 21:58:17 5220 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-29 21:58:17 5220 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace a_fragodajniav2mybb/mybb_dvz_shoutbox uses space ID: 307 at filepath: .\a_fragodajniav2mybb\mybb_dvz_shoutbox.ibd. Cannot open tablespace a_gamingo/mybb_dvz_shoutbox which uses space ID: 307 at filepath: .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: Error: could not open single-table tablespace file .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-05-29 21:58:19 3344 [Note] Plugin 'FEDERATED' is disabled.
2015-05-29 21:58:19 23b4 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.
2015-05-29 21:58:19 3344 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-29 21:58:19 3344 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-29 21:58:19 3344 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-29 21:58:19 3344 [Note] InnoDB: Memory barrier is not used
2015-05-29 21:58:19 3344 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-29 21:58:19 3344 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-29 21:58:19 3344 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-29 21:58:19 3344 [Note] InnoDB: Completed initialization of buffer pool
2015-05-29 21:58:19 3344 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-29 21:58:19 3344 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1665234
2015-05-29 21:58:19 3344 [Note] InnoDB: Database was not shutdown normally!
2015-05-29 21:58:19 3344 [Note] InnoDB: Starting crash recovery.
2015-05-29 21:58:19 3344 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-29 21:58:19 3344 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace a_fragodajniav2mybb/mybb_dvz_shoutbox uses space ID: 307 at filepath: .\a_fragodajniav2mybb\mybb_dvz_shoutbox.ibd. Cannot open tablespace a_gamingo/mybb_dvz_shoutbox which uses space ID: 307 at filepath: .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: Error: could not open single-table tablespace file .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-05-29 21:58:53 10684 [Note] Plugin 'FEDERATED' is disabled.
2015-05-29 21:58:53 6cc 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.
2015-05-29 21:58:53 10684 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-29 21:58:53 10684 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-29 21:58:53 10684 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-29 21:58:53 10684 [Note] InnoDB: Memory barrier is not used
2015-05-29 21:58:53 10684 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-29 21:58:53 10684 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-29 21:58:53 10684 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-29 21:58:53 10684 [Note] InnoDB: Completed initialization of buffer pool
2015-05-29 21:58:53 10684 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-29 21:58:53 10684 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1665234
2015-05-29 21:58:53 10684 [Note] InnoDB: Database was not shutdown normally!
2015-05-29 21:58:53 10684 [Note] InnoDB: Starting crash recovery.
2015-05-29 21:58:53 10684 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-29 21:58:53 10684 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace a_fragodajniav2mybb/mybb_dvz_shoutbox uses space ID: 307 at filepath: .\a_fragodajniav2mybb\mybb_dvz_shoutbox.ibd. Cannot open tablespace a_gamingo/mybb_dvz_shoutbox which uses space ID: 307 at filepath: .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: Error: could not open single-table tablespace file .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-05-29 22:00:47 9956 [Note] Plugin 'FEDERATED' is disabled.
2015-05-29 22:00:47 3c4 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.
2015-05-29 22:00:47 9956 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-29 22:00:47 9956 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-29 22:00:47 9956 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-29 22:00:47 9956 [Note] InnoDB: Memory barrier is not used
2015-05-29 22:00:47 9956 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-29 22:00:47 9956 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-29 22:00:47 9956 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-29 22:00:47 9956 [Note] InnoDB: Completed initialization of buffer pool
2015-05-29 22:00:47 9956 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-29 22:00:47 9956 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1665234
2015-05-29 22:00:47 9956 [Note] InnoDB: Database was not shutdown normally!
2015-05-29 22:00:47 9956 [Note] InnoDB: Starting crash recovery.
2015-05-29 22:00:47 9956 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-29 22:00:47 9956 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace a_fragodajniav2mybb/mybb_dvz_shoutbox uses space ID: 307 at filepath: .\a_fragodajniav2mybb\mybb_dvz_shoutbox.ibd. Cannot open tablespace a_gamingo/mybb_dvz_shoutbox which uses space ID: 307 at filepath: .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: Error: could not open single-table tablespace file .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-05-29 22:26:17 5168 [Note] Plugin 'FEDERATED' is disabled.
2015-05-29 22:26:17 15d4 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.
2015-05-29 22:26:17 5168 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-29 22:26:17 5168 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-29 22:26:17 5168 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-29 22:26:17 5168 [Note] InnoDB: Memory barrier is not used
2015-05-29 22:26:17 5168 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-29 22:26:17 5168 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-29 22:26:17 5168 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-29 22:26:17 5168 [Note] InnoDB: Completed initialization of buffer pool
2015-05-29 22:26:17 5168 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-29 22:26:17 5168 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1665234
2015-05-29 22:26:17 5168 [Note] InnoDB: Database was not shutdown normally!
2015-05-29 22:26:17 5168 [Note] InnoDB: Starting crash recovery.
2015-05-29 22:26:17 5168 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-29 22:26:17 5168 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace a_fragodajniav2mybb/mybb_dvz_shoutbox uses space ID: 307 at filepath: .\a_fragodajniav2mybb\mybb_dvz_shoutbox.ibd. Cannot open tablespace a_gamingo/mybb_dvz_shoutbox which uses space ID: 307 at filepath: .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: Error: could not open single-table tablespace file .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-05-29 22:36:29 4048 [Note] Plugin 'FEDERATED' is disabled.
2015-05-29 22:36:29 c10 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.
2015-05-29 22:36:29 4048 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-29 22:36:29 4048 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-29 22:36:29 4048 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-29 22:36:29 4048 [Note] InnoDB: Memory barrier is not used
2015-05-29 22:36:29 4048 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-29 22:36:29 4048 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-29 22:36:29 4048 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-29 22:36:29 4048 [Note] InnoDB: Completed initialization of buffer pool
2015-05-29 22:36:29 4048 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-29 22:36:29 4048 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1665234
2015-05-29 22:36:29 4048 [Note] InnoDB: Database was not shutdown normally!
2015-05-29 22:36:29 4048 [Note] InnoDB: Starting crash recovery.
2015-05-29 22:36:29 4048 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-29 22:36:29 4048 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace a_fragodajniav2mybb/mybb_dvz_shoutbox uses space ID: 307 at filepath: .\a_fragodajniav2mybb\mybb_dvz_shoutbox.ibd. Cannot open tablespace a_gamingo/mybb_dvz_shoutbox which uses space ID: 307 at filepath: .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: Error: could not open single-table tablespace file .\a_gamingo\mybb_dvz_shoutbox.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
by Frag
29. May 2015 22:28
 
Forum: XAMPP for Windows
Topic: Error with MySQL
Replies: 4
Views: 566

Re: joomla installation stuck

ygwolf wrote:Is this reasonable?

Maybe. If you serach the internet there are two common solutions for this problem:
- increase the max_execution_time limit
- change from InnoDB to MyISAM
Both seem to be plausible.

ygwolf wrote:how do I get to this code?

This is a joomla specific question better been asked at a joomla specific board.

best wishes,
Altrea
by Altrea
25. May 2015 13:39
 
Forum: XAMPP for Windows
Topic: joomla installation stuck
Replies: 4
Views: 227

Re: Recover Locally Hosted Site off Crashed HDD - XAMPP

Micci101 wrote:2015-05-20 10:54:10 2708 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace mysql/innodb_index_stats.Id_63049 which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

Have you tried steps 2 or 3?
It's normal for the message regarding UAC to come up. This won't be an issue.
by mark.mcdonald
20. May 2015 15:30
 
Forum: XAMPP for Windows
Topic: Recover Locally Hosted Site off Crashed HDD - XAMPP
Replies: 20
Views: 1160

Re: Recover Locally Hosted Site off Crashed HDD - XAMPP

2015-05-20 10:48:47 5920 [Note] Plugin 'FEDERATED' is disabled.
2015-05-20 10:48:47 8dc 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.
2015-05-20 10:48:47 5920 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-20 10:48:47 5920 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-20 10:48:47 5920 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-20 10:48:47 5920 [Note] InnoDB: Memory barrier is not used
2015-05-20 10:48:47 5920 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-20 10:48:47 5920 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-20 10:48:47 5920 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-20 10:48:47 5920 [Note] InnoDB: Completed initialization of buffer pool
2015-05-20 10:48:47 5920 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-20 10:48:47 5920 [Note] InnoDB: 128 rollback segment(s) are active.
2015-05-20 10:48:48 5920 [Note] InnoDB: Waiting for purge to start
2015-05-20 10:48:48 5920 [Note] InnoDB: 5.6.21 started; log sequence number 1665234
2015-05-20 10:48:48 5920 [Note] Server hostname (bind-address): '*'; port: 3306
2015-05-20 10:48:48 5920 [Note] IPv6 is available.
2015-05-20 10:48:48 5920 [Note] - '::' resolves to '::';
2015-05-20 10:48:48 5920 [Note] Server socket created on IP: '::'.
2015-05-20 10:54:10 2708 [Note] Plugin 'FEDERATED' is disabled.
2015-05-20 10:54:10 3f8 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.
2015-05-20 10:54:10 2708 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-20 10:54:10 2708 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-20 10:54:10 2708 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-20 10:54:10 2708 [Note] InnoDB: Memory barrier is not used
2015-05-20 10:54:10 2708 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-20 10:54:10 2708 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-20 10:54:10 2708 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-20 10:54:10 2708 [Note] InnoDB: Completed initialization of buffer pool
2015-05-20 10:54:10 2708 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-20 10:54:10 2708 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665244 in the ib_logfiles!
2015-05-20 10:54:10 2708 [Note] InnoDB: Database was not shutdown normally!
2015-05-20 10:54:10 2708 [Note] InnoDB: Starting crash recovery.
2015-05-20 10:54:10 2708 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-20 10:54:10 2708 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace mysql/innodb_index_stats.Id_63049 which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-05-20 16:05:02 128 [Note] Plugin 'FEDERATED' is disabled.
2015-05-20 16:05:02 d48 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.
2015-05-20 16:05:02 128 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-20 16:05:02 128 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-20 16:05:02 128 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-20 16:05:02 128 [Note] InnoDB: Memory barrier is not used
2015-05-20 16:05:02 128 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-20 16:05:02 128 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-20 16:05:02 128 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-20 16:05:02 128 [Note] InnoDB: Completed initialization of buffer pool
2015-05-20 16:05:02 128 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-20 16:05:02 128 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665244 in the ib_logfiles!
2015-05-20 16:05:02 128 [Note] InnoDB: Database was not shutdown normally!
2015-05-20 16:05:02 128 [Note] InnoDB: Starting crash recovery.
2015-05-20 16:05:02 128 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-20 16:05:02 128 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace mysql/innodb_index_stats.Id_63049 which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
by Micci101
20. May 2015 15:06
 
Forum: XAMPP for Windows
Topic: Recover Locally Hosted Site off Crashed HDD - XAMPP
Replies: 20
Views: 1160
PreviousNext

Return to advanced search