Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 10.0.0
    • Fix Version/s: 10.0.2
    • Component/s: None
    • Labels:
      None
    • Environment:
      WinXP

      Description

      I installed 10.0.0, MSI package. Apparently installation was successfull, but when I tried to start the server it didn't work. I deleted InnoDB log files, and then I was able to start the server.

      Error log:

      130124 10:49:47 InnoDB: The InnoDB memory heap is disabled
      130124 10:49:47 InnoDB: Mutexes and rw_locks use Windows interlocked functions
      130124 10:49:47 InnoDB: Compressed tables use zlib 1.2.3
      130124 10:49:47 InnoDB: CPU does not support crc32 instructions
      130124 10:49:47 InnoDB: Initializing buffer pool, size = 128.0M
      130124 10:49:47 InnoDB: Completed initialization of buffer pool
      InnoDB: The first specified data file .\ibdata1 did not exist:
      InnoDB: a new database to be created!
      130124 10:49:47 InnoDB: Setting file .\ibdata1 size to 10 MB
      InnoDB: Database physically writes the file full: wait...
      130124 10:49:47 InnoDB: Log file .\ib_logfile0 did not exist: new to be created
      InnoDB: Setting log file .\ib_logfile0 size to 5 MB
      InnoDB: Database physically writes the file full: wait...
      130124 10:49:48 InnoDB: Log file .\ib_logfile1 did not exist: new to be created
      InnoDB: Setting log file .\ib_logfile1 size to 5 MB
      InnoDB: Database physically writes the file full: wait...
      130124 10:49:48 InnoDB: Doublewrite buffer not found: creating new
      130124 10:49:48 InnoDB: Doublewrite buffer created
      130124 10:49:49 InnoDB: 128 rollback segment(s) are active.
      InnoDB: Creating foreign key constraint system tables
      InnoDB: Foreign key constraint system tables created
      130124 10:49:49 InnoDB: Waiting for the background threads to start
      130124 10:49:49 InnoDB: 1.2.0 started; log sequence number 0
      130124 10:49:49 [Note] Plugin 'FEEDBACK' is disabled.
      130124 10:49:56 InnoDB: FTS optimize thread exiting.
      130124 10:49:56 InnoDB: Starting shutdown...
      130124 10:49:58 InnoDB: Shutdown completed; log sequence number 1602824
      130124 10:50:00 InnoDB: The InnoDB memory heap is disabled
      130124 10:50:00 InnoDB: Mutexes and rw_locks use Windows interlocked functions
      130124 10:50:00 InnoDB: Compressed tables use zlib 1.2.3
      130124 10:50:00 InnoDB: CPU does not support crc32 instructions
      130124 10:50:01 InnoDB: Initializing buffer pool, size = 31.0M
      130124 10:50:01 InnoDB: Completed initialization of buffer pool
      130124 10:50:01 InnoDB: Log file .\ib_logfile0 did not exist: new to be created
      InnoDB: Setting log file .\ib_logfile0 size to 31 MB
      InnoDB: Database physically writes the file full: wait...
      130124 10:50:02 InnoDB: Log file .\ib_logfile1 did not exist: new to be created
      InnoDB: Setting log file .\ib_logfile1 size to 31 MB
      InnoDB: Database physically writes the file full: wait...
      130124 10:50:03 InnoDB: highest supported file format is Barracuda.
      InnoDB: The log sequence number in ibdata files does not match
      InnoDB: the log sequence number in the ib_logfiles!
      130124 10:50:03  InnoDB: Database was not shut down normally!
      InnoDB: Starting crash recovery.
      InnoDB: Reading tablespace information from the .ibd files...
      InnoDB: Restoring possible half-written data pages from the doublewrite
      InnoDB: buffer...
      130124 10:50:03 InnoDB: 128 rollback segment(s) are active.
      130124 10:50:03 InnoDB: Waiting for the background threads to start
      130124 10:50:03 InnoDB: 1.2.0 started; log sequence number 1603084
      130124 10:50:03 [Note] Plugin 'FEEDBACK' is disabled.
      130124 10:50:03 [Note] Event Scheduler: Loaded 0 events
      130124 10:50:03 [Note] C:\Programmi\MariaDB 10.0\bin\mysqld.exe: ready for connections.
      Version: '10.0.0-MariaDB'  socket: ''  port: 3306  Source distribution
      130124 11:03:13 InnoDB: The InnoDB memory heap is disabled
      130124 11:03:13 InnoDB: Mutexes and rw_locks use Windows interlocked functions
      130124 11:03:13 InnoDB: Compressed tables use zlib 1.2.3
      130124 11:03:13 InnoDB: CPU does not support crc32 instructions
      130124 11:03:13 InnoDB: Initializing buffer pool, size = 128.0M
      130124 11:03:13 InnoDB: Completed initialization of buffer pool
      InnoDB: Error: log file .\ib_logfile0 is of different size 32505856 bytes
      InnoDB: than specified in the .cnf file 5242880 bytes!
      130124 11:03:14 [ERROR] Plugin 'InnoDB' init function returned error.
      130124 11:03:14 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
      130124 11:03:15 [Note] Plugin 'FEEDBACK' is disabled.
      130124 11:03:16 [ERROR] Unknown/unsupported storage engine: InnoDB
      130124 11:03:16 [ERROR] Aborting
      
      130124 11:03:17 [Note] C:/Programmi/MariaDB 10.0/bin/mysqldd: Shutdown complete
      

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            wlad Vladislav Vaintroub added a comment -

            Federico, we tried couple of things here, and so far, nobody could reproduce it. If you're able to reproduce it still ,with 10.0.1, could you please record the filesystem activity with Process Monitor?
            It is very strange that log contains "C:\Programmi\MariaDB 10.0\bin\mysqld.exe: ready for connections" when service starts and "C:/Programmi/MariaDB 10.0/bin/mysqldd: Shutdown complete" when it finishes.
            Especially renamed executable name is suspicious.

            Show
            wlad Vladislav Vaintroub added a comment - Federico, we tried couple of things here, and so far, nobody could reproduce it. If you're able to reproduce it still ,with 10.0.1, could you please record the filesystem activity with Process Monitor? It is very strange that log contains "C:\Programmi\MariaDB 10.0\bin\mysqld.exe: ready for connections" when service starts and "C:/Programmi/MariaDB 10.0/bin/mysqldd: Shutdown complete" when it finishes. Especially renamed executable name is suspicious.
            Hide
            wlad Vladislav Vaintroub added a comment -

            Closing as still unable to reproduce. Please reopen if there is any information that can help to reproduce the issue.

            Show
            wlad Vladislav Vaintroub added a comment - Closing as still unable to reproduce. Please reopen if there is any information that can help to reproduce the issue.

              People

              • Assignee:
                wlad Vladislav Vaintroub
                Reporter:
                f_razzoli Federico Razzoli
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 hours
                  2h