If the mysql service is up right now, shut it down
C:\> net stop mysql
You need to create my.ini
Go to C:\Program Files\MySQL\MySQL Server 5.5
You should see a bin folder and the data folder you have in your question
Create my.ini in C:\Program Files\MySQL\MySQL Server 5.5
I noticed you have
- ibdata1
- 3 innodb log files
- binary logs that start with
mysql-bin
Make sure you have these options in my.ini
[mysqld]
innodb_data_file_path=ibdata1:10M:autoextend
innodb_log_files_in_group=3
innodb_log_file_size=256M
innodb_buffer_pool_size=768M
log-bin=mysql-bin
You need to start the service manually
C:\> cd "C:\Program Files\MySQL\MySQL Server 5.5\bin"
C:\> net start mysqld
By default, when starting up mysqld like this, mysqld.exe expects the my.ini to initially be in its parent directory.
If mysql starts successfully, you should see mysqld.exe
in the processlilst of the Task Manager and the file clarinet.err should have today's date. You can shut it down using:
C:\> cd "C:\Program Files\MySQL\MySQL Server 5.5\bin"
C:\> mysqladmin -uroot shutdown
Now configure mysql service so that it uses C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld.exe
you need to make sure the correct my.ini
is edited, you can check it from windows services by opening MySQL properties and make sure it is related to MySQL 5.6. now you need to stop the service then open the ini
file in the service description and edit the port. finally start the service and try to log in from CMD
using:
1) cd C:\Archivos de programa\MySQL\MySQL Server 5.6
2) mysql -uroot -Pport -ppassword
Best Answer
InnoDB
Please note the InnoDB Architecture (picture courtesy of Percona CTO Vadim Tkachenko)
If your database is read/write, I wrote about why InnoDB cannot allow multiple instances
Apr 24, 2014
: Two MySQL Server accessing same database over NFSOct 03, 2013
: Is there any way to use different InnoDB settings for different databases on the same server?Your only alternative would be to start InnoDB in read only mode (See my only post mentioning this How to start mysqld with read-only data directory? as well as the MySQL 5.6 Documentation for the ReadOnly InnoDB Setting).
MyISAM
If you have database is all MyISAM or a mix of InnoDB and MyISAM, your MyISAM tables would be very prone to being in crash state (Unfortunately, that is true even for a single mysqld instance).
Keep in mind that every time you open a MyISAM table, there is counter in the header of the MyISAM table that monitors how many open file handles a MyISAM table has (See my
Mar 15, 2012
answer to Why do MySQL tables crash? How do I prevent it?). If a single mysqld instance crashes, the table is consider crashed. This will pile up warnings in the error log stating the MyISAM table would have to be repaired. If this is the case for a single mysqld instance, it is far more likely to happen with multiple instances. This would be case even if a mysqld instance was started with innodb_read_only and read_only enabled.YOUR QUESTION
Your mysql schema has some MyISAM tables in it. They are small. Even if they crashed, your could run REPAIR TABLE on them and fix them quickly but there is a 1 in a million chance of dealing with authentication issues if you cannot repair them.
Since you mentioned
.ini
, I assume you are in Windows. When it comes to MySQL, file handling locking in Windows tending to be more strict that that of Linux. So, InnoDB might be more cumbersome or slower in read only mode.CONCLUSION