3. Mysql Can't Start Reason: Can't Create Test File C:\laragon\data\mysql\???.lower-test

Mysql Can't Start Reason: Can't Create Test File C:\laragon\data\mysql\???.lower-test

  • | 1926 points

    Hi,
    I have recently Installed laragon 4.0.15 on windows 10 and when i start the servers Apache works fine but for MySQL i get this error message saying MySQL can't start reason Can't create test file C:\laragon\data\mysql???.lower-test,:confused:
    Now What's causing this error???:thinking:
    I've set full permission to C:\laragon Folder It still doesn't work, then i completely removed it and installed it again on (D:) Drive Still doesn't seem to work.....
    any Help????? :pray: :pray_tone1: :pray_tone5: 0_1573999310539_mysql_error.PNG

    0
  • administrators
    | 131258 points

    Hi @gecha ,
    What's your OS language?
    Can you change the language to English?

    0
  • | 1926 points

    well thanks @leokhoa for the reply but I've been using English as my default language and it still is,
    here is the log i get with MySQL v5.7.24 X64
    2019-11-18T10:19:23.062299Z 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
    2019-11-18T10:19:23.062650Z 0 [Note] C:\laragon\bin\mysql\mysql-5.7.24-winx64\bin\mysqld (mysqld 5.7.24) starting as process 1352 ...
    2019-11-18T10:19:23.067012Z 0 [Warning] Can't create test file C:\laragon\data\mysql???.lower-test

    2019-11-18T10:19:23.067399Z 0 [Warning] Can't create test file C:\laragon\data\mysql???.lower-test
    2019-11-18T10:19:32.099069Z 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
    2019-11-18T10:19:32.099524Z 0 [Note] C:\laragon\bin\mysql\mysql-5.7.24-winx64\bin\mysqld (mysqld 5.7.24) starting as process 4120 ...
    2019-11-18T10:19:32.102632Z 0 [Warning] Can't create test file C:\laragon\data\mysql???.lower-test
    2019-11-18T10:19:32.102885Z 0 [Warning] Can't create test file C:\laragon\data\mysql???.lower-test
    2019-11-18T10:19:32.119610Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
    2019-11-18T10:19:32.120097Z 0 [Note] InnoDB: Uses event mutexes
    2019-11-18T10:19:32.120350Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
    2019-11-18T10:19:32.120707Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
    2019-11-18T10:19:32.121231Z 0 [Note] InnoDB: Number of pools: 1
    2019-11-18T10:19:32.121581Z 0 [Note] InnoDB: Not using CPU crc32 instructions
    2019-11-18T10:19:32.123734Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
    2019-11-18T10:19:32.129498Z 0 [Note] InnoDB: Completed initialization of buffer pool
    2019-11-18T10:19:32.207161Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
    2019-11-18T10:19:32.224631Z 0 [ERROR] InnoDB: Upgrade after a crash is not supported. This redo log was created before MySQL 5.7.9. Please follow the instructions at http://dev.mysql.com/doc/refman/5.7/en/upgrading.html
    2019-11-18T10:19:32.225457Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
    2019-11-18T10:19:32.443360Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
    2019-11-18T10:19:32.443821Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    2019-11-18T10:19:32.444202Z 0 [ERROR] Failed to initialize builtin plugins.
    2019-11-18T10:19:32.444498Z 0 [ERROR] Aborting

    2019-11-18T10:19:32.444695Z 0 [Note] Binlog end
    2019-11-18T10:19:32.444912Z 0 [Note] Shutting down plugin 'CSV'
    2019-11-18T10:19:32.449783Z 0 [Note] C:\laragon\bin\mysql\mysql-5.7.24-winx64\bin\mysqld: Shutdown complete

    And With MySQL V5.6.17 X64

    2019-11-18 13:47:41 8128 [Note] Plugin 'FEDERATED' is disabled.
    2019-11-18 13:47:41 8128 [Note] InnoDB: Using atomics to ref count buffer pool pages
    2019-11-18 13:47:41 8128 [Note] InnoDB: The InnoDB memory heap is disabled
    2019-11-18 13:47:41 8128 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
    2019-11-18 13:47:41 8128 [Note] InnoDB: Compressed tables use zlib 1.2.3
    2019-11-18 13:47:41 8128 [Note] InnoDB: Not using CPU crc32 instructions
    2019-11-18 13:47:41 8128 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    2019-11-18 13:47:41 8128 [Note] InnoDB: Completed initialization of buffer pool
    2019-11-18 13:47:41 8128 [Note] InnoDB: Highest supported file format is Barracuda.
    2019-11-18 13:47:41 8128 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1625977
    2019-11-18 13:47:41 8128 [Note] InnoDB: Database was not shutdown normally!
    2019-11-18 13:47:41 8128 [Note] InnoDB: Starting crash recovery.
    2019-11-18 13:47:41 8128 [Note] InnoDB: Reading tablespace information from the .ibd files...
    2019-11-18 13:47:42 8128 [Note] InnoDB: Restoring possible half-written data pages
    2019-11-18 13:47:42 8128 [Note] InnoDB: from the doublewrite buffer...
    InnoDB: Doing recovery: scanned up to log sequence number 1626057
    2019-11-18 13:47:42 8128 [Note] InnoDB: 128 rollback segment(s) are active.
    2019-11-18 13:47:43 8128 [Note] InnoDB: Waiting for purge to start
    2019-11-18 13:47:43 8128 [Note] InnoDB: 5.6.17 started; log sequence number 1626057
    2019-11-18 13:47:43 8128 [Note] Server hostname (bind-address): ''; port: 3306
    2019-11-18 13:47:43 8128 [Note] IPv6 is available.
    2019-11-18 13:47:43 8128 [Note] - '::' resolves to '::';
    2019-11-18 13:47:43 8128 [Note] Server socket created on IP: '::'.
    2019-11-18 13:47:51 7036 [Note] Plugin 'FEDERATED' is disabled.
    2019-11-18 13:47:51 7036 [Note] InnoDB: Using atomics to ref count buffer pool pages
    2019-11-18 13:47:51 7036 [Note] InnoDB: The InnoDB memory heap is disabled
    2019-11-18 13:47:51 7036 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
    2019-11-18 13:47:51 7036 [Note] InnoDB: Compressed tables use zlib 1.2.3
    2019-11-18 13:47:51 7036 [Note] InnoDB: Not using CPU crc32 instructions
    2019-11-18 13:47:51 7036 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    2019-11-18 13:47:51 7036 [Note] InnoDB: Completed initialization of buffer pool
    2019-11-18 13:47:51 7036 [Note] InnoDB: Highest supported file format is Barracuda.
    2019-11-18 13:47:51 7036 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1625977
    2019-11-18 13:47:51 7036 [Note] InnoDB: Database was not shutdown normally!
    2019-11-18 13:47:51 7036 [Note] InnoDB: Starting crash recovery.
    2019-11-18 13:47:51 7036 [Note] InnoDB: Reading tablespace information from the .ibd files...
    2019-11-18 13:47:52 7036 [Note] InnoDB: Restoring possible half-written data pages
    2019-11-18 13:47:52 7036 [Note] InnoDB: from the doublewrite buffer...
    InnoDB: Doing recovery: scanned up to log sequence number 1626067
    2019-11-18 13:47:52 7036 [Note] InnoDB: 128 rollback segment(s) are active.
    2019-11-18 13:47:52 7036 [Note] InnoDB: Waiting for purge to start
    2019-11-18 13:47:52 7036 [Note] InnoDB: 5.6.17 started; log sequence number 1626067
    2019-11-18 13:47:52 7036 [Note] Server hostname (bind-address): '    '; port: 3306
    2019-11-18 13:47:52 7036 [Note] IPv6 is available.
    2019-11-18 13:47:52 7036 [Note] - '::' resolves to '::';
    2019-11-18 13:47:52 7036 [Note] Server socket created on IP: '::'.
    2019-11-18 13:47:52 7036 [ERROR] C:\laragon\bin\mysql\mysql-5.6.17-winx64\bin\mysqld: Can't create/write to file 'C:\laragon\data\mysql???.pid' (Errcode: 22 - Invalid argument)
    2019-11-18 13:47:52 7036 [ERROR] Can't start server: can't create PID file: Invalid argument

    0
  • administrators
    | 131258 points

    @gecha : Strange. Why the filename is ???.lower-test?

    0 Replies: 1
  • | 1926 points

    @leokhoa anyways i tried it with mariadb and it's working......After some googling i found out it's more of Windows vs MySQL Issue ...

    0
Log in to reply
 

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