I don't think this should be fixed in apache'2 init script. It depends
on '$network' and whatever is providing $network must ensure that the
network is actually usable. Also, it makes much more sense to fix this
in one place instead of hundreds of network daemons which are affected
by the same
Whatever is happening is happening independent of Upstart, as I was able
to duplicate the issue on Debian Wheezy.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1207384
Title:
** Package changed: apache2 (Debian) = ifupdown (Debian)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1207384
Title:
apache2 failure to start on boot when binding to IPv6 address
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It sounds like this issue would affect Debian too. Please could you
investigate and file a bug in Debian if appropriate?
Setting Priority to Medium as a workaround is available. I appreciate
you documenting this.
Done.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718507
Thanks!
** Bug watch added: Debian Bug tracker #718507
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718507
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2
** Also affects: apache2 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718507
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
** Changed in: apache2 (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1207384
Title:
apache2 failure to start on boot when binding to IPv6
