Hi Shaswat, to me it seems you summarized the right steps in the error description already.
Form your log: 2018-09-02T10:02:38.428757Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2018-09-02T10:02:38.428762Z 0 [Note] InnoDB: Retrying to lock the first data file 2018-09-02T10:02:39.428914Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 There usually (with users having that issue) is a seconday database process running - often out of archive alternatives or such. Other common issues are modified permissions in default paths making it unable to lock the file. The internet is full of this issue and it usually involved uninstalling or at least killing the other instance like in [1]. Whatever it is it is custom to your system and not a bug in the package (at least as it seems to me). You'd need to remove/fix the broken config. [1]: https://serverfault.com/questions/477448/mysql-keeps-crashing-innodb-unable-to-lock-ibdata1-error-11 [2]: https://stackoverflow.com/questions/35978228/how-to-solve-innodb-unable-to-lock-ibdata1-mysql-error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790353 Title: package mysql-server-5.7 5.7.23-0ubuntu0.18.04.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1790353/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
