Comment 2 for bug 1803141

Hi leyb,

Looking in the logs, mysql is failing because it can't obtain a lockfile:

2018-11-13T14:17:06.265515Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2018-11-13T14:17:06.265584Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2018-11-13T14:17:06.265618Z 0 [Note] InnoDB: Unable to open the first data file
2018-11-13T14:17:06.265652Z 0 [ERROR] InnoDB: Operating system error number 11 in a file operation.
2018-11-13T14:17:06.265673Z 0 [ERROR] InnoDB: Error number 11 means 'Resource temporarily unavailable'
2018-11-13T14:17:06.265687Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2018-11-13T14:17:06.265701Z 0 [ERROR] InnoDB: Cannot open datafile './ibdata1'
2018-11-13T14:17:06.265738Z 0 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2018-11-13T14:17:06.265753Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Cannot open a file

Please make sure there aren't other instances accessing that file, and that its permissions are correct. Another cause could be an unclean shutdown.