Windows

PhpMyAdmin / mySQL - puca na win11

bozoou pet 14.10.2022 09:07

Pozdrav,

iako ovo moguće nije problem win11, no otkako sam na 11-ici non stop mi puca mySQL...sruši se i više se ne želi pokrenuti uz sljedeću grešku: slika prilog

U mysql_error.log kaže:


2022-10-14 8:32:27 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2022-10-14 8:32:27 0 [Note] InnoDB: Uses event mutexes
2022-10-14 8:32:27 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-10-14 8:32:27 0 [Note] InnoDB: Number of pools: 1
2022-10-14 8:32:27 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-10-14 8:32:27 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2022-10-14 8:32:27 0 [Note] InnoDB: Completed initialization of buffer pool
2022-10-14 8:32:27 0 [Note] InnoDB: The log sequence number 168283006 in the system tablespace does not match the log sequence number 168283015 in the ib_logfiles!
2022-10-14 8:32:27 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=3023, page number=2348] with future log sequence number 2998537016
2022-10-14 8:32:27 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=3023, page number=1894] with future log sequence number 2998997250
2022-10-14 8:32:27 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=3023, page number=1992] with future log sequence number 2998869661
2022-10-14 8:32:27 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=3023, page number=6832] with future log sequence number 3244546478
2022-10-14 8:32:27 0 [ERROR] InnoDB: Page [page id: space=0, page number=3] log sequence number 876006155 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:27 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:27 0 [ERROR] InnoDB: Page [page id: space=0, page number=356] log sequence number 1140254502 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:27 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:27 0 [ERROR] InnoDB: Page [page id: space=0, page number=451] log sequence number 1167407819 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:27 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:27 0 [ERROR] InnoDB: Page [page id: space=0, page number=381] log sequence number 1165473204 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:27 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:27 0 [ERROR] InnoDB: Page [page id: space=0, page number=333] log sequence number 1170684834 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:27 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:28 0 [ERROR] InnoDB: Page [page id: space=0, page number=334] log sequence number 1185348274 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:28 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:28 0 [ERROR] InnoDB: Page [page id: space=0, page number=452] log sequence number 1173585983 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:28 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:28 0 [ERROR] InnoDB: Page [page id: space=0, page number=389] log sequence number 1181060715 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:28 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:28 0 [ERROR] InnoDB: Page [page id: space=0, page number=340] log sequence number 2933947749 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:28 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:30 0 [ERROR] InnoDB: Page [page id: space=0, page number=407] log sequence number 2578436119 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:30 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Page [page id: space=0, page number=383] log sequence number 1168013344 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Page [page id: space=0, page number=413] log sequence number 1171232195 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Page [page id: space=0, page number=415] log sequence number 1174844775 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Page [page id: space=0, page number=450] log sequence number 1180313252 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Page [page id: space=0, page number=458] log sequence number 1190609393 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Page [page id: space=0, page number=485] log sequence number 1206225125 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Page [page id: space=0, page number=508] log sequence number 3307416380 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Page [page id: space=0, page number=479] log sequence number 3307416380 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-10-14 8:32:31 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-10-14 8:32:31 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-10-14 8:32:31 0 [Note] InnoDB: Setting file 'C:\xampp_7.4\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-10-14 8:32:31 0 [Note] InnoDB: File 'C:\xampp_7.4\mysql\data\ibtmp1' size is now 12 MB.
2022-10-14 8:32:31 0 [Note] InnoDB: Waiting for purge to start
2022-10-14 8:32:31 3 [ERROR] InnoDB: Page [page id: space=0, page number=418] log sequence number 1176073609 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 1 [ERROR] InnoDB: Page [page id: space=0, page number=439] log sequence number 3307880224 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 2 [ERROR] InnoDB: Page [page id: space=3002, page number=0] log sequence number 2934641811 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 2 [ERROR] InnoDB: Page [page id: space=0, page number=363] log sequence number 3287492375 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 2 [ERROR] InnoDB: Page [page id: space=3002, page number=1] log sequence number 2934641480 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 1 [ERROR] InnoDB: Page [page id: space=3070, page number=0] log sequence number 3292266189 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 1 [ERROR] InnoDB: Page [page id: space=3070, page number=3] log sequence number 3292267266 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 1 [ERROR] InnoDB: Page [page id: space=3070, page number=1] log sequence number 3292266556 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 2 [ERROR] InnoDB: Page [page id: space=3136, page number=0] log sequence number 3306691782 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 2 [ERROR] InnoDB: Page [page id: space=3136, page number=1] log sequence number 3306691782 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 0 [Note] InnoDB: 10.4.25 started; log sequence number 168283015; transaction id 1263010
2022-10-14 8:32:31 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp_7.4\mysql\data\ib_buffer_pool
2022-10-14 8:32:31 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Page [page id: space=0, page number=309] log sequence number 2592064185 is in the future! Current system log sequence number 168283024.
2022-10-14 8:32:31 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-10-14 8:32:31 0 [Note] InnoDB: Buffer pool(s) load completed at 221014 8:32:31
2022-10-14 8:32:31 0 [Note] Server socket created on IP: '::'.

 

Ono što bi mi najviše pomoglo je ako ima način da se exportaju baze čisto kopiranjem nekih foldera (bez phpMyAdmina) ...i ako bi se na isti način mogle importati u novu instalaciju xamppa. Jerbo taj phpMyAdmin jednostavno ne zna na importu progutati veće file-ove bez masu popratnih problema...


