MariaDB can not start.


  • | 956 points

    Everything has been running fine for a long time, last time was yesterday. This morning I get this error. I have read quite a few threads here, but have not been able to figure it out. I have been running Laragon 4.0.16 and MariaDB 10.0.30-winx64.

    Any help would be appreciated. I know WordPress but not databases. TYIA.

    The log shows this:
    200529 10:45:20 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    200529 10:45:20 [Note] InnoDB: The InnoDB memory heap is disabled
    200529 10:45:20 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
    200529 10:45:20 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
    200529 10:45:20 [Note] InnoDB: Compressed tables use zlib 1.2.3
    200529 10:45:20 [Note] InnoDB: Not using CPU crc32 instructions
    200529 10:45:20 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    200529 10:45:20 [Note] InnoDB: Completed initialization of buffer pool
    200529 10:45:20 [Note] InnoDB: Highest supported file format is Barracuda.
    InnoDB: Transaction 1515455 was in the XA prepared state.
    InnoDB: 1 transaction(s) which must be rolled back or cleaned up
    InnoDB: in total 0 row operations to undo
    InnoDB: Trx id counter is 1526528
    200529 10:45:20 [Note] InnoDB: 128 rollback segment(s) are active.
    InnoDB: Starting in background the rollback of uncommitted transactions
    2020-05-29 10:45:20 4698 InnoDB: Rollback of non-prepared transactions completed
    200529 10:45:20 [Note] InnoDB: Waiting for purge to start
    200529 10:45:20 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 627393387
    200529 10:45:20 [Note] Plugin 'FEEDBACK' is disabled.
    2020-05-29 10:45:20 470c InnoDB: Starting recovery for XA transactions...
    2020-05-29 10:45:20 470c InnoDB: Transaction 1515455 in prepared state after recovery
    2020-05-29 10:45:20 470c InnoDB: Transaction contains changes to 1 rows
    2020-05-29 10:45:20 470c InnoDB: 1 transactions in prepared state after recovery
    200529 10:45:20 [Note] Found 1 prepared transaction(s) in InnoDB
    200529 10:45:20 [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.
    200529 10:45:20 [ERROR] Aborting

    200529 10:45:20 [Note] InnoDB: FTS optimize thread exiting.
    200529 10:45:20 [Note] InnoDB: Starting shutdown...
    200529 10:45:21 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
    200529 10:45:23 [Note] InnoDB: Shutdown completed; log sequence number 627393397
    200529 10:45:23 [Note] C:\laragon\bin\mysql\mariadb-10.0.30-winx64\bin\mysqld: Shutdown complete


  • administrators
    | 123538 points

    @Mikek: No worries. The ERROR message is straightforward:

    200529 10:45:20 [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.

    You can open Laragon's terminal and type this:

    mysqld --tc-heuristic-recover=ROLLBACK
    
    

    Ref: https://forum.laragon.org/topic/371/database-is-not-working-error-2002/4


  • | 956 points

    Thank you but didn't work. When I run that it shows [Note] (mysqld 10.0.30-MariaDB) starting as process 19616 ...
    And then nothing.
    screenshot


  • administrators
    | 123538 points

    @Mikek : That's show MariaDB running OK. Then, you can stop it and start Laragon again.


Log in to reply
 

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