Autor | Zpráva | ||
---|---|---|---|
David Klouček Profil |
Po delší době jsem restartoval notebook. Nejprve spustim Apache (OK), potom MySQL, která se ale nezapne a XAMPP vyhodí:
Error: MySQL shutdown unexpectedly. 19:13:38 [mysql] This may be due to a blocked port, missing dependencies, 19:13:38 [mysql] improper privileges, a crash, or a shutdown by another method. 19:13:38 [mysql] Press the Logs button to view error logs and check 19:13:38 [mysql] the Windows Event Viewer for more clues 19:13:38 [mysql] If you need more help, copy and post this 19:13:38 [mysql] entire log window on the forums V MySQL logu je: 2014-01-03 19:18:37 5964 [Note] Plugin 'FEDERATED' is disabled. c:\xampp\mysql\bin\mysqld.exe: Table 'mysql.plugin' doesn't exist 2014-01-03 19:18:37 5964 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 2014-01-03 19:18:37 11f0 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-03 19:18:37 5964 [Note] InnoDB: The InnoDB memory heap is disabled 2014-01-03 19:18:37 5964 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2014-01-03 19:18:37 5964 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-01-03 19:18:37 5964 [Note] InnoDB: Not using CPU crc32 instructions 2014-01-03 19:18:37 5964 [Note] InnoDB: Initializing buffer pool, size = 16.0M 2014-01-03 19:18:37 5964 [Note] InnoDB: Completed initialization of buffer pool 2014-01-03 19:18:37 5964 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1 2014-01-03 19:18:37 5964 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data! 2014-01-03 19:18:37 5964 [ERROR] Plugin 'InnoDB' init function returned error. 2014-01-03 19:18:37 5964 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2014-01-03 19:18:37 5964 [ERROR] Unknown/unsupported storage engine: InnoDB 2014-01-03 19:18:37 5964 [ERROR] Aborting Používám Win7, XAMPP 3.2.1. Jak s tím naložit? Nemůžu si udělat ani zálohu, když MySQL nejde vůbec spustit. |
||
Taps Profil |
#2 · Zasláno: 3. 1. 2014, 19:28:28
David Klouček:
port, je již něčím využíván a tak blokován, nemáš spuštěný skype ? Pokud ano tak ho zkus vypnout. |
||
David Klouček Profil |
#3 · Zasláno: 3. 1. 2014, 19:36:25
Vim, při tom ho mám vždy vyplej. Teď něco čtu o změně portu v my.ini, ale i tak to hází stejnou chybu.
|
||
abc Profil |
#4 · Zasláno: 3. 1. 2014, 19:41:32
Portem to imho nebude, MySQL obvykle využíva 3306, kdežto Skype (a Apache 80). Zkusil bych nějakou aktualizaci Xamppu
|
||
David Klouček Profil |
abc:
„Zkusil bych nějakou aktualizaci Xamppu“ Asi mi nic jinýho nezbyde. Ale jak ty data zálohovat? Upraveno: tak ne, nebudu těch pár tabulek, mam je to někde v bordelu uložený. Teď hlavně aby se to přirestartu nestalo zas. |
||
Davex Profil |
#6 · Zasláno: 3. 1. 2014, 20:38:42
David Klouček:
Vypadá to, že se nedaří otevřít InnoDB tablespace v souboru C:\xampp\mysql\data\ibdata1. Pokud máš data v MyISAM, tak se dá MySQL spustit bez podpory InnoDB (s přepínačem --skip-innodb nebo skip-innodb v my.ini) a data vyexportovat.
|
||
Časová prodleva: 4 měsíce
|
|||
Paulus Profil |
#7 · Zasláno: 10. 5. 2014, 08:37:57
Nainstaloval jsem si XAMPP (xampp-win32-1.8.3-0-VC11) přidám JOOMLA, spustím APACHE a Mysql vše funguje, webovou stránku mohu upravovat. Druhý den chci pokračovat, APACHE se spustí, ale Mysql ne!
Chybová hláška: 2014-05-10 08:12:40 5780 [Note] Plugin 'FEDERATED' is disabled. 2014-05-10 08:12:40 16bc 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-05-10 08:12:40 5780 [Note] InnoDB: The InnoDB memory heap is disabled 2014-05-10 08:12:40 5780 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2014-05-10 08:12:40 5780 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-05-10 08:12:40 5780 [Note] InnoDB: Not using CPU crc32 instructions 2014-05-10 08:12:40 5780 [Note] InnoDB: Initializing buffer pool, size = 16.0M 2014-05-10 08:12:40 5780 [Note] InnoDB: Completed initialization of buffer pool 2014-05-10 08:12:40 5780 [Note] InnoDB: Highest supported file format is Barracuda. 2014-05-10 08:12:40 5780 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3097440 in the ib_logfiles! 2014-05-10 08:12:40 5780 [Note] InnoDB: Database was not shutdown normally! 2014-05-10 08:12:40 5780 [Note] InnoDB: Starting crash recovery. 2014-05-10 08:12:40 5780 [Note] InnoDB: Reading tablespace information from the .ibd files... 2014-05-10 08:12:40 5780 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace digifoto/svfob_associations uses space ID: 2 at filepath: .\digifoto\svfob_associations.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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. Co je špatně!!! Už se mi to stalo několikrát. Pomohl jen reinstal XAMPP. Tím ztrácím veškeré úpravy stránek. |
||
Kajman Profil |
Jak spouštíte mysql server a hlavně jak ho vypínáte? Ručně nebo ukončujete automaticky službu při korektním vypínání počítače?
|
||
Paulus Profil |
Kajman:
Spouštím v XAMPP Control Panel klinutím na start. Ukončuji oběma způsoby. Jak kdy. |
||
jefitto44 Profil |
#10 · Zasláno: 13. 5. 2014, 14:20:51
Skús staršiu verziu, ak sa to dá niekde stiahnúť, alebo skús WAMP
|
||
Davex Profil |
#11 · Zasláno: 13. 5. 2014, 23:58:52
|
||
Časová prodleva: 10 let
|
0