Are there files in /var/lib/mysql (or other location if a custom datadir
is used) or /etc/mysql before installation? Even if it's a "fresh"
install there may be files present in those locations, and then MySQL
would try to continue using them.
Older packages also didn't remove any of these files when purging (newer
packages should ask if you want to erase data and config files completely).
Try renaming /etc/mysql and /var/lib/mysql (or just erase if you are
sure you don't need anything there) before installing.
--
Lars
On 04/14/2017 05:03 PM, Eduard Bloch wrote:
Package: mysql-server
Version: 5.7.17-1
Severity: important
Situation: attempting to install mysql-server and some dependent
packages
Result: installation fails, the dpkg configuration phase is aborted.
Reason is mysql-server postinst, failing to start a systemd unit.
Stronger investigation is inconclusive. dpkg.log says this is a fresh
installation... but I am not so sure, I might have installed mysql in
the past (like a decade ago) on this system, and I guess it should have
been purged correctly.
Apr 14 12:51:05 whitestar systemd[1]: Starting MySQL Community Server...
Apr 14 12:51:06 whitestar systemd[1]: mysql.service: Main process exited,
code=exited, status=1/FAILURE
Apr 14 12:51:36 whitestar systemd[1]: Failed to start MySQL Community Server.
Apr 14 12:51:36 whitestar systemd[1]: mysql.service: Unit entered failed state.
Apr 14 12:51:36 whitestar systemd[1]: mysql.service: Failed with result
'exit-code'.
2017-04-14T14:52:23.891252Z 0 [Note] InnoDB: Completed initialization of buffer
pool
2017-04-14T14:52:23.893681Z 0 [Note] InnoDB: If the mysqld execution user is
authorized, page cleaner thread priority can be changed. See the man page of
setpriority().
2017-04-14T14:52:23.903988Z 0 [ERROR] InnoDB: The Auto-extending innodb_system
data file './ibdata1' is of a different size 640 pages (rounded down to MB)
than specified in the .cnf file: initial 768 pages, max 0 (relevant if
non-zero) pages!
2017-04-14T14:52:23.904034Z 0 [ERROR] InnoDB: Plugin initialization aborted
with error Generic error
2017-04-14T14:52:24.505591Z 0 [ERROR] Plugin 'InnoDB' init function returned
error.
2017-04-14T14:52:24.505663Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE
ENGINE failed.
2017-04-14T14:52:24.505682Z 0 [ERROR] Failed to initialize plugins.
2017-04-14T14:52:24.505696Z 0 [ERROR] Aborting
2017-04-14T14:52:24.505712Z 0 [Note] Binlog end
2017-04-14T14:52:24.505831Z 0 [Note] Shutting down plugin 'CSV'
2017-04-14T14:52:24.506954Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
-- System Information:
Debian Release: 9.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.11.0-rc6 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages mysql-server depends on:
ih mysql-server-5.7 5.7.17-1
mysql-server recommends no packages.
mysql-server suggests no packages.
-- no debconf information
_______________________________________________
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint
