| 2015-11-06 18:23:54 |
Andreas Hasenack |
bug |
|
|
added bug |
| 2015-11-06 18:25:14 |
Andreas Hasenack |
description |
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
start-stop-daemon doesn't complain about --pid not being a valid option...
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
start-stop-daemon doesn't complain about --pid not being a valid option...
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
|
| 2015-11-06 18:25:41 |
Andreas Hasenack |
description |
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
start-stop-daemon doesn't complain about --pid not being a valid option...
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
--pid is not a valid option for trusty's start-stop-daemon.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
|
| 2015-11-06 18:26:15 |
Andreas Hasenack |
description |
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
--pid is not a valid option for trusty's start-stop-daemon.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
--pid is not a valid option for trusty's start-stop-daemon.
In trusty proper, that stop action does:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
|
| 2015-11-06 18:32:18 |
Jon Grimm |
bug |
|
|
added subscriber Jon Grimm |
| 2015-11-06 18:34:14 |
Andreas Hasenack |
description |
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
--pid is not a valid option for trusty's start-stop-daemon.
In trusty proper, that stop action does:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action in /etc/init.d/haproxy does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
--pid is not a valid option for trusty's start-stop-daemon.
In trusty proper, that stop action does:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
Example:
No haproxy running yet:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
let's start one:
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
Ok, it's there:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
Let's restart:
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
And now I have two!
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
Let's try to kill one just like the initscript does it, with the incorrect --pid option:
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
Still alive:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
|
| 2015-11-06 18:34:51 |
Andreas Hasenack |
description |
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action in /etc/init.d/haproxy does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
--pid is not a valid option for trusty's start-stop-daemon.
In trusty proper, that stop action does:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
Example:
No haproxy running yet:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
let's start one:
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
Ok, it's there:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
Let's restart:
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
And now I have two!
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
Let's try to kill one just like the initscript does it, with the incorrect --pid option:
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
Still alive:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action in /etc/init.d/haproxy does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
--pid is not a valid option for trusty's start-stop-daemon.
In trusty proper, that stop action does:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
Example:
No haproxy running yet:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
let's start one:
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
Ok, it's there:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
Let's restart:
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
And now I have two!
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
Let's try to kill one just like the initscript does it, with the --pid option that does not exist in trusty:
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
Still alive:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
|
| 2015-11-06 19:02:22 |
Jorge Niedbalski |
tags |
|
sts |
|
| 2015-11-06 19:05:07 |
Jorge Niedbalski |
description |
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action in /etc/init.d/haproxy does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
--pid is not a valid option for trusty's start-stop-daemon.
In trusty proper, that stop action does:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
Example:
No haproxy running yet:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
let's start one:
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
Ok, it's there:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
Let's restart:
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
And now I have two!
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
Let's try to kill one just like the initscript does it, with the --pid option that does not exist in trusty:
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
Still alive:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
Observation:
On Trusty the start-stop-daemon (man start-stop-daemon) just supports the --pidfile parameter, since utopic, that parameter was split on --pidfile --ppid and --pid parameters.
On dev release the stop function actually makes use of the --pid , which
is unexistant on the trusty version of start-stop-daemon, for this reason
any backport made from dev to trusty will consequently not work.
Note that this bug also affects Kilo backports.
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action in /etc/init.d/haproxy does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
--pid is not a valid option for trusty's start-stop-daemon.
In trusty proper, that stop action does:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
Example:
No haproxy running yet:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
let's start one:
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
Ok, it's there:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
Let's restart:
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
And now I have two!
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
Let's try to kill one just like the initscript does it, with the --pid option that does not exist in trusty:
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
Still alive:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
|
| 2015-11-06 19:07:36 |
Jorge Niedbalski |
description |
Observation:
On Trusty the start-stop-daemon (man start-stop-daemon) just supports the --pidfile parameter, since utopic, that parameter was split on --pidfile --ppid and --pid parameters.
On dev release the stop function actually makes use of the --pid , which
is unexistant on the trusty version of start-stop-daemon, for this reason
any backport made from dev to trusty will consequently not work.
Note that this bug also affects Kilo backports.
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action in /etc/init.d/haproxy does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
--pid is not a valid option for trusty's start-stop-daemon.
In trusty proper, that stop action does:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
Example:
No haproxy running yet:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
let's start one:
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
Ok, it's there:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
Let's restart:
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
And now I have two!
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
Let's try to kill one just like the initscript does it, with the --pid option that does not exist in trusty:
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
Still alive:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
Observation:
On Trusty the start-stop-daemon (man start-stop-daemon) just supports the --pidfile parameter, since utopic, that parameter was split on --pidfile --ppid and --pid parameters.
On dev release the stop function actually makes use of the --pid , which
is unexistant on the trusty version of start-stop-daemon, for this reason
any backport made from dev to trusty will consequently not work.
Note that this bug also affects Kilo backports.
Please also note that this is actually fixed on trusty-updates via
the bug http://pad.lv/1477198.
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action in /etc/init.d/haproxy does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
--pid is not a valid option for trusty's start-stop-daemon.
In trusty proper, that stop action does:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
Example:
No haproxy running yet:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
let's start one:
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
Ok, it's there:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
Let's restart:
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
And now I have two!
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
Let's try to kill one just like the initscript does it, with the --pid option that does not exist in trusty:
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
Still alive:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
|
| 2015-11-06 19:07:42 |
Scott Moser |
description |
Observation:
On Trusty the start-stop-daemon (man start-stop-daemon) just supports the --pidfile parameter, since utopic, that parameter was split on --pidfile --ppid and --pid parameters.
On dev release the stop function actually makes use of the --pid , which
is unexistant on the trusty version of start-stop-daemon, for this reason
any backport made from dev to trusty will consequently not work.
Note that this bug also affects Kilo backports.
Please also note that this is actually fixed on trusty-updates via
the bug http://pad.lv/1477198.
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action in /etc/init.d/haproxy does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
--pid is not a valid option for trusty's start-stop-daemon.
In trusty proper, that stop action does:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
Example:
No haproxy running yet:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
let's start one:
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
Ok, it's there:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
Let's restart:
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
And now I have two!
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
Let's try to kill one just like the initscript does it, with the --pid option that does not exist in trusty:
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
Still alive:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
Observation:
On Trusty the start-stop-daemon (man start-stop-daemon) just supports the --pidfile parameter, since utopic, that parameter was split on --pidfile --ppid and --pid parameters.
On dev release the stop function actually makes use of the --pid , which
is unexistant on the trusty version of start-stop-daemon, for this reason
any backport made from dev to trusty will consequently not work.
Note that this bug also affects Kilo backports.
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action in /etc/init.d/haproxy does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
--pid is not a valid option for trusty's start-stop-daemon.
In trusty proper, that stop action does:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
Example:
No haproxy running yet:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
let's start one:
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
Ok, it's there:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
Let's restart:
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
And now I have two!
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
Let's try to kill one just like the initscript does it, with the --pid option that does not exist in trusty:
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
Still alive:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
Related bugs:
* bug 1477198: [haproxy] Stop doesn't works on Trusty |
|
| 2015-11-06 19:08:11 |
Jorge Niedbalski |
description |
Observation:
On Trusty the start-stop-daemon (man start-stop-daemon) just supports the --pidfile parameter, since utopic, that parameter was split on --pidfile --ppid and --pid parameters.
On dev release the stop function actually makes use of the --pid , which
is unexistant on the trusty version of start-stop-daemon, for this reason
any backport made from dev to trusty will consequently not work.
Note that this bug also affects Kilo backports.
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action in /etc/init.d/haproxy does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
--pid is not a valid option for trusty's start-stop-daemon.
In trusty proper, that stop action does:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
Example:
No haproxy running yet:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
let's start one:
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
Ok, it's there:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
Let's restart:
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
And now I have two!
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
Let's try to kill one just like the initscript does it, with the --pid option that does not exist in trusty:
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
Still alive:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
Related bugs:
* bug 1477198: [haproxy] Stop doesn't works on Trusty |
Observation:
On Trusty the start-stop-daemon (man start-stop-daemon) just supports the --pidfile parameter, since utopic, that parameter was split on --pidfile --ppid and --pid parameters.
On dev release the stop function actually makes use of the --pid parameter , which is unexistant on the trusty version of start-stop-daemon, for this reason any backport made from dev to trusty will consequently not work.
Note that this bug also affects Kilo backports.
Please also note that this is actually fixed on trusty-updates via
the bug http://pad.lv/1477198.
With liberty:
*** 1.5.14-1~cloud2 0
500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
"service haproxy stop" does not work:
The stop action in /etc/init.d/haproxy does this:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pid $pid --exec $HAPROXY || ret=$?
--pid is not a valid option for trusty's start-stop-daemon.
In trusty proper, that stop action does:
start-stop-daemon --quiet --oknodo --stop \
--retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
Example:
No haproxy running yet:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy
104776 pts/2 S+ 0:00 | \_ grep --color=auto haproxy
let's start one:
root@juju-machine-1-lxc-2:~# service haproxy start
* Starting haproxy haproxy
...done.
Ok, it's there:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
Let's restart:
root@juju-machine-1-lxc-2:~# service haproxy restart
* Restarting haproxy haproxy
...done.
And now I have two!
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~#
Let's try to kill one just like the initscript does it, with the --pid option that does not exist in trusty:
root@juju-machine-1-lxc-2:~# start-stop-daemon --oknodo --stop --retry 5 --pid 104803 --exec /usr/sbin/haproxy
No /usr/sbin/haproxy found running; none killed.
Still alive:
root@juju-machine-1-lxc-2:~# ps fxaw|grep haproxy|grep -v grep
104786 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
104803 ? Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
root@juju-machine-1-lxc-2:~# |
|
| 2015-11-06 19:11:21 |
Scott Moser |
marked as duplicate |
|
1477198 |
|
| 2015-11-06 19:11:54 |
Louis Bouchard |
changed duplicate marker |
1477198 |
1481737 |
|
