| 2014-01-27 22:28:04 |
Eric Connell |
bug |
|
|
added bug |
| 2014-01-28 15:07:47 |
Robie Basak |
mysql-5.5 (Ubuntu): status |
New |
Triaged |
|
| 2014-01-28 15:07:51 |
Robie Basak |
mysql-5.5 (Ubuntu): importance |
Undecided |
Medium |
|
| 2014-01-28 15:07:54 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2014-01-28 15:08:14 |
Robie Basak |
summary |
Upstart job config and init.d script are incompatible with each other |
init.d/mysql is erroneously supplied, and using it causes problems |
|
| 2014-01-30 14:09:35 |
Robie Basak |
summary |
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 |
|
| 2014-01-30 14:09:41 |
Robie Basak |
mysql-5.5 (Ubuntu): status |
Triaged |
Invalid |
|
| 2014-01-30 14:09:55 |
Robie Basak |
bug task added |
|
lsb (Ubuntu) |
|
| 2014-01-30 14:10:39 |
Robie Basak |
lsb (Ubuntu): status |
New |
Triaged |
|
| 2014-01-30 14:13:39 |
Dimitri John Ledkov |
lsb (Ubuntu): importance |
Undecided |
Critical |
|
| 2014-01-30 14:13:41 |
Dimitri John Ledkov |
lsb (Ubuntu): assignee |
|
Dimitri John Ledkov (xnox) |
|
| 2014-01-30 14:16:14 |
Dimitri John Ledkov |
affects |
lsb (Ubuntu) |
upstart (Ubuntu) |
|
| 2014-01-30 14:16:14 |
Dimitri John Ledkov |
upstart (Ubuntu): assignee |
Dimitri John Ledkov (xnox) |
|
|
| 2014-01-30 14:17:57 |
Dimitri John Ledkov |
upstart (Ubuntu): assignee |
|
Dimitri John Ledkov (xnox) |
|
| 2014-05-03 03:09:57 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Trusty |
|
| 2014-05-03 03:09:57 |
Dimitri John Ledkov |
bug task added |
|
upstart (Ubuntu Trusty) |
|
| 2014-05-03 03:09:57 |
Dimitri John Ledkov |
bug task added |
|
mysql-5.5 (Ubuntu Trusty) |
|
| 2014-05-03 03:09:57 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Utopic |
|
| 2014-05-03 03:09:57 |
Dimitri John Ledkov |
bug task added |
|
upstart (Ubuntu Utopic) |
|
| 2014-05-03 03:09:57 |
Dimitri John Ledkov |
bug task added |
|
mysql-5.5 (Ubuntu Utopic) |
|
| 2014-05-03 03:10:07 |
Dimitri John Ledkov |
mysql-5.5 (Ubuntu Trusty): status |
New |
Invalid |
|
| 2014-05-03 03:10:10 |
Dimitri John Ledkov |
upstart (Ubuntu Trusty): status |
New |
Triaged |
|
| 2014-05-03 03:10:14 |
Dimitri John Ledkov |
upstart (Ubuntu Trusty): importance |
Undecided |
High |
|
| 2014-05-03 03:10:16 |
Dimitri John Ledkov |
upstart (Ubuntu Trusty): assignee |
|
Dimitri John Ledkov (xnox) |
|
| 2014-05-03 03:10:20 |
Dimitri John Ledkov |
upstart (Ubuntu Utopic): status |
Triaged |
In Progress |
|
| 2014-05-03 03:13:14 |
Dimitri John Ledkov |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712763 |
|
| 2014-05-03 03:13:14 |
Dimitri John Ledkov |
bug task added |
|
upstart (Debian) |
|
| 2014-05-03 03:34:30 |
Dimitri John Ledkov |
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). |
[ impact ]
Previously, init.d scripts that were replaced by upstart jobs had "upstart-job" symlink as a redirect in-place, which directed users at using upstart commands. Despite the good intentions, that never actually taught people about the correct interfaces. Now with the advent of co-installability of multiple init systems, users may have systemd, upstart, and sysv-init all installed on users system and have init.d scripts / upstart jobs / systemd units all available. To avoid any daubt, we should support executing /etc/init.d/ scripts which may call into upstart, or into systemd, or actually execute the script in question depending on whether there is native configuration for that particular job and which init system we are running under.
[ test case ]
Invoking init.d script should invoke upstart commands, for example:
$ /etc/init.d/ssh status
ssh start/running, process 4620
$ /etc/init.d/ssh stop
stop: Rejected send message, 1 matched rules; type="method_call", sender=":1.2469694" (uid=1000 pid=3908 comm="stop ssh ") interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init")
$ sudo /etc/init.d/ssh stop
ssh stop/waiting
$ sudo /etc/init.d/ssh start
ssh start/running, process 5373
$ sudo /etc/init.d/ssh restart
ssh stop/waiting
ssh start/running, process 5405
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). |
|
| 2014-05-03 04:59:53 |
Bug Watch Updater |
upstart (Debian): status |
Unknown |
New |
|
| 2014-05-07 20:28:06 |
Launchpad Janitor |
upstart (Ubuntu Utopic): status |
In Progress |
Fix Released |
|
| 2014-05-09 03:29:05 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/trusty/upstart |
|
| 2014-06-20 11:00:57 |
Dimitri John Ledkov |
upstart (Ubuntu Trusty): status |
Triaged |
Won't Fix |
|
| 2014-06-20 11:01:05 |
Dimitri John Ledkov |
bug task added |
|
lsb (Ubuntu) |
|
| 2014-06-20 11:01:19 |
Dimitri John Ledkov |
lsb (Ubuntu Utopic): status |
New |
Fix Released |
|
| 2014-06-20 11:01:29 |
Dimitri John Ledkov |
lsb (Ubuntu Trusty): status |
New |
Confirmed |
|
| 2014-06-20 11:01:44 |
Dimitri John Ledkov |
lsb (Ubuntu Trusty): importance |
Undecided |
High |
|
| 2014-06-20 11:03:02 |
Dimitri John Ledkov |
lsb (Ubuntu Trusty): assignee |
|
Dimitri John Ledkov (xnox) |
|
| 2014-06-30 10:43:38 |
Nick Moffitt |
bug |
|
|
added subscriber The Canonical Sysadmins |
| 2015-04-30 13:27:41 |
Jan Groenewald |
bug |
|
|
added subscriber AIMS |
| 2015-06-23 15:18:45 |
Michael Cunningham |
bug |
|
|
added subscriber Michael Cunningham |
| 2015-07-14 16:58:53 |
Edward Hope-Morley |
attachment added |
|
trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1273462/+attachment/4428923/+files/trusty.debdiff |
|
| 2015-07-14 18:25:16 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2015-07-17 03:55:16 |
Hua Zhang |
attachment added |
|
trusty_v2.debdiff https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1273462/+attachment/4430332/+files/trusty_v2.debdiff |
|
| 2015-07-17 04:22:16 |
Hua Zhang |
description |
[ impact ]
Previously, init.d scripts that were replaced by upstart jobs had "upstart-job" symlink as a redirect in-place, which directed users at using upstart commands. Despite the good intentions, that never actually taught people about the correct interfaces. Now with the advent of co-installability of multiple init systems, users may have systemd, upstart, and sysv-init all installed on users system and have init.d scripts / upstart jobs / systemd units all available. To avoid any daubt, we should support executing /etc/init.d/ scripts which may call into upstart, or into systemd, or actually execute the script in question depending on whether there is native configuration for that particular job and which init system we are running under.
[ test case ]
Invoking init.d script should invoke upstart commands, for example:
$ /etc/init.d/ssh status
ssh start/running, process 4620
$ /etc/init.d/ssh stop
stop: Rejected send message, 1 matched rules; type="method_call", sender=":1.2469694" (uid=1000 pid=3908 comm="stop ssh ") interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init")
$ sudo /etc/init.d/ssh stop
ssh stop/waiting
$ sudo /etc/init.d/ssh start
ssh start/running, process 5373
$ sudo /etc/init.d/ssh restart
ssh stop/waiting
ssh start/running, process 5405
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). |
[ impact ]
Previously, init.d scripts that were replaced by upstart jobs had "upstart-job" symlink as a redirect in-place, which directed users at using upstart commands. Despite the good intentions, that never actually taught people about the correct interfaces. Now with the advent of co-installability of multiple init systems, users may have systemd, upstart, and sysv-init all installed on users system and have init.d scripts / upstart jobs / systemd units all available. To avoid any daubt, we should support executing /etc/init.d/ scripts which may call into upstart, or into systemd, or actually execute the script in question depending on whether there is native configuration for that particular job and which init system we are running under.
[ test case ]
Invoking init.d script should invoke upstart commands, for example:
$ /etc/init.d/ssh status
ssh start/running, process 4620
$ /etc/init.d/ssh stop
stop: Rejected send message, 1 matched rules; type="method_call", sender=":1.2469694" (uid=1000 pid=3908 comm="stop ssh ") interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init")
$ sudo /etc/init.d/ssh stop
ssh stop/waiting
$ sudo /etc/init.d/ssh start
ssh start/running, process 5373
$ sudo /etc/init.d/ssh restart
ssh stop/waiting
ssh start/running, process 5405
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).
Description: Ubuntu 14.04
Release: 14.04
mysql: mysql-server-5.5.43-0ubuntu0.14.04.1
The problem in some setup was that the upgrade von 12.04 to 14.04 requres the adjustment of the InnoDB log size. Therefore the start of MySQL via upstart failed directly while the one via init started successfully and then failed as below.
root@webserver01.kurt..ref:~# status mysql
mysql start/running, process 5866
root@webserver01.kurt..ref:~# /etc/init.d/mysql stop
* Stopping MySQL database server mysqld [ OK ]
root@webserver01.kurt..ref:~# status mysql
mysql start/running, process 6101
root@webserver01.kurt..ref:~# /etc/init.d/mysql status
* /usr/bin/mysqladmin Ver 8.42 Distrib 5.5.43, for debian-linux-gnu on x86_64
Copyright (c) 2000, 2015, 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.43-0ubuntu0.14.04.1-log
Protocol version 10
Connection Localhost via UNIX socket
UNIX socket /var/run/mysqld/mysqld.sock
Uptime: 7 sec
Threads: 1 Questions: 108 Slow queries: 0 Opens: 48 Flush tables: 1 Open tables: 41 Queries per second avg: 15.428
root@webserver01.kurt..ref:~# stop mysql
mysql stop/waiting
root@webserver01.kurt..ref:~# /etc/init.d/mysql status
* MySQL is stopped.
This is horrible. The "status" commands report the wrong status and the start/stop commands do not work. If our operators are not super careful, our orchestration and monitoring system will go wild, report the wrong status and/or perform continuous restarts of the system as they think the service is not running. So we also fix it in trusty. the result will looks as below:
ubuntu@maas:~/work/deb$ sudo start mysql
mysql start/running, process 8523
ubuntu@maas:~/work/deb$ sudo status mysql
mysql start/running, process 8523
ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql stop
mysql stop/waiting
ubuntu@maas:~/work/deb$ sudo status mysql
mysql stop/waiting
ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql status
mysql stop/waiting
[Regression Potential]
* None |
|
| 2015-07-20 09:34:05 |
Hua Zhang |
attachment removed |
trusty_v2.debdiff https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1273462/+attachment/4430332/+files/trusty_v2.debdiff |
|
|
| 2015-07-20 09:34:20 |
Hua Zhang |
attachment removed |
trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1273462/+attachment/4428923/+files/trusty.debdiff |
|
|
| 2015-07-20 09:36:36 |
Hua Zhang |
attachment added |
|
trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1273462/+attachment/4431508/+files/trusty.debdiff |
|
| 2015-07-24 14:59:58 |
Edward Hope-Morley |
lsb (Ubuntu Trusty): assignee |
Dimitri John Ledkov (xnox) |
Hua Zhang (zhhuabj) |
|
| 2015-07-24 15:00:17 |
Edward Hope-Morley |
lsb (Ubuntu Trusty): status |
Confirmed |
In Progress |
|
| 2015-07-24 15:01:01 |
Edward Hope-Morley |
tags |
init scripts upstart |
init scripts sts upstart |
|
| 2015-07-30 20:35:15 |
Tony Garcia |
bug |
|
|
added subscriber tonyskapunk |
| 2015-08-06 16:34:20 |
Chris J Arges |
attachment added |
|
fix-lp1273462-trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1273462/+attachment/4440530/+files/fix-lp1273462-trusty.debdiff |
|
| 2015-08-06 16:34:24 |
Chris J Arges |
attachment added |
|
fix-lp1273462-trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1273462/+attachment/4440531/+files/fix-lp1273462-trusty.debdiff |
|
| 2015-08-06 16:35:04 |
Chris J Arges |
description |
[ impact ]
Previously, init.d scripts that were replaced by upstart jobs had "upstart-job" symlink as a redirect in-place, which directed users at using upstart commands. Despite the good intentions, that never actually taught people about the correct interfaces. Now with the advent of co-installability of multiple init systems, users may have systemd, upstart, and sysv-init all installed on users system and have init.d scripts / upstart jobs / systemd units all available. To avoid any daubt, we should support executing /etc/init.d/ scripts which may call into upstart, or into systemd, or actually execute the script in question depending on whether there is native configuration for that particular job and which init system we are running under.
[ test case ]
Invoking init.d script should invoke upstart commands, for example:
$ /etc/init.d/ssh status
ssh start/running, process 4620
$ /etc/init.d/ssh stop
stop: Rejected send message, 1 matched rules; type="method_call", sender=":1.2469694" (uid=1000 pid=3908 comm="stop ssh ") interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init")
$ sudo /etc/init.d/ssh stop
ssh stop/waiting
$ sudo /etc/init.d/ssh start
ssh start/running, process 5373
$ sudo /etc/init.d/ssh restart
ssh stop/waiting
ssh start/running, process 5405
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).
Description: Ubuntu 14.04
Release: 14.04
mysql: mysql-server-5.5.43-0ubuntu0.14.04.1
The problem in some setup was that the upgrade von 12.04 to 14.04 requres the adjustment of the InnoDB log size. Therefore the start of MySQL via upstart failed directly while the one via init started successfully and then failed as below.
root@webserver01.kurt..ref:~# status mysql
mysql start/running, process 5866
root@webserver01.kurt..ref:~# /etc/init.d/mysql stop
* Stopping MySQL database server mysqld [ OK ]
root@webserver01.kurt..ref:~# status mysql
mysql start/running, process 6101
root@webserver01.kurt..ref:~# /etc/init.d/mysql status
* /usr/bin/mysqladmin Ver 8.42 Distrib 5.5.43, for debian-linux-gnu on x86_64
Copyright (c) 2000, 2015, 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.43-0ubuntu0.14.04.1-log
Protocol version 10
Connection Localhost via UNIX socket
UNIX socket /var/run/mysqld/mysqld.sock
Uptime: 7 sec
Threads: 1 Questions: 108 Slow queries: 0 Opens: 48 Flush tables: 1 Open tables: 41 Queries per second avg: 15.428
root@webserver01.kurt..ref:~# stop mysql
mysql stop/waiting
root@webserver01.kurt..ref:~# /etc/init.d/mysql status
* MySQL is stopped.
This is horrible. The "status" commands report the wrong status and the start/stop commands do not work. If our operators are not super careful, our orchestration and monitoring system will go wild, report the wrong status and/or perform continuous restarts of the system as they think the service is not running. So we also fix it in trusty. the result will looks as below:
ubuntu@maas:~/work/deb$ sudo start mysql
mysql start/running, process 8523
ubuntu@maas:~/work/deb$ sudo status mysql
mysql start/running, process 8523
ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql stop
mysql stop/waiting
ubuntu@maas:~/work/deb$ sudo status mysql
mysql stop/waiting
ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql status
mysql stop/waiting
[Regression Potential]
* None |
[ impact ]
Previously, init.d scripts that were replaced by upstart jobs had "upstart-job" symlink as a redirect in-place, which directed users at using upstart commands. Despite the good intentions, that never actually taught people about the correct interfaces. Now with the advent of co-installability of multiple init systems, users may have systemd, upstart, and sysv-init all installed on users system and have init.d scripts / upstart jobs / systemd units all available. To avoid any doubt, we should support executing /etc/init.d/ scripts which may call into upstart, or into systemd, or actually execute the script in question depending on whether there is native configuration for that particular job and which init system we are running under.
[ test case ]
Invoking init.d script should invoke upstart commands, for example:
$ /etc/init.d/ssh status
ssh start/running, process 4620
$ /etc/init.d/ssh stop
stop: Rejected send message, 1 matched rules; type="method_call", sender=":1.2469694" (uid=1000 pid=3908 comm="stop ssh ") interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init")
$ sudo /etc/init.d/ssh stop
ssh stop/waiting
$ sudo /etc/init.d/ssh start
ssh start/running, process 5373
$ sudo /etc/init.d/ssh restart
ssh stop/waiting
ssh start/running, process 5405
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).
Description: Ubuntu 14.04
Release: 14.04
mysql: mysql-server-5.5.43-0ubuntu0.14.04.1
The problem in some setup was that the upgrade von 12.04 to 14.04 requres the adjustment of the InnoDB log size. Therefore the start of MySQL via upstart failed directly while the one via init started successfully and then failed as below.
root@webserver01.kurt..ref:~# status mysql
mysql start/running, process 5866
root@webserver01.kurt..ref:~# /etc/init.d/mysql stop
* Stopping MySQL database server mysqld [ OK ]
root@webserver01.kurt..ref:~# status mysql
mysql start/running, process 6101
root@webserver01.kurt..ref:~# /etc/init.d/mysql status
* /usr/bin/mysqladmin Ver 8.42 Distrib 5.5.43, for debian-linux-gnu on x86_64
Copyright (c) 2000, 2015, 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.43-0ubuntu0.14.04.1-log
Protocol version 10
Connection Localhost via UNIX socket
UNIX socket /var/run/mysqld/mysqld.sock
Uptime: 7 sec
Threads: 1 Questions: 108 Slow queries: 0 Opens: 48 Flush tables: 1 Open tables: 41 Queries per second avg: 15.428
root@webserver01.kurt..ref:~# stop mysql
mysql stop/waiting
root@webserver01.kurt..ref:~# /etc/init.d/mysql status
* MySQL is stopped.
This is horrible. The "status" commands report the wrong status and the start/stop commands do not work. If our operators are not super careful, our orchestration and monitoring system will go wild, report the wrong status and/or perform continuous restarts of the system as they think the service is not running. So we also fix it in trusty. the result will looks as below:
ubuntu@maas:~/work/deb$ sudo start mysql
mysql start/running, process 8523
ubuntu@maas:~/work/deb$ sudo status mysql
mysql start/running, process 8523
ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql stop
mysql stop/waiting
ubuntu@maas:~/work/deb$ sudo status mysql
mysql stop/waiting
ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql status
mysql stop/waiting
[Regression Potential]
* None |
|
| 2015-08-07 10:08:27 |
Hua Zhang |
description |
[ impact ]
Previously, init.d scripts that were replaced by upstart jobs had "upstart-job" symlink as a redirect in-place, which directed users at using upstart commands. Despite the good intentions, that never actually taught people about the correct interfaces. Now with the advent of co-installability of multiple init systems, users may have systemd, upstart, and sysv-init all installed on users system and have init.d scripts / upstart jobs / systemd units all available. To avoid any doubt, we should support executing /etc/init.d/ scripts which may call into upstart, or into systemd, or actually execute the script in question depending on whether there is native configuration for that particular job and which init system we are running under.
[ test case ]
Invoking init.d script should invoke upstart commands, for example:
$ /etc/init.d/ssh status
ssh start/running, process 4620
$ /etc/init.d/ssh stop
stop: Rejected send message, 1 matched rules; type="method_call", sender=":1.2469694" (uid=1000 pid=3908 comm="stop ssh ") interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init")
$ sudo /etc/init.d/ssh stop
ssh stop/waiting
$ sudo /etc/init.d/ssh start
ssh start/running, process 5373
$ sudo /etc/init.d/ssh restart
ssh stop/waiting
ssh start/running, process 5405
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).
Description: Ubuntu 14.04
Release: 14.04
mysql: mysql-server-5.5.43-0ubuntu0.14.04.1
The problem in some setup was that the upgrade von 12.04 to 14.04 requres the adjustment of the InnoDB log size. Therefore the start of MySQL via upstart failed directly while the one via init started successfully and then failed as below.
root@webserver01.kurt..ref:~# status mysql
mysql start/running, process 5866
root@webserver01.kurt..ref:~# /etc/init.d/mysql stop
* Stopping MySQL database server mysqld [ OK ]
root@webserver01.kurt..ref:~# status mysql
mysql start/running, process 6101
root@webserver01.kurt..ref:~# /etc/init.d/mysql status
* /usr/bin/mysqladmin Ver 8.42 Distrib 5.5.43, for debian-linux-gnu on x86_64
Copyright (c) 2000, 2015, 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.43-0ubuntu0.14.04.1-log
Protocol version 10
Connection Localhost via UNIX socket
UNIX socket /var/run/mysqld/mysqld.sock
Uptime: 7 sec
Threads: 1 Questions: 108 Slow queries: 0 Opens: 48 Flush tables: 1 Open tables: 41 Queries per second avg: 15.428
root@webserver01.kurt..ref:~# stop mysql
mysql stop/waiting
root@webserver01.kurt..ref:~# /etc/init.d/mysql status
* MySQL is stopped.
This is horrible. The "status" commands report the wrong status and the start/stop commands do not work. If our operators are not super careful, our orchestration and monitoring system will go wild, report the wrong status and/or perform continuous restarts of the system as they think the service is not running. So we also fix it in trusty. the result will looks as below:
ubuntu@maas:~/work/deb$ sudo start mysql
mysql start/running, process 8523
ubuntu@maas:~/work/deb$ sudo status mysql
mysql start/running, process 8523
ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql stop
mysql stop/waiting
ubuntu@maas:~/work/deb$ sudo status mysql
mysql stop/waiting
ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql status
mysql stop/waiting
[Regression Potential]
* None |
[ impact ]
Previously, init.d scripts that were replaced by upstart jobs had "upstart-job" symlink as a redirect in-place, which directed users at using upstart commands. Despite the good intentions, that never actually taught people about the correct interfaces. Now with the advent of co-installability of multiple init systems, users may have systemd, upstart, and sysv-init all installed on users system and have init.d scripts / upstart jobs / systemd units all available. To avoid any doubt, we should support executing /etc/init.d/ scripts which may call into upstart, or into systemd, or actually execute the script in question depending on whether there is native configuration for that particular job and which init system we are running under.
[ test case ]
Invoking init.d script should invoke upstart commands, for example:
$ /etc/init.d/ssh status
ssh start/running, process 4620
$ /etc/init.d/ssh stop
stop: Rejected send message, 1 matched rules; type="method_call", sender=":1.2469694" (uid=1000 pid=3908 comm="stop ssh ") interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init")
$ sudo /etc/init.d/ssh stop
ssh stop/waiting
$ sudo /etc/init.d/ssh start
ssh start/running, process 5373
$ sudo /etc/init.d/ssh restart
ssh stop/waiting
ssh start/running, process 5405
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).
Description: Ubuntu 14.04
Release: 14.04
mysql: mysql-server-5.5.43-0ubuntu0.14.04.1
The problem in some setup was that the upgrade von 12.04 to 14.04 requres the adjustment of the InnoDB log size. Therefore the start of MySQL via upstart failed directly while the one via init started successfully and then failed as below.
root@webserver01.kurt..ref:~# status mysql
mysql start/running, process 5866
root@webserver01.kurt..ref:~# /etc/init.d/mysql stop
* Stopping MySQL database server mysqld [ OK ]
root@webserver01.kurt..ref:~# status mysql
mysql start/running, process 6101
root@webserver01.kurt..ref:~# /etc/init.d/mysql status
* /usr/bin/mysqladmin Ver 8.42 Distrib 5.5.43, for debian-linux-gnu on x86_64
Copyright (c) 2000, 2015, 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.43-0ubuntu0.14.04.1-log
Protocol version 10
Connection Localhost via UNIX socket
UNIX socket /var/run/mysqld/mysqld.sock
Uptime: 7 sec
Threads: 1 Questions: 108 Slow queries: 0 Opens: 48 Flush tables: 1 Open tables: 41 Queries per second avg: 15.428
root@webserver01.kurt..ref:~# stop mysql
mysql stop/waiting
root@webserver01.kurt..ref:~# /etc/init.d/mysql status
* MySQL is stopped.
This is horrible. The "status" commands report the wrong status and the start/stop commands do not work. If our operators are not super careful, our orchestration and monitoring system will go wild, report the wrong status and/or perform continuous restarts of the system as they think the service is not running. So we also fix it in trusty. the result will looks as below:
ubuntu@maas:~/work/deb$ sudo start mysql
mysql start/running, process 8523
ubuntu@maas:~/work/deb$ sudo status mysql
mysql start/running, process 8523
ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql stop
mysql stop/waiting
ubuntu@maas:~/work/deb$ sudo status mysql
mysql stop/waiting
ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql status
mysql stop/waiting
[Regression Potential]
* Some scripts call '/etc/init.d/<service> reload' will not work if upstart script lacks a reload function and the reload function of /etc/init.d/<service> also uses PID. because it's managed by upstart now (the PID file does not exist). We should enumerate all those bad scripts and make them do the correct thing. |
|
| 2015-09-01 16:01:58 |
Martin Pitt |
bug |
|
|
added subscriber Martin Pitt |
| 2015-09-01 16:15:00 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Server Team |
| 2015-09-02 15:09:45 |
Steve Langasek |
bug |
|
|
added subscriber Steve Langasek |
| 2015-09-17 15:45:30 |
Louis Bouchard |
bug |
|
|
added subscriber Louis Bouchard |
| 2015-10-20 14:52:44 |
Martin Pitt |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2015-10-20 19:35:59 |
Steve Langasek |
description |
[ impact ]
Previously, init.d scripts that were replaced by upstart jobs had "upstart-job" symlink as a redirect in-place, which directed users at using upstart commands. Despite the good intentions, that never actually taught people about the correct interfaces. Now with the advent of co-installability of multiple init systems, users may have systemd, upstart, and sysv-init all installed on users system and have init.d scripts / upstart jobs / systemd units all available. To avoid any doubt, we should support executing /etc/init.d/ scripts which may call into upstart, or into systemd, or actually execute the script in question depending on whether there is native configuration for that particular job and which init system we are running under.
[ test case ]
Invoking init.d script should invoke upstart commands, for example:
$ /etc/init.d/ssh status
ssh start/running, process 4620
$ /etc/init.d/ssh stop
stop: Rejected send message, 1 matched rules; type="method_call", sender=":1.2469694" (uid=1000 pid=3908 comm="stop ssh ") interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init")
$ sudo /etc/init.d/ssh stop
ssh stop/waiting
$ sudo /etc/init.d/ssh start
ssh start/running, process 5373
$ sudo /etc/init.d/ssh restart
ssh stop/waiting
ssh start/running, process 5405
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).
Description: Ubuntu 14.04
Release: 14.04
mysql: mysql-server-5.5.43-0ubuntu0.14.04.1
The problem in some setup was that the upgrade von 12.04 to 14.04 requres the adjustment of the InnoDB log size. Therefore the start of MySQL via upstart failed directly while the one via init started successfully and then failed as below.
root@webserver01.kurt..ref:~# status mysql
mysql start/running, process 5866
root@webserver01.kurt..ref:~# /etc/init.d/mysql stop
* Stopping MySQL database server mysqld [ OK ]
root@webserver01.kurt..ref:~# status mysql
mysql start/running, process 6101
root@webserver01.kurt..ref:~# /etc/init.d/mysql status
* /usr/bin/mysqladmin Ver 8.42 Distrib 5.5.43, for debian-linux-gnu on x86_64
Copyright (c) 2000, 2015, 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.43-0ubuntu0.14.04.1-log
Protocol version 10
Connection Localhost via UNIX socket
UNIX socket /var/run/mysqld/mysqld.sock
Uptime: 7 sec
Threads: 1 Questions: 108 Slow queries: 0 Opens: 48 Flush tables: 1 Open tables: 41 Queries per second avg: 15.428
root@webserver01.kurt..ref:~# stop mysql
mysql stop/waiting
root@webserver01.kurt..ref:~# /etc/init.d/mysql status
* MySQL is stopped.
This is horrible. The "status" commands report the wrong status and the start/stop commands do not work. If our operators are not super careful, our orchestration and monitoring system will go wild, report the wrong status and/or perform continuous restarts of the system as they think the service is not running. So we also fix it in trusty. the result will looks as below:
ubuntu@maas:~/work/deb$ sudo start mysql
mysql start/running, process 8523
ubuntu@maas:~/work/deb$ sudo status mysql
mysql start/running, process 8523
ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql stop
mysql stop/waiting
ubuntu@maas:~/work/deb$ sudo status mysql
mysql stop/waiting
ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql status
mysql stop/waiting
[Regression Potential]
* Some scripts call '/etc/init.d/<service> reload' will not work if upstart script lacks a reload function and the reload function of /etc/init.d/<service> also uses PID. because it's managed by upstart now (the PID file does not exist). We should enumerate all those bad scripts and make them do the correct thing. |
[ impact ]
Previously, init.d scripts that were replaced by upstart jobs had "upstart-job" symlink as a redirect in-place, which directed users at using upstart commands. Despite the good intentions, that never actually taught people about the correct interfaces. Now with the advent of co-installability of multiple init systems, users may have systemd, upstart, and sysv-init all installed on users system and have init.d scripts / upstart jobs / systemd units all available. To avoid any doubt, we should support executing /etc/init.d/ scripts which may call into upstart, or into systemd, or actually execute the script in question depending on whether there is native configuration for that particular job and which init system we are running under.
[ test case ]
Invoking init.d script should invoke upstart commands, for example:
$ /etc/init.d/ssh status
ssh start/running, process 4620
$ /etc/init.d/ssh stop
stop: Rejected send message, 1 matched rules; type="method_call", sender=":1.2469694" (uid=1000 pid=3908 comm="stop ssh ") interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init")
$ sudo /etc/init.d/ssh stop
ssh stop/waiting
$ sudo /etc/init.d/ssh start
ssh start/running, process 5373
$ sudo /etc/init.d/ssh restart
ssh stop/waiting
ssh start/running, process 5405
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).
Description: Ubuntu 14.04
Release: 14.04
mysql: mysql-server-5.5.43-0ubuntu0.14.04.1
The problem in some setup was that the upgrade von 12.04 to 14.04 requres the adjustment of the InnoDB log size. Therefore the start of MySQL via upstart failed directly while the one via init started successfully and then failed as below.
root@webserver01.kurt..ref:~# status mysql
mysql start/running, process 5866
root@webserver01.kurt..ref:~# /etc/init.d/mysql stop
* Stopping MySQL database server mysqld [ OK ]
root@webserver01.kurt..ref:~# status mysql
mysql start/running, process 6101
root@webserver01.kurt..ref:~# /etc/init.d/mysql status
* /usr/bin/mysqladmin Ver 8.42 Distrib 5.5.43, for debian-linux-gnu on x86_64
Copyright (c) 2000, 2015, 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.43-0ubuntu0.14.04.1-log
Protocol version 10
Connection Localhost via UNIX socket
UNIX socket /var/run/mysqld/mysqld.sock
Uptime: 7 sec
Threads: 1 Questions: 108 Slow queries: 0 Opens: 48 Flush tables: 1 Open tables: 41 Queries per second avg: 15.428
root@webserver01.kurt..ref:~# stop mysql
mysql stop/waiting
root@webserver01.kurt..ref:~# /etc/init.d/mysql status
* MySQL is stopped.
This is horrible. The "status" commands report the wrong status and the start/stop commands do not work. If our operators are not super careful, our orchestration and monitoring system will go wild, report the wrong status and/or perform continuous restarts of the system as they think the service is not running. So we also fix it in trusty. the result will looks as below:
ubuntu@maas:~/work/deb$ sudo start mysql
mysql start/running, process 8523
ubuntu@maas:~/work/deb$ sudo status mysql
mysql start/running, process 8523
ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql stop
mysql stop/waiting
ubuntu@maas:~/work/deb$ sudo status mysql
mysql stop/waiting
ubuntu@maas:~/work/deb$ sudo /etc/init.d/mysql status
mysql stop/waiting
[Regression Potential]
Some scripts call '/etc/init.d/<service> reload' will not work if upstart script's 'reload signal' setting is incorrect and or /etc/init.d/<service> requires special reload handling. We should enumerate all those bad scripts and make them do the correct thing.
At the same time, '/etc/init.d/<service> reload' is not a guaranteed interface under Debian policy, and /etc/init.d/<service> force-reload will work correctly for all packages; and if using the 'service' command, this is already the existing behavior in trusty. |
|
| 2015-10-20 19:36:06 |
Steve Langasek |
lsb (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2015-10-20 19:36:11 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2015-10-20 19:36:13 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2015-10-20 19:36:21 |
Steve Langasek |
tags |
init scripts sts upstart |
init scripts sts upstart verification-needed |
|
| 2015-10-20 19:47:58 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/trusty-proposed/lsb |
|
| 2015-10-20 20:25:28 |
Simon Déziel |
bug |
|
|
added subscriber Simon Déziel |
| 2015-10-21 16:22:05 |
Mathew Hodson |
bug task deleted |
mysql-5.5 (Ubuntu) |
|
|
| 2015-10-21 16:22:20 |
Mathew Hodson |
bug task deleted |
mysql-5.5 (Ubuntu Trusty) |
|
|
| 2015-10-21 16:22:26 |
Mathew Hodson |
bug task deleted |
mysql-5.5 (Ubuntu Utopic) |
|
|
| 2015-10-27 15:24:57 |
Mathew Hodson |
lsb (Ubuntu): importance |
Undecided |
High |
|
| 2015-10-27 15:24:59 |
Mathew Hodson |
lsb (Ubuntu Utopic): importance |
Undecided |
High |
|
| 2015-12-03 17:57:25 |
Simon Déziel |
tags |
init scripts sts upstart verification-needed |
init scripts sts upstart verification-done-trusty verification-needed |
|
| 2015-12-04 08:58:46 |
Mathew Hodson |
tags |
init scripts sts upstart verification-done-trusty verification-needed |
init sts trusty upstart verification-done |
|
| 2016-01-20 07:16:23 |
Bug Watch Updater |
upstart (Debian): status |
New |
Fix Released |
|
| 2016-03-04 08:11:45 |
Laurent Declercq |
bug |
|
|
added subscriber Laurent Declercq |
| 2016-05-12 13:43:13 |
Launchpad Janitor |
lsb (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2016-05-12 13:43:20 |
Martin Pitt |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
