Hi, the logs all point to the assumption that there might be a seconds mysl daemon process still running, from your logs:
2020-05-28T01:47:45.943449Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 2020-05-28T01:47:45.943476Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2020-05-28T01:47:45.943485Z 0 [Note] InnoDB: Retrying to lock the first data file ... 2020-05-28T02:25:51.531290Z 0 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use 2020-05-28T02:25:51.531294Z 0 [ERROR] Do you already have another mysqld server running on port: 3306 ? 2020-05-28T02:25:51.531307Z 0 [ERROR] Aborting That is a conflict as on the update/upgrade the packaging system needs to restart the service. By restarting the packaged service the collision with - whatever else is up - is happening. The only other chance is that stopping the process failed, but I found many proper 2020-05-27T15:54:28.098127Z 0 [Note] /usr/sbin/mysqld: Shutdown complete So I'd tihnk that isn't the case. You'd need to find what you have running in background and resolve that - then restarting and thereby the upgrade will work again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881053 Title: package mysql-server-5.7 5.7.30-0ubuntu0.16.04.1 failed to install/upgrade: subprocesso script post-installation instalado retornou erro do status de saída 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1881053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
