[Expired for haproxy (Ubuntu) because there has been no activity for 60
days.]
** Changed in: haproxy (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/689734
I've not tried this on a newer version of ubuntu, as I only tend to use
LTS versions. I haven't got my head around the new post sys V startup
thing, but the issue was that it needs to start after networking, but
was trying to start before it.
I would assume from what you're saying, that in
Ubuntu 11.10 was released with haproxy 1.4.15.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/689734
Title:
HAProxy fails to start at boot time
To manage notifications about this bug go to:
From 10.10 (Maverick) on, the haproxy init has:
# Required-Start:$local_fs $network $remote_fs
This looks right to me. In 10.04 (Lucid) it has only:
# Required-Start:$local_fs $network
I suspect this is what your bug was and it's fixed. Did you see this
problem on 10.04 originally
haproxy was updated in Debian, but not Ubuntu. I've requested to have
the package sync'ed so we'll have the newest for 11.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/689734
Title:
HAProxy
There was a fairly significant bugfix in HAProxy v 1.4.15, April 2011
that prevents DOS attacks and HAProxy crashes. I've built a .deb for it
with the same config options as the existing version (TCP Splicing, Full
Transparent Proxy, PCRE). Networking is listed as a startup dependency,
so it
Is this specific bug still happening with the Ubuntu 11.04 beta?
(However, not that /restarting/ of haproxy may be broken for other
reasons at bug #731878 shutdown(2) behavior changed in kernel).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Just a quick follow up, that didn't fix it. It went away for a bit,
then magically came back. The solution seemed to be to add networking
to init.d startup directories before haproxy:-
update-rc.d networking start 35 2 3 4 5 .
Like I said, the solution is probably to create a proper upstart
