Hi Wahaj,
you mysql service fails to start - from the log:
● mysql.service - MySQL Community Server
   Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: 
enabled)
   Active: activating (auto-restart) (Result: exit-code) since Sat 2017-06-24 
15:28:19 PKT; 82ms ago
  Process: 18677 ExecStartPost=/usr/share/mysql/mysql-systemd-start post 
(code=exited, status=0/SUCCESS)
  Process: 18674 ExecStart=/usr/sbin/mysqld (code=exited, 
status=1/FAILURE)
  Process: 18668 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre 
(code=exited, status=0/SUCCESS)
 Main PID: 18674 (code=exited, status=1/FAILURE)

Jun 24 15:28:19 INSIRON-mini systemd[1]: mysql.service: Unit entered 
failed …te.
Jun 24 15:28:19 INSIRON-mini systemd[1]: mysql.service: Failed with 
result '…e'.

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.

Mostly the best log to see what is going wrong is the mysql error log,
but it was not attached on this bug report.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700397

Title:
  package mysql-server-5.7 5.7.18-0ubuntu0.17.04.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1700397/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to