felix.voir
Picopat
Daha fazla
- Cinsiyet
- Erkek
- Meslek
- Müzik prodüktörü
Selamlar. 1 aydır XAMPP uygulamasını kapatmaya çalıştığımda ilk görseldeki gibi hata alıyordum ve sonunda yanıt vermeyerek kapanıyordu. Bugün durduk yere mySQL sunucusu kapandı ve artık başlatılamıyor. Port değiştirerek başlatmayı denedim fakat olmadı. Çözümü bilen var mı?
Error log:
Error log:
Kod:
InnoDB: End of page dump
2020-12-26 0:57:20 0 [Note] InnoDB: Uncompressed page, stored checksum in field1 3802004516, calculated checksums for field1: crc32 3802004516, innodb 3354532414, page type 2 == UNDO LOG.none 3735928559, stored checksum in field2 3228898708, calculated checksums for field2: crc32 3802004516, innodb 1976599612, none 3735928559, page LSN 0 1021064, low 4 bytes of LSN at page end 2259400, page number (if stored to page already) 357, space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an undo log page
2020-12-26 0:57:20 0 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2020-12-26 0:57:20 0 [ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page.
201226 0:57:20 [ERROR] 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.
