MariaDb suddenly the service shuts down
-
how check error ?
-
@atma-negara : What's your Laragon's version?
Normally, there is a log file in: C:\laragon\data\mariadb\mysqld.log
-
laragon 3.3.2 180730
log mariadb
2018-10-29 11:33:29 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-10-29 11:33:29 0 [Note] InnoDB: Uses event mutexes
2018-10-29 11:33:29 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-10-29 11:33:29 0 [Note] InnoDB: Number of pools: 1
2018-10-29 11:33:29 0 [Note] InnoDB: Using SSE2 crc32 instructions
2018-10-29 11:33:29 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-10-29 11:33:29 0 [Note] InnoDB: Completed initialization of buffer pool
2018-10-29 11:33:29 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=7113624169
2018-10-29 11:33:29 0 [Note] InnoDB: Last binlog file '.\mysql-bin.000083', position 5755
2018-10-29 11:33:46 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2018-10-29 11:33:46 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-10-29 11:33:46 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-10-29 11:33:46 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-10-29 11:33:46 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
2018-10-29 11:33:46 0 [Note] InnoDB: Waiting for purge to start
2018-10-29 11:33:46 0 [Note] InnoDB: 10.3.10 started; log sequence number 7113624178; transaction id 3816135
2018-10-29 11:33:46 0 [Note] InnoDB: Loading buffer pool(s) from F:\laragon\data\mariadb\mariadb\ib_buffer_pool
2018-10-29 11:33:46 0 [Note] Recovering after a crash using mysql-bin
2018-10-29 11:33:46 0 [Note] Starting crash recovery...
2018-10-29 11:33:46 0 [Note] Crash recovery finished.
2018-10-29 11:33:47 0 [Note] Server socket created on IP: '::'.
-
up, help me
-
@atma-negara : If you can not fix from the log file, you can rename
C:\data\mariadb
toC:\data\mariadb.bak
?
Laragon will start with new refresh data.