since last friday - mysql and mariadb won't start anymore


  • | 832 points

    Hello in the round and good morning...

    Last Friday I shut down my machine with win 10x64 prof 19041.985 and laragon normally after work. On Monday morning laragon no longer starts. to be more precise, the db server no longer starts. I am also unable to fix the error or find the cause.

    I tried the following

    1. I tried to install a new db server version, (before that, mysql 5.7.24 and mariadb 10.5.9 was running properly), i've installed mysql 8.0.25 from zip -> without success
    2. i've installed new mariadb 10.5.10 from zip ->without success
    3. I followed these steps: https://forum.laragon.org/topic/1884/new-install-of-laragon-mysql-fails-after-a-few-seconds-on-startup ->no result
    4. I ran sfc /scannow ->there were a few errors
    5. I ran dsim ->with success
    6. I ran sfc again ->no errors
    7. I've installed mariadb 10.5.10 from zip -> no sucess
    8. I've removed the whole data folder -> no success
    9. I ran mysqld --tc-heuristic-recover=COMMIT -> no success
    10. I ran mysqld --tc-heuristic-recover=ROLLBACK -> no success

    I am getting these errors at any time:
    2021-06-01 6:44:23 0 [ERROR] Aborting
    2021-06-01 6:44:32 0 [Note] InnoDB: Uses event mutexes
    2021-06-01 6:44:32 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
    2021-06-01 6:44:32 0 [Note] InnoDB: Number of pools: 1
    2021-06-01 6:44:32 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
    2021-06-01 6:44:32 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
    2021-06-01 6:44:32 0 [Note] InnoDB: Completed initialization of buffer pool
    2021-06-01 6:44:32 0 [Note] InnoDB: Transaction 32504 was in the XA prepared state.
    2021-06-01 6:44:32 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo
    2021-06-01 6:44:32 0 [Note] InnoDB: Trx id counter is 32505
    2021-06-01 6:44:32 0 [Note] InnoDB: 128 rollback segments are active.
    2021-06-01 6:44:32 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
    2021-06-01 6:44:32 0 [Note] InnoDB: Rollback of non-prepared transactions completed
    2021-06-01 6:44:32 0 [Note] InnoDB: Creating shared tablespace for temporary tables
    2021-06-01 6:44:32 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
    2021-06-01 6:44:32 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
    2021-06-01 6:44:32 0 [Note] InnoDB: 10.5.10 started; log sequence number 450837383; transaction id 32506
    2021-06-01 6:44:32 0 [Note] Plugin 'FEEDBACK' is disabled.
    2021-06-01 6:44:32 0 [Note] InnoDB: Starting recovery for XA transactions...
    2021-06-01 6:44:32 0 [Note] InnoDB: Transaction 32504 in prepared state after recovery
    2021-06-01 6:44:32 0 [Note] InnoDB: Transaction contains changes to 1 rows
    2021-06-01 6:44:32 0 [Note] InnoDB: 1 transactions in prepared state after recovery
    2021-06-01 6:44:32 0 [Note] Found 1 prepared transaction(s) in InnoDB
    2021-06-01 6:44:32 0 [ERROR] Found 1 prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or tc.log file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.
    2021-06-01 6:44:32 0 [ERROR] Aborting

    can enybody help me?
    best regards theo


  • administrators
    | 131371 points

    @cmette : If you did step 8, Laragon will start MySQL with a fresh datadir so I wonder why it did not work for you.


Log in to reply
 

Looks like your connection to Laragon was lost, please wait while we try to reconnect.