Setup of socket: '/var/run/mysqld/mysqlx.sock' failed, can't create lock file /var/run/mysqld/mysqlx.sock.lock

[Kiruthika Srinivasan]

I'm receiving a bug associated with mysql-server

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.25-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun May 16 12:22:12 2021
ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2020-05-14 (366 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Logs.var.log.daemon.log:

MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLVarLibDirListing: ['server-cert.pem', '#ib_16384_1.dblwr', 'undo_001', 'binlog.000029', '#ib_16384_0.dblwr', 'mysql', 'debian-5.7.flag', 'binlog.000032', 'sys', '#innodb_temp', 'private_key.pem', 'auto.cnf', 'mysql.ibd', 'ca.pem', 'ib_logfile1', 'ca-key.pem', 'public_key.pem', 'ib_buffer_pool', 'ibdata1', 'binlog.000031', 'binlog.000030', 'ib_logfile0', 'performance_schema', 'mysql_upgrade_info', 'binlog.000033', 'undo_002', 'binlog.index', 'server-key.pem', 'client-key.pem', 'client-cert.pem']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=ef2296ed-6f01-4638-aa82-c069e628afd9 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.5
SourcePackage: mysql-8.0
Title: package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christian Ehrhardt  (paelzer)]

From the log:

mysqld is running as pid 40206
Error: Unable to shut down server with process id 40206
dpkg: error processing package mysql-server-8.0 (--configure):
 installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1

I have found a few more of the very same kind of symptom and dup'ed them onto this bug.

[Christian Ehrhardt  (paelzer)]

From the various logs of the Dup'ed reports

2021-05-16T06:50:50.121637Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 8.0.25-0ubuntu0.20.04.1).
2021-05-16T06:52:11.158581Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.25-0ubuntu0.20.04.1) (Ubuntu).

2021-05-14T15:00:45.374548Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 8.0.25-0ubuntu0.20.04.1).
2021-05-14T15:02:34.772555Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.25-0ubuntu0.20.04.1) (Ubuntu).

2021-05-15T03:47:57.482984Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 8.0.25-0ubuntu0.20.04.1).
2021-05-15T03:49:12.833404Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.25-0ubuntu0.20.04.1) (Ubuntu).

That is 1-2 minutes which clearly is much longer than usual.
Was there a recent change which made shutdown slower?
Or OTOH do we generally have a problem with big databases that might take a while.

@Bug reporters - what size and complexity of mysql database are you using?

@Lars - would you take a detailed look please?

[Utkarsh Gupta (utkarsh)]

Hello,

A duplicate of this came in on Friday as well; cf: LP: #1928290, which is further a duplicate of LP: #1928290, thus marking the same.

Thanks!