Ubuntu
mysql-5.7 package

package mysql-server-5.7 5.7.20-0ubuntu0.17.04.1 failed to install/upgrade: el subproceso instalado paquete mysql-server-5.7 script post-installation devolvió el código de salida de error 1

Bug #1923010 reported by Enrique GE on 2021-04-08

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	mysql-5.7 (Ubuntu)	Expired	Undecided	Unassigned

Bug Description

mysql.service - MySQL Community Server
     Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Thu 2021-04-08 09:43:06 CEST; 69ms ago
    Process: 104470 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
    Process: 104491 ExecStart=/usr/sbin/mysqld (code=exited, status=2)
    Process: 104492 ExecStartPost=/usr/share/mysql/mysql-systemd-start post (code=exited, status=0/SUCCESS)
   Main PID: 104491 (code=exited, status=2)

abr 08 09:43:06 bigdata systemd[1]: mysql.service: Scheduled restart job, restart counter is at 1.
abr 08 09:43:06 bigdata systemd[1]: Stopped MySQL Community Server.
abr 08 09:43:06 bigdata systemd[1]: Starting MySQL Community Server...
abr 08 09:43:06 bigdata systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
dpkg: error al procesar el paquete mysql-server-5.7 (--configure):
el subproceso instalado paquete mysql-server-5.7 script post-installation devolvió el código de salida de error 1
Procesando disparadores para man-db (2.9.1-1) ...
Procesando disparadores para ureadahead (0.100.0-21) ...
Procesando disparadores para libc-bin (2.31-0ubuntu9.2) ...
Procesando disparadores para systemd (245.4-4ubuntu3.6) ...
Se encontraron errores al procesar:
mysql-server-5.7
E: Sub-process /usr/bin/dpkg returned an error code (1)
bigdata@bigdata:~$ mysql -u root -p
Enter password:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-5.7 5.7.20-0ubuntu0.17.04.1
ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94
Uname: Linux 5.4.0-67-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Apr 7 18:32:52 2021
ErrorMessage: el subproceso instalado paquete mysql-server-5.7 script post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2018-04-22 (1081 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
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
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLVarLibDirListing: ['ibdata1', 'sys', 'auto.cnf', 'ca.pem', 'ib_buffer_pool', 'ib_logfile1', 'server-key.pem', 'binlog.index', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'server-cert.pem', 'binlog.000005', 'binlog.000006', 'mysql.ibd', 'binlog.000002', 'client-cert.pem', 'bigdata.err', '#innodb_temp', 'ib_logfile0', 'client-key.pem', 'ca-key.pem', 'binlog.000001', 'binlog.000003', 'undo_002', 'performance_schema', 'undo_001', 'binlog.000004', 'private_key.pem', 'public_key.pem', '#ib_16384_1.dblwr', 'mysql']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=a6ee2e9e-ba5e-48ae-b942-864120ade056 ro quiet splash
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-5.7
Title: package mysql-server-5.7 5.7.20-0ubuntu0.17.04.1 failed to install/upgrade: el subproceso instalado paquete mysql-server-5.7 script post-installation devolvió el código de salida de error 1
UpgradeStatus: Upgraded to focal on 2021-03-04 (34 days ago)

Tags:

Revision history for this message

Enrique GE (enrique19-91) wrote on 2021-04-08:

.etc.apparmor.d.usr.sbin.mysqld.txt Edit (1.5 KiB, text/plain; charset="utf-8")
AptOrdering.txt Edit (356 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Df.txt Edit (511 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (63.1 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (7.8 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (3.1 KiB, text/plain; charset="utf-8")
KernLog.txt Edit (36.1 KiB, text/plain; charset="utf-8")
Logs.var.log.mysql.error.log.txt Edit (332.8 KiB, text/plain; charset="utf-8")
MySQLConf.etc.mysql.my.cnf.txt Edit (682 bytes, text/plain; charset="utf-8")
MySQLConf.etc.mysql.mysql.cnf.txt Edit (682 bytes, text/plain; charset="utf-8")
MySQLConf.etc.mysql.mysql.conf.d.mysql.cnf.txt Edit (132 bytes, text/plain; charset="utf-8")
MySQLConf.etc.mysql.mysql.conf.d.mysqld.cnf.txt Edit (3.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (941 bytes, text/plain; charset="utf-8")

Revision history for this message

Christian Ehrhardt  (paelzer) wrote on 2021-04-09:

Download full text (4.4 KiB)

Thanks for your report and your help to make Ubuntu better.

From you log this seems to be a real crash:

2021-04-07T17:09:57.616740Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
2021-04-07 19:09:57 0x7f053ee22740 InnoDB: Assertion failure in thread 139660506572608 in file ut0ut.cc line 916
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
17:09:57 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76385 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x55a2a8de48eb]
/usr/sbin/mysqld(handle_fatal_signal+0x489)[0x55a2a86dd679]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0)[0x7f053f3983c0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7f053ee8a18b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7f053ee69859]
/usr/sbin/mysqld(+0x61d9b9)[0x55a2a86b39b9]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0x145)[0x55a2a8fbd0a5]
/usr/sbin/mysqld(+0xfd80ab)[0x55a2a906e0ab]
/usr/sbin/mysqld(+0xfd8717)[0x55a2a906e717]
/usr/sbin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2e8)[0x55a2a9077cc8]
/usr/sbin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xdd)[0x55a2a902ab6d]
/usr/sbin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4ca)[0x55a2a8ff8efa]
/usr/sbin/mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x152)[0x55a2a8f9a462]
/usr/sbin/mysqld(+0x61cb3d)[0x55a2a86b2b3d]
/usr/sbin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f5d)[0x55a2a8f6622d]
/usr/sbin/mysqld(+0xd9786a)[0x55a2a8e2d86a]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x55a2a872ad9f]
/usr/sbin/mysqld(+0xb321d5)[0x55a2a8bc81d5]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x600)[0x55a2a8bcf9d0]
/usr/sbin/mysqld(+0x63fa2f)[0x55a2a86d5a2f]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x810)[0x55a2a86d7190]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x7f053ee6b0b3]
/usr/sbin/mysqld(_start+0x2a)[0x55a2a86cda2a]
...

