>From your log
2020-04-15T23:47:03 Received SHUTDOWN from user boot.
2020-04-15T23:47:09 /usr/sbin/mysqld starting as process 28376
2020-04-15T23:47:12 /usr/sbin/mysqld: ready for connections.
socket: '/tmp/tmp.FK5jsVGYfP/mysqld.sock' port: 0 (Ubuntu).
2020-04-15T23:47:12 Plugin mysqlx reported: 'Setup of socket:
'/var/run/mysqld/mysqlx.sock' failed, can't create lock file
/var/run/mysqld/mysqlx.sock.lock'
2020-04-15T23:47:14 /usr/sbin/mysqld: Shutdown complete
2020-04-15T23:47:15 /usr/sbin/mysqld starting as process 28439
2020-04-15T23:47:17.853619Z 0 [ERROR] Can't start server: Bind on TCP/IP
port: Address already in use
So through the updates it goes through some restarts.
This looks like either:
- concurrent start/stop
- something in the background has grabbed the port
Does this issue reproduce when you install/upgrade again?
If so could you please check which ports are bound by which proceses.
Like:
$ sudo netstat -tlpeen
I'm also wondering about that lock issue.
Maybe we can check for who owns that file (if it exists)
$ sudo lsof +fg +E /var/run/mysqld/mysqlx.sock.lock
If there is one or more PIDs having that file open report what they are (e.g.
via ps axlf | grep >PID<)
And report that here?
** Changed in: mysql-8.0 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873101
Title:
package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to
install/upgrade: el subproceso instalado paquete mysql-server-8.0
script post-installation devolvió el código de salida de error 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1873101/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
