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).
Description: Ubuntu 13.10
Release: 13.10
mysql-server-5.5: 0ubuntu0. 13.10.1 0ubuntu0. 13.10.1 0ubuntu0. 13.10.1 0 us-east- 1.ec2.archive. ubuntu. com/ubuntu/ saucy-updates/main amd64 Packages security. ubuntu. com/ubuntu/ saucy-security/main amd64 Packages dpkg/status 5.32-0ubuntu7 0 us-east- 1.ec2.archive. ubuntu. com/ubuntu/ saucy/main amd64 Packages
Installed: 5.5.35-
Candidate: 5.5.35-
Version table:
*** 5.5.35-
500 http://
500 http://
100 /var/lib/
5.
500 http://
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).