This is because there are other MYSQL processes also read the data file, you need to kill this process can
ps -eaf | gerp mysql
killall mysql
ps -eaf | gerp mysql
killall mysql
Read More:
- Centos 7 | mariadb/mysql | [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
- Global lock, table lock and row lock in MySQL
- Fatal: unable to create ‘project_ path/.git/ index.lock ‘: File exists.
- Permission denied error: unable to index file .vs/Trip2015/v15/Server/sqlite3/db.lock fatal: adding
- Unity Cursor Lock& Camera Lock
- Forced shutdown of VMware wrokstation error (failed to get exclusive lock on the configuration file —)
- InnoDB, tokudb, MyISAM directory structure
- When linux installs rpm, it prompts: can’t create transaction lock on /var/lib/rpm/.rpm.lock error
- MySQL error: InnoDB: operating system error number 13 in a file operation
- MySQL error 1205 (HY000): lock wait timeout exceeded; try restarting transaction
- Waiting for another pilot command to release the startup lock
- mysqldump: Got error: 1016: Can’t open file: ‘./xxx.frm’ (errno: 24) when using LOCK TABLES
- Java uses lock to realize multithread sequential alternate execution mode 2
- Lock wait timeout exceeded — transaction and index
- could not be opened to write the process output: fopen(/tmp\sf_proc_00.out.lock)
- [338] MySQL error: error 1205: lock wait timeout exceeded solution
- Solution to MySQL workbench error 1148 unable to load local data
- VMware failed to lock memory file. Error restoring virtual machine state from file
- Lock mechanism in Oracle
- Ansible Failed – apt lock