[Bug 1273462] Re: init.d/mysql is erroneously supplied, and using it causes problems

[Robie Basak]

I just spoke to Stéphane Graber about this. AIUI, this should be fixed
in lsb-base, so that Sys V init scripts that source /lib/lsb/init-
functions will correctly handle the case that an upstart job exists and
not let you run it.

** Summary changed:

- init.d/mysql is erroneously supplied, and using it causes problems
+ Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists

** Changed in: mysql-5.5 (Ubuntu)
       Status: Triaged => Invalid

** Also affects: lsb (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: lsb (Ubuntu)
       Status: New => Triaged

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

Title:
  Users can mistakenly run init.d scripts and cause problems if an
  equivalent upstart job already exists

Status in “mysql-5.5” package in Ubuntu:
  Invalid
Status in “upstart” package in Ubuntu:
  Triaged

Bug description:
  
  Description:    Ubuntu 13.10
  Release:        13.10

  mysql-server-5.5:
    Installed: 5.5.35-0ubuntu0.13.10.1
    Candidate: 5.5.35-0ubuntu0.13.10.1
    Version table:
   *** 5.5.35-0ubuntu0.13.10.1 0
          500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages
          500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 Packages
          100 /var/lib/dpkg/status
       5.5.32-0ubuntu7 0
          500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

  
  In Ubuntu 13.10, the Upstart job and the init.d script do not work properly.  In previous versions, the init.d script was a symlink to the wrapper script around upstart (/lib/init/upstart-job).  This conflict means that if the server was started using the init.d script, upstart does not recognize that the server is running and will attempt to start a second instance of mysqld.

  Also problematic is that if the upstart job is started using the
  service or start commands, the init.d script's "stop" function runs a
  mysql shutdown, but upstart simply restarts mysqld (because it's
  marked respawn in the upstart config).

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