group.of.nepali.translators team mailing list archive

[Robie Basak <1602763@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

[Impact]

A common cause of upgrade failures are invalid configuration directives
due to deprecation. In this kind of case, apport does not currently tell
us the failure reason, and even if it did print a service start failure,
the actual reason has to be dug out of the logs. Further, some users
have a very old conffile that did not log output to the current
location, so the real reason isn't always submitted in a bug report.

We can ask if mysqld will start by using: "mysqld --verbose --help
--innodb-read-only 2>&1 > /dev/null". The postinst should do this so
that it can fail early with a more useful error message.

This is fixed in Yakkety already (http://anonscm.debian.org/cgit/pkg-
mysql/mysql.git/commit/?id=7897042ea6c65aeb608fb28b4b54639d3dbf3352) but
should also be SRU'd to Xenial.

Also see bug 1596056 and bug 1571865. Fixing each of these will improve
the situation in a different way. Fixing all three bugs would catch the
most failure cases and be the most helpful.

** Affects: mysql-5.7 (Ubuntu)
     Importance: Medium
         Status: Fix Released

** Affects: mysql-5.7 (Ubuntu Xenial)
     Importance: Undecided
     Assignee: Robie Basak (racb)
         Status: In Progress

** Also affects: mysql-5.7 (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: mysql-5.7 (Ubuntu Xenial)
       Status: New => In Progress

** Changed in: mysql-5.7 (Ubuntu Xenial)
     Assignee: (unassigned) => Robie Basak (racb)

** Description changed:

  [Impact]
  
  A common cause of upgrade failures are invalid configuration directives
  due to deprecation. In this kind of case, apport does not currently tell
  us the failure reason, and even if it did print a service start failure,
  the actual reason has to be dug out of the logs. Further, some users
  have a very old conffile that did not log output to the current
  location, so the real reason isn't always submitted in a bug report.
  
  We can ask if mysqld will start by using: "mysqld --verbose --help
  --innodb-read-only 2>&1 > /dev/null". The postinst should do this so
  that it can fail early with a more useful error message.
  
  This is fixed in Yakkety already (http://anonscm.debian.org/cgit/pkg-
  mysql/mysql.git/commit/?id=7897042ea6c65aeb608fb28b4b54639d3dbf3352) but
  should also be SRU'd to Xenial.
  
- Also see bug 1596056 and 1571865. Fixing each of these will improve the
- situation in a different way. Fixing all three bugs would catch the most
- failure cases and be the most helpful.
+ Also see bug 1596056 and bug 1571865. Fixing each of these will improve
+ the situation in a different way. Fixing all three bugs would catch the
+ most failure cases and be the most helpful.

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1602763

Title:
  postinst does not print a helpful message when the server will fail to
  start

Status in mysql-5.7 package in Ubuntu:
  Fix Released
Status in mysql-5.7 source package in Xenial:
  In Progress

Bug description:
  [Impact]

  A common cause of upgrade failures are invalid configuration
  directives due to deprecation. In this kind of case, apport does not
  currently tell us the failure reason, and even if it did print a
  service start failure, the actual reason has to be dug out of the
  logs. Further, some users have a very old conffile that did not log
  output to the current location, so the real reason isn't always
  submitted in a bug report.

  We can ask if mysqld will start by using: "mysqld --verbose --help
  --innodb-read-only 2>&1 > /dev/null". The postinst should do this so
  that it can fail early with a more useful error message.

  This is fixed in Yakkety already (http://anonscm.debian.org/cgit/pkg-
  mysql/mysql.git/commit/?id=7897042ea6c65aeb608fb28b4b54639d3dbf3352)
  but should also be SRU'd to Xenial.

  Also see bug 1596056 and bug 1571865. Fixing each of these will
  improve the situation in a different way. Fixing all three bugs would
  catch the most failure cases and be the most helpful.

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