package mysql-server-5.7 5.7.22-0ubuntu0.16.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 137

Bug #1768698 reported by rogerio fredo vieira
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mysql-5.7 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

after installation, it doesn't work.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.22-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
AptOrdering:
 mysql-server-5.7: Configure
 mysql-server: Configure
 NULL: ConfigurePending
Architecture: i386
Date: Thu Apr 26 23:52:22 2018
DpkgTerminalLog:
 Configurando mysql-server-5.7 (5.7.22-0ubuntu0.16.04.1) ...
 /var/lib/dpkg/info/mysql-server-5.7.postinst: linha 40: 7295 Morto invoke-rc.d mysql $1
 dpkg: erro ao processar o pacote mysql-server-5.7 (--configure):
  sub-processo script post-installation instalado retornou estado de saída de erro 137
ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 137
InstallationDate: Installed on 2017-06-26 (311 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.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: ['mysql_upgrade_info', 'ib_logfile0', 'ibtmp1', 'mysql', 'phpmyadmin', 'ib_logfile1', 'ibdata1', 'ib_buffer_pool', 'auto.cnf', 'debian-5.7.flag', 'sys', 'performance_schema']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=6395f1b3-b7d7-41ca-bdf7-f60d3359fcdc ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.20
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.22-0ubuntu0.16.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 137
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
rogerio fredo vieira (fredovieira) wrote :
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi Rogerio,
neither the mysql error log nor the journal that you auto-attached contain useful hints to help you.
If anything then I'd wonder about:
2018-05-03T01:48:33.898935Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.22-0ubuntu0.16.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
2018-05-03T01:48:33.900092Z 2 [Note] Access denied for user 'root'@'localhost' (using password: NO)

You said this is a clean install of mysql.
So is the problem reproducible if you purge and install it again?

$ apt remove --purge mysql-server mysql-server-5.7 mysql-server-core-5.7
$ apt install mysql-server

Is that just running into the SAME issue again?
If so please share your right after the fail
- /var/log/mysql/error.log
- the ouput of journalctl -xe
- the ouput of your console since you started with the commands above

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration.
But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting the service will work.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then 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.

Changed in mysql-5.7 (Ubuntu):
status: New → Incomplete
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.