Forum » Programiranje » XAMPP - mysql
XAMPP - mysql
Ales47 ::
pozdrav, formatiral sem računalnik in sem prej namestil XAMPP. zdaj pa mi javi ven ko hočem zagnat mySQL :
14:02:53 [mysql] Error: MySQL shutdown unexpectedly.
14:02:53 [mysql] This may be due to a blocked port, missing dependencies,
14:02:53 [mysql] improper privileges, a crash, or a shutdown by another method.
14:02:53 [mysql] Press the Logs button to view error logs and check
14:02:53 [mysql] the Windows Event Viewer for more clues
14:02:53 [mysql] If you need more help, copy and post this
14:02:53 [mysql] entire log window on the forums
v čem je problem?
lp hvala
14:02:53 [mysql] Error: MySQL shutdown unexpectedly.
14:02:53 [mysql] This may be due to a blocked port, missing dependencies,
14:02:53 [mysql] improper privileges, a crash, or a shutdown by another method.
14:02:53 [mysql] Press the Logs button to view error logs and check
14:02:53 [mysql] the Windows Event Viewer for more clues
14:02:53 [mysql] If you need more help, copy and post this
14:02:53 [mysql] entire log window on the forums
v čem je problem?
lp hvala
Ryzen 7 5800X3D|Aorus X570|32GB KINGSTON DDR4|RTX 3080|250GB SSD Samsung|2TB
Ales47 ::
sem probal in isto.... tukaj error log:
018-12-03 14:13:01 152c 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.
2018-12-03 14:13:01 5420 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2018-12-03 14:13:01 5420 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-12-03 14:13:01 5420 [Note] InnoDB: The InnoDB memory heap is disabled
2018-12-03 14:13:01 5420 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-12-03 14:13:01 5420 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-12-03 14:13:01 5420 [Note] InnoDB: Compressed tables use zlib 1.2.11
2018-12-03 14:13:01 5420 [Note] InnoDB: Using generic crc32 instructions
2018-12-03 14:13:01 5420 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-12-03 14:13:01 5420 [Note] InnoDB: Completed initialization of buffer pool
2018-12-03 14:13:01 5420 [Note] InnoDB: Restoring page 0 of tablespace 0
2018-12-03 14:13:01 5420 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2018-12-03 14:13:01 5420 [ERROR] InnoDB: space header page consists of zero bytes in data file D:\xampp\mysql\data\ibdata1
2018-12-03 14:13:01 5420 [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!
2018-12-03 14:13:01 5420 [ERROR] Plugin 'InnoDB' init function returned error.
2018-12-03 14:13:01 5420 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-12-03 14:13:01 5420 [Note] Plugin 'FEEDBACK' is disabled.
2018-12-03 14:13:01 5420 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2018-12-03 14:13:01 5420 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-12-03 14:13:01 5420 [ERROR] Aborting
018-12-03 14:13:01 152c 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.
2018-12-03 14:13:01 5420 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2018-12-03 14:13:01 5420 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-12-03 14:13:01 5420 [Note] InnoDB: The InnoDB memory heap is disabled
2018-12-03 14:13:01 5420 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-12-03 14:13:01 5420 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-12-03 14:13:01 5420 [Note] InnoDB: Compressed tables use zlib 1.2.11
2018-12-03 14:13:01 5420 [Note] InnoDB: Using generic crc32 instructions
2018-12-03 14:13:01 5420 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-12-03 14:13:01 5420 [Note] InnoDB: Completed initialization of buffer pool
2018-12-03 14:13:01 5420 [Note] InnoDB: Restoring page 0 of tablespace 0
2018-12-03 14:13:01 5420 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2018-12-03 14:13:01 5420 [ERROR] InnoDB: space header page consists of zero bytes in data file D:\xampp\mysql\data\ibdata1
2018-12-03 14:13:01 5420 [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!
2018-12-03 14:13:01 5420 [ERROR] Plugin 'InnoDB' init function returned error.
2018-12-03 14:13:01 5420 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-12-03 14:13:01 5420 [Note] Plugin 'FEEDBACK' is disabled.
2018-12-03 14:13:01 5420 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2018-12-03 14:13:01 5420 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-12-03 14:13:01 5420 [ERROR] Aborting
Ryzen 7 5800X3D|Aorus X570|32GB KINGSTON DDR4|RTX 3080|250GB SSD Samsung|2TB
Tr0n ::
Ni isto, sedaj vidis pravi 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!
To naredi I guess. Nekaj se ti je pokvarlo ali ni prav nastavljeno.
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!
To naredi I guess. Nekaj se ti je pokvarlo ali ni prav nastavljeno.
Ales47 ::
ja to v xampu se itak vrze isti error... to sem zdaj pod error log pogledal..
Ryzen 7 5800X3D|Aorus X570|32GB KINGSTON DDR4|RTX 3080|250GB SSD Samsung|2TB
Ales47 ::
ok problem rešen... naložil prešnjo verzijo in deluje. hvala vseeno;)
Ryzen 7 5800X3D|Aorus X570|32GB KINGSTON DDR4|RTX 3080|250GB SSD Samsung|2TB
illion ::
pa si pogledal tud kaj o migriranju na novejso verijo, al pa recimo dump podatkov in potem clean install novejse verzije ter import podatkov? men se zdi ostajanje na starih verzijah bl slaba odlocitev za tvoj primer.
Vredno ogleda ...
Tema | Ogledi | Zadnje sporočilo | |
---|---|---|---|
Tema | Ogledi | Zadnje sporočilo | |
» | myslq poizvedba več kot sekundoOddelek: Programiranje | 765 (592) | biasko |
» | MySQL RelacijeOddelek: Izdelava spletišč | 1124 (890) | mkos2 |
» | MySql Vprasanje - problem dupliciranih kljucevOddelek: Izdelava spletišč | 1447 (1269) | KernelPanic |
» | Sun Microsystems prevzema MySQL ABOddelek: Novice / Nakupi / združitve / propadi | 6013 (4108) | Bistri007 |
» | Backup podatkovnih bazOddelek: Omrežja in internet | 2174 (1802) | jype |