...
...
E sad, long story ... kako me zadesio ovaj problem...

Prije sam uobičajavao imati više php verzija u xampp folderu i onda bi po potrebi aktivirao željenu php verziju. Imao bi duple foldere php & appache i onda bi samo sa promjenom imena foldera uključio one koje želim. To je radilo na win8 za par php5.6 i php7.4

Sada na win11 to nije radilo za par php7.4 i php.8.2. Upravo mySQL komponenta nije htjela raditi...pa sam tako ubacio i dupli folder mySQL pored postojećih php&appache foldera.
Nakon toga mi je vrištala ova mySQL greška.
Zatim nakon što sam vratio sve originalne foldere php/appache/mySQL ..ta greška je i dalje vrištala.

Nije bilo drugoga nego reinstalacija XAMPP sa ponovnim užasno mukotrpnim importom svih baza u phpMyAdmin.

Pošto sam i dalje htio imati php7 i php8 ..ovog puta sam instalirao dva XAMPP-a, po jedan za svaku php verziju.
No desio se isti problem:
1. Aktiviram xampp 7.4 control panel -> mySQL uredno radi
2. Ugasim 7.4 i aktiviram xampp 8.2 control panel -> mySQL uredno radi
3. Ugasim 8.2 i aktiviram xampp 7.4 i opet lupim u istu mySQL grešku, koji više ne želi raditi

 

E sad, pošto me phpMyAdmin ubije od pucanja dok importam sve baze/podatke ... tražio sam soluciju problemu bez da moram reinstalirati opet xampp. Usto, reinstalacija nebi bila rješenje problema da mogu upogoniti različite verzije php-a.

Zguglam uglavnom ovu metodu: https://stackoverflow.com/questions/18022809/how-to-solve-error-mysql-shutdown-unexpectedly i to je u suštini radilo. Konkretno ovaj dio:

> 1. Rename folder `mysql/data` to `mysql/data_old`
> 2. Make a copy of `mysql/backup` folder and name it as `mysql/data`
> 3. Copy all your database folders from `mysql/data_old` into `mysql/data` (except `mysql`, `performance_schema`, and `phpmyadmin` folders)
> 4. Copy `mysql/data_old/ibdata1` file into `mysql/data` folder
> 5. Start MySQL from XAMPP control panel

Taj fix je uglavnom radio.

 

I sada mi dođe mili automatski win update ... i nakon toga mySQL zakuca opet u istu grešku.
Napravim ovaj fix i proradi samo na tren i opet se skrši.
Ponovim fix, ali se opet skrši...

 

What the heck is going here??

 

Ako netko ima ikakvu ideju zbog čega se buni mySQL.

Neka logika mi kaže da mora biti neki vanjski zajednički file na kojem ostavljaju nekakav svoj "fingerprint" ... i kada drugi xampp/mySQL takne taj file, onda prethodni mySQL vrisne. Također je i win update očito uspio zmrdati taj file... 

 

Ono što bi bila utopija ... da mogu nekako dislocirati mySQL folder ...pa da i xampp7.4 i xampp 8.2 se referiraju prema istom mySQL folderu gdje su baze podataka.

bozoou pet 14.10.2022 09:47

Pošto se problem pojavljivao i na dvije nezavisne xampp instance ... odlučio sam se vratiti na jednu i šaltati php verziju spomenutom "rename" metodom.

Na svježe instaliran xampp 8.2 ubacim foldere php & appache od 7.4 verzije.

1. Probam startati php7 - uredno sve radi
2. Probam startati php8 - uredno sve radi
3. Probam opet startati php 7 - vojla, uredno sve radi. Pomislih, ovog problema više neću možda imati.

4. Dodam ručno jednu bazu kroz phpMyAdmin .. napravim kroz program neke izmjene na toj bazi...
5. Ugasim appache/mySQL kroz xampp control panel
6. Probam opet startati php 7 - i evo ga greške natrag.

 

 

 

Ovog puta ipak drugačiji error log u ovoj varijanti provociranja greške:

 


2022-10-14 9:34:31 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2022-10-14 9:34:31 0 [Note] InnoDB: Uses event mutexes
2022-10-14 9:34:31 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-10-14 9:34:31 0 [Note] InnoDB: Number of pools: 1
2022-10-14 9:34:31 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-10-14 9:34:31 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2022-10-14 9:34:31 0 [Note] InnoDB: Completed initialization of buffer pool
2022-10-14 9:34:31 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=3045895503
2022-10-14 9:34:31 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-10-14 9:34:31 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-10-14 9:34:31 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-10-14 9:34:31 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-10-14 9:34:31 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2022-10-14 9:34:31 0 [Note] InnoDB: Waiting for purge to start
2022-10-14 9:34:31 0 [Note] InnoDB: 10.4.25 started; log sequence number 3045895512; transaction id 91536
2022-10-14 9:34:31 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2022-10-14 9:34:31 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-10-14 9:34:31 0 [Note] Server socket created on IP: '::'.

 

Rekao bih da je ovo kvalitetniji error log, jer ovdje se sada radi baš o svježoj xampp instanci, bez ikakvih prethodnih fix-eva niti ičega..

Što ga to muči? Hmm...