package mysql-server-5.7 5.7.17-0ubuntu0.16.10.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

Bug #1666048 reported by belmin
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mysql-5.7 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

It does not work :(

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: mysql-server-5.7 5.7.17-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Sun Feb 19 15:47:20 2017
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2017-02-12 (7 days ago)
InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
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: ['sys', 'ib_logfile1', 'auto.cnf', 'ibtmp1', 'debian-5.7.flag', 'ib_logfile0', 'performance_schema', 'ib_buffer_pool', 'ibdata1', 'mysql']
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-37-generic root=UUID=4cc51162-958c-4984-bbad-50cfbb52e0ae ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt 1.3.4
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.17-0ubuntu0.16.10.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
belmin (belmin) wrote :
Revision history for this message
Marc Deslauriers (mdeslaur) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi,
from your log I see:
2017-02-19T14:47:51.800982Z 0 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
2017-02-19T14:47:51.800985Z 0 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2017-02-19T14:47:51.800996Z 0 [ERROR] Aborting

And that was right about the time when the install log tried to install.
I've seen in the mysql error log that later on the same day about 4 hours later the server started.

Did you have to resolve a configuration issue?
Usually when I see this issue it is one of:
- second mysql server installed from a 3rd party source blocking the port
- configuration issue that can be resolved by purging/re-installing (if no important config existed before)
- configuration issue that had to be resolved by the admin.

Your logs indicate the latter but also that you might already have achived it.
Might I ask what the latest status on this is?

Also if purge/reinstall of mysql is an option (no custom data/config yet) could you try and let me know that helped?

Changed in mysql-5.7 (Ubuntu):
status: New → Incomplete
Revision history for this message
Andreas Schirra (preludi) wrote :

I am a bit astonished that this bug is unassigned. Please assign it and check the root cause. Thanks in advance

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in mysql-5.7 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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