Hi, from your log: 2020-06-25T06:53:24.803948Z 0 [ERROR] [MY-011300] [Server] Plugin mysqlx reported: 'Setup of socket: '/var/run/mysqld/mysqlx.sock' failed, another process with PID 22883 is using UNIX socket file' 2020-06-25T06:53:26.068348Z 0 [ERROR] [MY-010259] [Server] Another process with pid 22883 is using unix socket file. 2020-06-25T06:53:26.068546Z 0 [ERROR] [MY-010268] [Server] Unable to setup unix socket lock file. 2020-06-25T06:53:26.069046Z 0 [ERROR] [MY-010119] [Server] Aborting
I have seen such issues rarely to show up as flaky behavior, but in your case it seems soemthing else really locks that file still. You might have a look at running procsses and the last (on a re-install) reported PID especially. Do you have an out-of-archive mysql running in background and/or had a very unclean application shutdown that might keep it open? As trivial as it sounds - if unsure how to clean up a restart might help as well here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885120 Title: package mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 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-8.0/+bug/1885120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
