unable to start any service via upstart script, sysvinit scripts work fine though

[Jeff Lane ]

NOTE: I originally filed this against mysql-server, but in reality what I'm seeing affects pretty much every upstart job. I can't start them, stop them, or query them. I can do fine if I delete the upstart script causing 'service' to fall back to sysvinit scripts in /etc/init.d/ however.

Installed mysql-server meta package which pulled in mysql-server-5.5 and mysql-server-core-5.5 which created both an upstart script (attached) and a sysvinit script.

When starting mysql via the service command, the presense of the upstart script causes that script to be used in preference of the sysvinit script. The problem is, with the upstart script present in /etc/init, it is impossible to start or stop the mysql service:

bladernr@klaatu:~/development/devstack$ sudo service mysql status
status: Unknown job: mysql
bladernr@klaatu:~/development/devstack$ sudo service mysql restart
stop: Unknown job: mysql
start: Unknown job: mysql
bladernr@klaatu:~/development/devstack$ sudo service mysql stop
stop: Unknown job: mysql

Now, if I remove the upstart script causing service to fall back on the sysvinit script, I am able to stop, start and do other things with the mysql service:

bladernr@klaatu:~/development/devstack$ sudo mv /etc/init/mysql.conf .
bladernr@klaatu:~/development/devstack$ sudo service mysql status
 * /usr/bin/mysqladmin Ver 8.42 Distrib 5.5.31, for debian-linux-gnu on x86_64
Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Server version 5.5.31-0ubuntu1-log
Protocol version 10
Connection Localhost via UNIX socket
UNIX socket /var/run/mysqld/mysqld.sock
Uptime: 5 hours 27 min 56 sec

Threads: 1 Questions: 572 Slow queries: 432 Opens: 421 Flush tables: 1 Open tables: 41 Queries per second avg: 0.029
bladernr@klaatu:~/development/devstack$ sudo service mysql restart
 * Stopping MySQL database server mysqld [ OK ]
 * Starting MySQL database server mysqld [ OK ]
 * Checking for tables which need an upgrade, are corrupt or were
not closed cleanly.

So the problem appears to be with the upstart job on Saucy.

I tried this also on a second machine running raring with mysql-server-5.5 (5.5.31-0ubuntu0.13.04.1) and mysql-server-core-5.5 (5.5.31-0ubuntu0.14.04.1) and am able to successfully start and stop the mysql service using the upstart script via service:

bladernr@garbagescow:~$ find /etc -name mysql.conf
/etc/init/mysql.conf
bladernr@garbagescow:~$ sudo service mysql restart
mysql stop/waiting
mysql start/running, process 5825

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: mysql-server 5.5.31-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
Date: Mon Jul 15 18:04:22 2013
InstallationDate: Installed on 2012-03-15 (487 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120307)
Logs.var.log.daemon.log:

MarkForUpload: True
MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf:
 [mysqld_safe]
 syslog
MySQLVarLibDirListing: False
PackageArchitecture: all
SourcePackage: mysql-5.5
UpgradeStatus: Upgraded to saucy on 2013-06-22 (23 days ago)

[Jeff Lane  (bladernr)]

I tried removing and re-installing mysql, and even during the installation of the package, the server is unable to start via upstart:

bladernr@klaatu:~/development/devstack$ sudo apt-get install mysql-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  mysql-server-5.5 mysql-server-core-5.5
Suggested packages:
  tinyca
The following NEW packages will be installed:
  mysql-server mysql-server-5.5 mysql-server-core-5.5
0 upgraded, 3 newly installed, 0 to remove and 77 not upgraded.
Need to get 0 B/14.8 MB of archives.
After this operation, 52.5 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Preconfiguring packages ...
Selecting previously unselected package mysql-server-core-5.5.
(Reading database ... 400070 files and directories currently installed.)
Unpacking mysql-server-core-5.5 (from .../mysql-server-core-5.5_5.5.31-0ubuntu1_amd64.deb) ...
Selecting previously unselected package mysql-server-5.5.
Unpacking mysql-server-5.5 (from .../mysql-server-5.5_5.5.31-0ubuntu1_amd64.deb) ...
Selecting previously unselected package mysql-server.
Unpacking mysql-server (from .../mysql-server_5.5.31-0ubuntu1_all.deb) ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Setting up mysql-server-core-5.5 (5.5.31-0ubuntu1) ...
Setting up mysql-server-5.5 (5.5.31-0ubuntu1) ...
initctl: Unknown job: mysql
130716 9:40:45 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' instead.
initctl: Unknown job: mysql
Processing triggers for ureadahead ...
Setting up mysql-server (5.5.31-0ubuntu1) ...

Note the instances of "initctl: Unknown job: mysql"

and again, if I remove the upstart script, it starts just fine:
bladernr@klaatu:~/development/devstack$ sudo rm -f /etc/init/mysql.conf
bladernr@klaatu:~/development/devstack$ sudo service mysql start
 * Starting MySQL database server mysqld [ OK ]

I also looked at the tgt daemon which I also noticed was failing when trying to install devstack:

bladernr@klaatu:~/development/devstack$ sudo service tgt start
start: Unknown job: tgt
bladernr@klaatu:~/development/devstack$ sudo rm /etc/init/tgt.conf
bladernr@klaatu:~/development/devstack$ sudo service tgt start
 * Starting target framework daemon tgtd [ OK ]

In fact, I get the same "Unknown job" message for every single service that has an upstart script in /etc/init.

[Jeff Lane  (bladernr)]

I also retried doing this a couple ways:

bladernr@klaatu:~/development/devstack$ sudo start mysql
start: Unknown job: mysql
bladernr@klaatu:~/development/devstack$ sudo service start mysql
start: unrecognized service
bladernr@klaatu:~/development/devstack$ sudo start mysql
start: Unknown job: mysql
bladernr@klaatu:~/development/devstack$ sudo service mysql start
start: Unknown job: mysql
bladernr@klaatu:~/development/devstack$ sudo rm /etc/init/mysql.conf
bladernr@klaatu:~/development/devstack$ sudo start mysql
start: Unknown job: mysql
bladernr@klaatu:~/development/devstack$ sudo service mysql start
 * Starting MySQL database server mysqld [ OK ]

[Brian Murray (brian-murray)]

I was unable to recreate this in a schroot of saucy using the same package version of mysql. Comparing your msql.conf and mine they are the same.

I also tried install tgt and that did not create the problem either. I wonder if it some other upstart job in /etc/init causing the problem. You might trying running init-checkconf against every file in there.

[Aaron Brady (bradya)]

I have this problem after installing mysql-server - it's like the job is not picked up. Doing a `kill -HUP 1` causes things to work how they should, and then I can start and stop the mysql job.

I am running within an LXC container on Precise.

[Brian Murray (brian-murray)]

Aaron - could you try checking your other files in /etc/init as I suggested in comment #4?

[Launchpad Janitor (janitor)]

[Expired for upstart (Ubuntu) because there has been no activity for 60 days.]