phpMyAdmin / mySQL - puca na win11

[bozoou]

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:

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 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: xampp - How to solve "Error: MySQL shutdown unexpectedly"? - Stack Overflow 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 će netko imati volje pročitati uopće ovo.

[bozoou]

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:

Nešto je 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…

[igor]

@bozoou

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??

Kad si probavao ovaj fix, jesi li crashao nakon sto si naizmjenicno aktivirao XAMPP 7.4 i 8.2 ili si stalno koristio istu verziju?

Je li i dalje imas 2 razlicita mysql/data foldera, jedan za 7.4 i jedan za 8.2? Mislim da je problem sto te novije verzije XAMPPa vjerovatno koriste novi MariaDB/MySQL i da zbog toga ne moze ucitati stare datoteke, sto imas u logu:

[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.

Ja bih ti savjetovao da koristis jednu verziju XAMPPa (ako je uopce mozes fikisrati) i onda mijenjas PHP verziju po projektu, nisam probao ali sam vidio tutorial kako bi se trebalo konfigurirati:
https://mathewparker.co.uk/2021/04/running-multiple-php-versions-on-xampp/

[musliamar]

na windowsu 10/11 imas opciju windows subsystem for linux (WSL) … u okviru svog windowsa instaliras neku linux distribuciju i pokreces sve preko terminala te distribucije …

instaliras ubuntu, instaliras apache2 i mariadb, service apache2 start && service mariadb start … i pjevas

ja tako radim, pristupas localhostu kao i sa xampom, pristupas phpmyadminu kao i sa xampom, ima brdo tutorijala kako na ubuntuu koristiti vise php verzija, mozes VS code povezati sa tim WSLom …

razmisli o toj opciji, linux je mnogo stabilniji od tih xampp tweakova

[bozoou]

@igor

Kad si probavao ovaj fix, jesi li crashao nakon sto si naizmjenicno aktivirao XAMPP 7.4 i 8.2 ili si stalno koristio istu verziju?

Dok sam tek testirao fix, mogao sam se prešaltati … ali svaki puta je potrebno bilo fixati nakon promjene verzije.

@igor

Je li i dalje imas 2 razlicita mysql/data foldera, jedan za 7.4 i jedan za 8.2?

Imam potpuno dva različita xampp foldera …sve bi trebalo biti nezavisno, ali imaju negdje neku zajedničku točku koja ih crasha nakon zamjene xampp-a kojeg želim startati.
(Mislim, imao sam za vrijeme ovih problema … više nemam, morao sam za sada odustati od toga.)

@igor

Mislim da je problem sto te novije verzije XAMPPa vjerovatno koriste novi MariaDB/MySQL i da zbog toga ne moze ucitati stare datoteke, sto imas u logu:

Da, ali mi nije jasno gdje to sheraju zajedničke file-ove kada su instalirani nezavisno kao dva xampp foldera.
Meni se više čini kao da windows zabilježi koji program pristupa nekom portu ili čemu već … i onda kada uoči da drugi program pokušava proći kroz “ista ta vrata”, da ga onda blokira.

@igor

Ja bih ti savjetovao da koristis jednu verziju XAMPPa (ako je uopce mozes fikisrati) i onda mijenjas PHP verziju po projektu, nisam probao ali sam vidio tutorial kako bi se trebalo konfigurirati:

Probao sam već i velim, to mi je radilo na prijašnjim windowsima.
Ovako brzim preletom gornje metode mislim da ovo dolazi na isto kao kada sam ja mijenjao nazive folderima. (Isto rasprostranjena metoda) Ovdje kod tebe se samo mijenjaju nazivi u konfiguraciji na koji folder će gledati za pogonjenje PHP/appachea…trebalo bi doći na isto.

No nakon svih ovih problema, pokušao sam ja opet sa jednim folderom XAMPP-a i tako mijenjati nazive folderima i opet mi se skrši mySQL …nekako to fiksam i nakon toga mi vrisne nova greška.
Ovog puta se appache skrši i greška u suštini kaže istu stvar, samo ovog puta u kontekstu da je appache blokiran zbog…bla bla.

I vratim sve foldere na original i greška dalje vrišti za appache.
Zaključujem iz toga da očito nije greška u sustavu mySQL-a, pa niti tako u sustavu appache-a …nego je greška negdje izvanjska (do windowsa) da ih nakon izmjene iz nekog razloga blokira.

Iako vjerujem da je to neki mali fix da se kaže windowsima da podrže to, ja sam zapravo potpuno slijep kako bi to učinio …tako da zasad jednostavno odustajem od verzioniranja PHP-a.

Sve obrisao, instalirao samo XAMPP sa php 7.4 i radi stabilno.

[bozoou]

@musliamar

na windowsu 10/11 imas opciju windows subsystem for linux (WSL) … u okviru svog windowsa instaliras neku linux distribuciju i pokreces sve preko terminala te distribucije …

instaliras ubuntu, instaliras apache2 i mariadb, service apache2 start && service mariadb start … i pjevas

ja tako radim, pristupas localhostu kao i sa xampom, pristupas phpmyadminu kao i sa xampom, ima brdo tutorijala kako na ubuntuu koristiti vise php verzija, mozes VS code povezati sa tim WSLom …

razmisli o toj opciji, linux je mnogo stabilniji od tih xampp tweakova

Ovo će biti očito riješenje.

[rijo]

@bozoou

Ovo će biti očito riješenje.

Na šta čekaš onda, već si to par puta rekao, pa si još uvijek na windowsu
Kada se uhodaš i privikneš malo na neki linux distro, više te ništa neće natjerati da se vratiš na windows, osim ako nisi neki žešći gejmer, i preporučio bi ti Debian (desk verzija) od samog početka, to kada savladaš, poslije možeš testirati i ostale linux distribucije: ubuntu, fedora, alma, mint, opensuse, manjaro, elementary, zorin itd… imaš ih tonu…

[bozoou]

@rijo

Na šta čekaš onda, već si to par puta rekao, pa si još uvijek na windowsu

True, true … ma bit će, al nije goruće …hbga.
Upalo je u todo listu, ali sortiranje/favoriziranje mojih todo lista je zamršenije i od samih Windowsa

[adr1]

probaj zamijeniti xaamp sa laragonom ako vec nisi fixao

[bozoou]

mm…bmti ledinu …vrisnuo je opet, a bez da sam išta ovog puta dirao. Znači imam clean instalaciju i nisam ama baš ništa mijenjao. (Osim naravno izmjena u htdocs folderu)

I radilo je nekoliko paljenja/gašenja računala … i evo noćas opet ugasim računalo i ujutro ne radi…greška ista:

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

…više se neću bojati updejta na windowsima, nego i svakog gašenja računala

@bozoou

Upalo je u todo listu, ali sortiranje/favoriziranje mojih todo lista je zamršenije i od samih Windowsa

Čini se da ak nemrem razmrsit Windowse, da ću silom prilike morat razmrsit svoju todo listu, heh.

[bozoou]

@musliamar

na windowsu 10/11 imas opciju windows subsystem for linux (WSL) … u okviru svog windowsa instaliras neku linux distribuciju i pokreces sve preko terminala te distribucije …

instaliras ubuntu, instaliras apache2 i mariadb, service apache2 start && service mariadb start … i pjevas

Gledam neki tutorijal: Windows Subsystem for Linux (WSL) Tutorial & How To - YouTube … sve brdo nekih terminal instrukcija …

Jesam li dobro shvatio …kroz terminal linuxa instaliram navedeno za apache/mariadb i onda sam slobodan od terminala i dalje radim kao i dosada?

[bozoou]

@adr1

probaj zamijeniti xaamp sa laragonom ako vec nisi fixao

Laragon se čini zanimljiv. Hvala ti na ovome… čini se da ostajem vjeran nevjernim Windowsima xd

[musliamar]

@bozoou

kroz terminal linuxa instaliram navedeno za apache/mariadb i onda sam slobodan od terminala i dalje radim kao i dosada?

kada podesis apache i mariadb, sajtove dodajes u /var/www/ a phpmyadmin koristis kao i sa xampom

preko xampa apache i mysql pokreces preko xamp control panela klikom na Start dugme a preko WSL-a pokreces tako sto kucas service apache2 start && service mariadb start

trazi tutorijale how to install LAMP in ubuntu, how to use lamp locally, install lamp stack on WSL i slicne kombinacije

[jorgovan]

skini mysql posebno, instaliraj i radit će ti.
Za php razvoj, linux no. 1.
Preporuka za postgresql.