Thanks for your report and your help to make Ubuntu better.

From you log this seems to be a real crash:

2021-04-07T17:09:57.616740Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
2021-04-07 19:09:57 0x7f053ee22740  InnoDB: Assertion failure in thread 139660506572608 in file ut0ut.cc line 916
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
17:09:57 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76385 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Further from your logs it seems that this is a fresh mysql install - is that correct?
I wonder where it should get bad table data then - is on that system an old DB that might not work well with the new server?

Checking the internet for this kind of errors I've found that the most likely case seems to be a database that was created/used with a new mysql e.g. 8.0 and then trying to use an old mysql e.g. 5.7 with it.

In your logs I then found:

Start-Date: 2021-04-07  16:32:40
Commandline: apt-get install mysql-server
Requested-By: bigdata (1000)
...
Start-Date: 2021-04-07  18:32:01
Commandline: apt-get install mysql-server-5.7

So you installed "mysql-server" which in Ubuntu 20.04 is mysql-8.0.
So far so good, that should be fine and work.

But later on you installed 5.7 from some other (non supported) source.
And this crashes.

You need to 
a) use the mysql-8.0 from the archive as that is what the DB files on disk match
b) fully purge the package and the database, then re-install the 5.7 server - but be aware that this is not supported it isn't in the Ubuntu repository of 20.04 and therefore will not get fixes and security updates.

I'll mark this incomplete as it seems a local configuration issue, more than a bug in Ubuntu.
If you think it is a package bug please explain why and re-open the case.

Changed in mysql-5.7 (Ubuntu):
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2021-06-09:

[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]

Changed in mysql-5.7 (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntumysql-5.7 package

package mysql-server-5.7 5.7.20-0ubuntu0.17.04.1 failed to install/upgrade: el subproceso instalado paquete mysql-server-5.7 script post-installation devolvió el código de salida de error 1

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
mysql-5.7 package