Hey Robie,
Unfortunately, this server was installed for a conference that has
already ended, and infrastructure for the site has already torn it down.
If it helps, I installed 14.04.2 just a couple days before 14.04.3 was
released. No ppas, stock from the repo. No modifications on the sources
Hello, Robie!
I downloaded and installed Ubuntu Server from the releases.ubuntu.com cd
repository. Once the server was installed (14.04.2), I installed and
configured a mirror with squid-deb-proxy. I set it up so it would work
with a DNS redirect. So, I had custom DNSs, and they pointed
Public bug reported:
On the mirror-dstdomain.acl list, it has the following entries:
.archive.ubuntu.com
ports.ubuntu.com
security.ubuntu.com
ddebs.ubuntu.com
mirrors.ubuntu.com
.archive.canonical.com
.extras.ubuntu.com
changelogs.ubuntu.com
However, the .archive.ubuntu.com entry, for example,
apport information
** Tags added: apport-collected raring
** Description changed:
LXC will not create the lxcbr0 bridge if bind9 is on, as it can not take
the 10.0.3.1 address. If bind9 is stopped, then LXC successfully creates
the bridge.
Expected result: LXC will create the bridge,
apport information
** Attachment added: KernLog.txt
https://bugs.launchpad.net/bugs/1240757/+attachment/3880369/+files/KernLog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
apport information
** Attachment added: SyslogBind9.txt
https://bugs.launchpad.net/bugs/1240757/+attachment/3880371/+files/SyslogBind9.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1240757/+attachment/3880370/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Attachment added: named.conf.local
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1240757/+attachment/3880400/+files/named.conf.local
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Attachment added: named.conf.options
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1240757/+attachment/3880401/+files/named.conf.options
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
Currently on Raring. I'm adding comments with the respective files
attached:
** Attachment added: named.conf
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1240757/+attachment/3880399/+files/named.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Attachment added: named.conf.default-zones
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1240757/+attachment/3880402/+files/named.conf.default-zones
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
Public bug reported:
LXC will not create the lxcbr0 bridge if bind9 is on, as it can not take
the 10.0.3.1 address. If bind9 is stopped, then LXC successfully creates
the bridge.
Expected result: LXC will create the bridge, even if bind9 is on.
** Affects: lxc (Ubuntu)
Importance:
12 matches
Mail list logo