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 10.04 it was configured to 'require' local_fs and network to have started. That would make sense, but it didn't seem to be doing that in my case, as it was trying to start before the aliased IPs had started. Not sure why they wouldn't have been included in the 'network' command. Also not sure that adding 'remote_fs' would help, unless that somehow adds the dependancy for the aliased IPs, when networking doesn't. I'll check this out when I next have time to try out a new desktop OS. Thanks Scott, Simon On 21/12/11 20:49, Scott Kitterman wrote: > > 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 and have you seen it on a later version > since? > > > ** Changed in: haproxy (Ubuntu) > Status: New => Incomplete > -- 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: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/689734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
