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

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

Need more information

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

2020-06-09T14:27:27.020179Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-06-09T14:27:27.020943Z 0 [ERROR] [MY-010262] [Server] Can't start server: Bind on TCP/IP port: Address already in use
2020-06-09T14:27:27.021054Z 0 [ERROR] [MY-010257] [Server] Do you already have another mysqld server running on port: 3306 ?
2020-06-09T14:27:27.021284Z 0 [ERROR] [MY-010119] [Server] Aborting

This usually means that, for some reason, the previous instance could *not* be shutdown before the new instance start was attempted. This usually happens because of manually started instances (outside the scope of mysql service) or because of the shutdown procedure hitting the default timeout set in the mysql services unit file (or similar reasons that might happen during an upgrade).

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, 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

Hi Rafael,

Thanks for getting back to me.
The crash happened after I installed "dbeaver".
I opened the freshly installed dbeaver and tried do make a new connection
to mySQL.
dbeaver alerted me for failed connection prompting me to download a mySQL
driver.
I accepted the download and the crash happened.

Actually I've had several problems with Ubuntu 20.04, so now I downgraded
to 18.04 (bionic).
(e.g. Did you know the command *lsb_release -a * does not work on ubuntu
20.04 either? At least on my machine....)

My system:
description: Desktop Computer
    product: MS-7918 (To be filled by O.E.M.)
    vendor: MSI
    version: 1.0
    serial: To be filled by O.E.M.
    width: 64 bits
    capabilities: smbios-2.8 dmi-2.8 smp vsyscall32
    configuration: administrator_password=enabled boot=normal
chassis=desktop family=To be filled by O.E.M. frontpanel_password=disabled
keyboard_password=disabled power-on_password=disabled sku=To be filled by
O.E.M. uuid=00000000-0000-0000-0000-D8CB8A15DDFA
  *-core
       description: Motherboard
       product: H97 GAMING 3 (MS-7918)
       vendor: MSI
       physical id: 0
       version: 1.0
       serial: To be filled by O.E.M.
       slot: To be filled by O.E.M.
     *-firmware
          description: BIOS
          vendor: American Megatrends Inc.
          physical id: 0
          version: V1.7
          date: 12/24/2014
          size: 64KiB
          capacity: 15MiB
          capabilities: pci upgrade shadowing cdboot bootselect socketedrom
edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen
int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
     *-cpu
          description: CPU
          product: Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz
          vendor: Intel Corp.
          physical id: 3d
          bus info: cpu@0
          version: Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz
          slot: SOCKET 0
          size: 3651MHz
          capacity: 3900MHz
          width: 64 bits
          clock: 100MHz
          capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse
sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc arch_perfmon pebs
bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c
rdrand lahf_lm abm cpuid_fault invpcid_single pti ssbd ibrs ibpb stibp
tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2
smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts md_clear flush_l1d
cpufreq
          configuration: cores=4 enabledcores=4 threads=4
        *-cache:0
             description: L1 cache
             physical id: 3e
             slot: CPU Internal L1
             size: 256KiB
             capacity: 256KiB
             capabilities: synchronous internal write-back
             configuration: level=1
        *-cache:1
             description: L2 cache
             physical id: 3f
             slot: CPU Internal L2
             size: 1MiB
             capacity: 1MiB
             capabilities: ...

Thank you for your feedback, Pedro.

The first thing that caught my attention was the "dbeaver" thing. Where did you install it from? Because it is not in the Ubuntu archives, so it's not an official Ubuntu package. Another thing worth mentioning is the fact that, if dbeaver asked you to download and install a third-party driver to MySQL, then this probably caused MySQL's internal state to be inconsistent.

Last, but not least, I was perfectly able to run "lsb_release -a" on a Ubuntu 20.04 machine, which is yet another indicator that there might be something wrong with your system.

Thanks!

Hi,
The first thing that caught my attention was the "dbeaver" thing. Where did
you install it from?
The name is *dbeaver-ce, got it *from Ubuntu Software (with which I also
had problems as well. I couldn't see most images or even apt's.. ).
*dbeaver-ce *is a database management tool (supposedly).
I wanted an alternative to MySQL Workbench and phpMyAdmin was not able to
deal with all the data I had.

Last, but not least, I was perfectly able to run "lsb_release -a" on a
Ubuntu 20.04 which is yet another indicator that there might be something
wrong with your system.
That really triggered some bells. Don't have a clue as to what that could
be, but it only happened with *Focal Fossa *(which is kind of an ugly name
in Portuguese).
Before that, I installed *Docker* and created some containers, but I don't
think that had anything to do with it.

I really liked the speed of *20.04* and the new look.
Anyway, Ubuntu 18 is running smoothly and I got everything up and running
now.

I hope you guys can overcome the problems that may arise.
I'll wait a bit before upgrading again.

Best wishes!

On Tue, Jun 16, 2020 at 7:55 PM Sergio Durigan Junior <
<email address hidden>> wrote:

> Thank you for your feedback, Pedro.
>
> The first thing that caught my attention was the "dbeaver" thing. Where
> did you install it from? Because it is not in the Ubuntu archives, so
> it's not an official Ubuntu package. Another thing worth mentioning is
> the fact that, if dbeaver asked you to download and install a third-
> party driver to MySQL, then this probably caused MySQL's internal state
> to be inconsistent.
>
> Last, but not least, I was perfectly able to run "lsb_release -a" on a
> Ubuntu 20.04 machine, which is yet another indicator that there might be
> something wrong with your system.
>
> Thanks!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1882791
>
> 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
>
> Status in mysql-8.0 package in Ubuntu:
> Incomplete
>
> Bug description:
> Renaming removed key_buffer and myisam-recover options (if present)
> mysqld will log errors to /var/log/mysql/error.log
> mysqld is running as pid 6969
> dpkg: error processing package mysql-server-8.0 (--configure):
> installed mysql-server-8.0 package post-installation script subprocess
> returned
> error exit status 1
> dpkg: dependency problems prevent configuration of mysql-server:
> mysql-server depends on mysql-server-8.0; however:
> Package mysql-server-8.0 is not configured yet.
>
> dpkg: error processing package mysql-server (--configure):
> dependency problems - leaving unconfigured
> Processing triggers for systemd (245.4-4ubuntu3.1) ...
> No apport report written because the error message indicates its a
> followup erro
> r from a previous failure.
> Processing triggers for man-db (2.9.1-1) ...
> Processing triggers for libc-bin (2.31-0ubuntu9) ...
> Errors were encountere...

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