Bug #95166 Zypper Update Fails and MySQL becomes unuseable
Submitted: 27 Apr 2019 14:46 Modified: 27 Apr 2019 18:09
Reporter: Peter VARGA Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Packaging Severity:S3 (Non-critical)
Version:8.0.16 OS:SUSE
Assigned to: CPU Architecture:Any
Tags: installation fails

[27 Apr 2019 14:46] Peter VARGA
Description:
Running the update with zypper fails.
Output from journal:
Stopped MySQL Server.
Starting MySQL Server...
 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.16) starting as process 17900
 [Warning] [MY-013245] [Server] The SSL library function CRYPTO_set_mem_functions failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation
 [Warning] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-001
 [System] [MY-013381] [Server] Server upgrade from '80015' to '80016' started.
 [ERROR] [MY-013384] [Server] Could not create server upgrade info file at '/var/lib/mysql/'.
 [ERROR] [MY-013380] [Server] Failed to upgrade server.
 [ERROR] [MY-010119] [Server] Aborting
 [Warning] [MY-011068] [Server] The syntax 'validate password plugin' is deprecated and will be removed in a future release. Please use validate_password component instead.
 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.16)  MySQL Community Server - GPL.
mysql.service: Main process exited, code=exited, status=1/FAILURE
Failed to start MySQL Server.
mysql.service: Unit entered failed state.
mysql.service: Failed with result 'exit-code'. 

/var/lib/mysql has 17GB free, or 52%

Output from ll:
drwxr-x--x 22 mysql      mysql   1.3K Apr 27 16:11 mysql/

Checking for file conflicts: ...............................................[done]
(1/8) Installing: python-dbus-python-1.2.4-2.5.2.x86_64 ....................[done]
(2/8) Installing: python3-dbus-python-1.2.4-2.5.2.x86_64 ...................[done]
(3/8) Installing: mysql-community-common-8.0.16-1.sles12.x86_64 ............[done]
(4/8) Installing: mysql80-community-release-sles12-3.noarch ................[done]
Additional rpm output:
warning: /etc/zypp/repos.d/mysql-community-source.repo created as /etc/zypp/repos.d/mysql-community-source.repo.rpmnew
warning: /etc/zypp/repos.d/mysql-community.repo created as /etc/zypp/repos.d/mysql-community.repo.rpmnew

(5/8) Installing: mysql-community-libs-8.0.16-1.sles12.x86_64 ..............[done]
(6/8) Installing: mysql-community-devel-8.0.16-1.sles12.x86_64 .............[done]
(7/8) Installing: mysql-community-client-8.0.16-1.sles12.x86_64 ............[done]
(8/8) Installing: mysql-community-server-8.0.16-1.sles12.x86_64 ............[done]
Additional rpm output:
/bin/chmod: cannot access '': No such file or directory
Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details.

There are some running programs that might use files deleted by recent upgrade. You may wish to check and restart some of them. Run 'zypper ps -s' to list these programs.

How to repeat:
Revert the VM and run 'zypper update'
[27 Apr 2019 15:56] Terje Røsten
Hi!

Thanks for your report!

This seems like dup of https://bugs.mysql.com/bug.php?id=95165

Try to change owner of mysql_upgrade_info:

$ sudo chown  mysql:mysql /var/lib/mysql/mysql_upgrade_info

Then start MySQL service again.

The 

"/bin/chmod: cannot access '': No such file or directory" 

is an (unreleated and harmless problem I think).
[27 Apr 2019 18:09] Peter VARGA
Yes, I confirm, your suggestion fixed the problem.

Thank you for the very fast reply.