Comment 2 for bug 1884354

Thank you for taking the time to file a bug report.

Upon investigating the log files, I noticed a few problematic error messages:

2020-06-08T20:32:39.589633Z 0 [ERROR] [MY-011300] [Server] Plugin mysqlx reported: 'Setup of socket: '/var/run/mysqld/mysqlx.sock' failed, can't create lock file /var/run/mysqld/mysqlx.sock.lock'
2020-06-08T20:32:39.590574Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060
2020-06-08T20:32:40.007744Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-06-08T20:32:40.012430Z 0 [ERROR] [MY-010262] [Server] Can't start server: Bind on TCP/IP port: Address already in use
2020-06-08T20:32:40.013033Z 0 [ERROR] [MY-010257] [Server] Do you already have another mysqld server running on port: 3306 ?
2020-06-08T20:32:40.014116Z 0 [ERROR] [MY-010119] [Server] Aborting

These lines tell me that there is likely another instance of mysqld running on your system, which is preventing the complete restart of the system mysqld. I also find it strange that the mysqlx.sock.lock lockfile could not be created; this is also an indication that another mysqld instance is being executed.

My suggestion is that you make sure that no other mysqld is running (a "ps ax | grep mysqld" should tell you if there is any), and that no other program is using the port 3306. After you do that, you will likely be able to successfully complete the installation.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community