Alert

  • Creator
    Topic
  • #4151862

    XAMPP

    by maheshjadhav03200 ·

    2023-07-25 0:27:30 0 [Note] Starting MariaDB 10.4.28-MariaDB source revision c8f2e9a5c0ac5905f28b050b7df5a9ffd914b7e7 as process 19316
    2023-07-25 0:27:30 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
    2023-07-25 0:27:30 0 [Note] InnoDB: Uses event mutexes
    2023-07-25 0:27:30 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
    2023-07-25 0:27:30 0 [Note] InnoDB: Number of pools: 1
    2023-07-25 0:27:30 0 [Note] InnoDB: Using SSE2 crc32 instructions
    2023-07-25 0:27:30 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
    2023-07-25 0:27:30 0 [Note] InnoDB: Completed initialization of buffer pool
    2023-07-25 0:27:30 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300288
    2023-07-25 0:27:30 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
    2023-07-25 0:27:30 0 [Note] InnoDB: Removed temporary tablespace data file: “ibtmp1”
    2023-07-25 0:27:30 0 [Note] InnoDB: Creating shared tablespace for temporary tables
    2023-07-25 0:27:30 0 [Note] InnoDB: Setting file ‘C:\Users\Rupesh Jadhav\Downloads\MJ\mysql\data\ibtmp1’ size to 12 MB. Physically writing the file full; Please wait …
    2023-07-25 0:27:30 0 [Note] InnoDB: File ‘C:\Users\Rupesh Jadhav\Downloads\MJ\mysql\data\ibtmp1’ size is now 12 MB.
    2023-07-25 0:27:30 0 [Note] InnoDB: Waiting for purge to start
    2023-07-25 0:27:30 0 [Note] InnoDB: 10.4.28 started; log sequence number 300297; transaction id 170
    2023-07-25 0:27:30 0 [Note] InnoDB: Loading buffer pool(s) from C:\Users\Rupesh Jadhav\Downloads\MJ\mysql\data\ib_buffer_pool
    2023-07-25 0:27:30 0 [Note] Plugin ‘FEEDBACK’ is disabled.
    2023-07-25 0:27:30 0 [Note] Server socket created on IP: ‘::’.
    2023-07-25 0:36:47 0 [Note] Starting MariaDB 10.4.28-MariaDB source revision c8f2e9a5c0ac5905f28b050b7df5a9ffd914b7e7 as process 11532
    2023-07-25 0:36:47 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
    2023-07-25 0:36:47 0 [Note] InnoDB: Uses event mutexes
    2023-07-25 0:36:47 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
    2023-07-25 0:36:47 0 [Note] InnoDB: Number of pools: 1
    2023-07-25 0:36:47 0 [Note] InnoDB: Using SSE2 crc32 instructions
    2023-07-25 0:36:47 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
    2023-07-25 0:36:47 0 [Note] InnoDB: Completed initialization of buffer pool
    2023-07-25 0:36:47 0 [Note] InnoDB: Starting crash recovery

You are posting a reply to: XAMPP

The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our Community FAQs for details. All submitted content is subject to our Terms of Use.

All Comments

  • Author
    Replies
    • #4151880
      Avatar photo

      Reply To: XAMPP

      by birdmantd ·

      In reply to XAMPP

      It would help to know if there is an issue with that code or just what or why you posted it. Hard to offer any advice with just this information.

      Reminder to all: keep out internet links in this thread.

    • #4151912
      Avatar photo

      Old version?

      by rproffitt ·

      In reply to XAMPP

      “The latest current long-term stable series is MariaDB 10.11 (maintained for five years)”

      I’ve learned to use the latest stable releases.

    • #4157082

      MariaDB error

      by Harisamer214 ·

      In reply to XAMPP

      To troubleshoot the problem, you can check the following:

      1. The system logs for any errors that may have occurred around the time of the crash.
      2. The MariaDB error logs for any errors that may have been generated during the crash recovery.
      3. The MariaDB configuration file for any errors or inconsistencies.
      4. The MariaDB data files for any corruption.

      If you are unable to troubleshoot the problem yourself, you can contact the MariaDB support team for assistance.

Viewing 2 reply threads