MySql won't start

[knutsford]

I can't get my MySql to start



The error log gives


2020-07-13 10:19:29 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2020-07-13 10:19:29 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2020-07-13 10:19:29 0 [Note] InnoDB: Uses event mutexes
2020-07-13 10:19:29 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-07-13 10:19:29 0 [Note] InnoDB: Number of pools: 1
2020-07-13 10:19:29 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-07-13 10:19:29 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2020-07-13 10:19:29 0 [Note] InnoDB: Completed initialization of buffer pool
2020-07-13 10:19:29 0 [Note] InnoDB: Setting file 'D:\xamplatest\mysql\data\ibdata1' size to 10 MB. Physically writing the file full; Please wait ...
2020-07-13 10:19:29 0 [Note] InnoDB: File 'D:\xamplatest\mysql\data\ibdata1' size is now 10 MB.
2020-07-13 10:19:29 0 [Note] InnoDB: Setting log file D:\xamplatest\mysql\data\ib_logfile101 size to 5242880 bytes
2020-07-13 10:19:29 0 [Note] InnoDB: Setting log file D:\xamplatest\mysql\data\ib_logfile1 size to 5242880 bytes
2020-07-13 10:19:29 0 [Note] InnoDB: Renaming log file D:\xamplatest\mysql\data\ib_logfile101 to D:\xamplatest\mysql\data\ib_logfile0
2020-07-13 10:19:29 0 [Note] InnoDB: New log files created, LSN=11452
2020-07-13 10:19:29 0 [Note] InnoDB: Doublewrite buffer not found: creating new
2020-07-13 10:19:29 0 [Note] InnoDB: Doublewrite buffer created
2020-07-13 10:19:29 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-07-13 10:19:29 0 [Note] InnoDB: Creating foreign key constraint system tables.
2020-07-13 10:19:29 0 [Note] InnoDB: Creating tablespace and datafile system tables.
2020-07-13 10:19:29 0 [Note] InnoDB: Creating sys_virtual system tables.
2020-07-13 10:19:30 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-07-13 10:19:30 0 [Note] InnoDB: Setting file 'D:\xamplatest\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-07-13 10:19:30 0 [Note] InnoDB: File 'D:\xamplatest\mysql\data\ibtmp1' size is now 12 MB.
2020-07-13 10:19:30 0 [Note] InnoDB: 10.4.11 started; log sequence number 0; transaction id 7
2020-07-13 10:19:30 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-07-13 10:19:30 0 [Note] Server socket created on IP: '::'.l



What do I do please - thanks

[peterm]

I am having the exact same problem with the same log messages.

I shutdown Skype, changed the listening ports multiple times and recreated ibtmp1 but neither worked.

I haven't changed anything significant on my machine, well, not that I can remember, and it has been a few days since I last launched XAMPP.

[knutsford]

Not sure what I did. I was tryingto get Banshee working on XAMP which appears to be impossible unless someone on here has managed it. I presume I messed something up. I ended up downloading and settind up xamp again

[peterm]

Still no luck for me.

I installed new version of XAMPP (7.2.31 from 7.2.29). I verified the new installation worked and checked PHPMyAdmin.

Then I copied the MYSQL/data folder from the old directory into the new one. But again it fails to start. Interestingly, the log produces the same output for both starting correctly and failing to start:

InnoDB: using atomic writes.
2020-07-15 10:46:39 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2020-07-15 10:46:39 0 [Note] InnoDB: Uses event mutexes
2020-07-15 10:46:39 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-07-15 10:46:39 0 [Note] InnoDB: Number of pools: 1
2020-07-15 10:46:39 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-07-15 10:46:39 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2020-07-15 10:46:39 0 [Note] InnoDB: Completed initialization of buffer pool
2020-07-15 10:46:39 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-07-15 10:46:39 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-07-15 10:46:39 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-07-15 10:46:39 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2020-07-15 10:46:39 0 [Note] InnoDB: Waiting for purge to start
2020-07-15 10:46:39 0 [Note] InnoDB: 10.4.13 started; log sequence number 47134; transaction id 9
2020-07-15 10:46:39 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2020-07-15 10:46:39 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-07-15 10:46:39 0 [Note] InnoDB: Buffer pool(s) load completed at 200715 10:46:39
2020-07-15 10:46:39 0 [Note] Server socket created on IP: '::'.

[peterm]

I managed to get it to work by copying ONLY the data sub folder of the database for the site I need.

For example, instead of copying the entire mysql/data folder I only copied over mysql/data/site1 into the new XAMPP installation.

XAMPP started and I can view/edit the site as needed. However, I'm just concerned that maybe I have missed something that might cause problems later on. Is this all that is needed?

Thanks!

[knutsford]

I did that to copy over the missing DAtabases after I reloaded XAMP an it worked no problem at all.

[peterm]

OK, so the entire data folder is not necessary? I just wanted to check that I don't miss something fundamental.

[Altrea]

I'm just concerned that maybe I have missed something that might cause problems later on. Is this all that is needed?

For InnoDB Databases the ibdata1 file is essential because it contains important information about the existance of each InnoDB database.
So if you are missing databases that is because of the missing informtion from the ibdata1 file.

[peterm]

Thanks Altrea!

That worked too actually...I copied the ibdata1 file from the old install over and the site still works. However, looking into PHPMyAdmin it shows that the tables are MyISAM. Is that a problem?

[Altrea]

Not a problem. Current MariaDB and MySQL versions set InnoDB as default engine but support the MyISAM engine too.

In fact MyISAM is much easier to backup and restore because all you need (except the user permissions) are capsuled inside one data folder. But MyISAM is not actively developed any further.

[peterm]

Great, thanks for the info, much appreciated!

So, using MyISAM shouldn't be a problem for the foreseeable future you think? Can you convert a MyISAM DB to an InnoDB?