I simply issued sudo reboot and this happened. So I assume then that
I have a different issue from the original reporter? Should I open a
separate bug and stop polluting this one?
In the meantime I'll pull the requested config files.
--
You received this bug notification because you are a
/etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet manual
auto juju-br0
iface juju-br0 inet dhcp
bridge_ports eth0
/etc/network/interfaces.d is empty
--
You received this bug notification
I simply issued sudo reboot and this happened. So I assume then that
I have a different issue from the original reporter? Should I open a
separate bug and stop polluting this one?
In the meantime I'll pull the requested config files.
--
You received this bug notification because you are a
/etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet manual
auto juju-br0
iface juju-br0 inet dhcp
bridge_ports eth0
/etc/network/interfaces.d is empty
--
You received this bug notification
Same as comment #44 I'm running hardware MAAS and I get this on every
deployment. If I let cloud-init error out I can get logged in and juju-
br0 is up by that point but it doesn't come up until after cloud-init
tries to do it's stuff. This makes the nodes I deploy unusable.
I'm going to see if
@dimitern Thanks for the swift reply. I'll do this now, for your
information I'm currently running juju 1.21-beta3-trusty-amd64 from the
juju-proposed ppa.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Also I've found that if I edit /etc/init/networking.conf and change the
starts on line to:-
starts on stopped cloud-init-local
Then everything works fine although I realise that this is a very poor
solution. Best I could manage with my limited upstart knowledge.
--
You received this bug
@dimitern
Quite right, it is the devel branch I'm using. I was trying to find a
new version which might already have a fix. I'm not very up on building
software based on go. I'm getting the following when I try to run go
install -v launchpad.net/juju-core/...
go build
Here is the bootstrap log created when I run juju bootstrap --to
db2.ed1.mavennetwork.co.uk --debug ~/maas-bootstrap.log
** Attachment added: maas-bootstrap.log
https://bugs.launchpad.net/juju-core/+bug/1271144/+attachment/4282230/+files/maas-bootstrap.log
--
You received this bug
And these are the juju and cloud logs from the node which was
bootstrapped. This node is working fine right now but once it is
rebooted I will get the cloud-init problem. I'll reboot it now and then
post the logs after the problematic boot.
** Attachment added: logs.zip
And lastly the logs from the node after it is rebooted. On this boot it
takes a very long time to come up as cloud-init waits for the network
bridge to come up and then eventually errors out.
** Attachment added: logs2.zip
Same as comment #44 I'm running hardware MAAS and I get this on every
deployment. If I let cloud-init error out I can get logged in and juju-
br0 is up by that point but it doesn't come up until after cloud-init
tries to do it's stuff. This makes the nodes I deploy unusable.
I'm going to see if
@dimitern Thanks for the swift reply. I'll do this now, for your
information I'm currently running juju 1.21-beta3-trusty-amd64 from the
juju-proposed ppa.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also I've found that if I edit /etc/init/networking.conf and change the
starts on line to:-
starts on stopped cloud-init-local
Then everything works fine although I realise that this is a very poor
solution. Best I could manage with my limited upstart knowledge.
--
You received this bug
@dimitern
Quite right, it is the devel branch I'm using. I was trying to find a
new version which might already have a fix. I'm not very up on building
software based on go. I'm getting the following when I try to run go
install -v launchpad.net/juju-core/...
go build
Here is the bootstrap log created when I run juju bootstrap --to
db2.ed1.mavennetwork.co.uk --debug ~/maas-bootstrap.log
** Attachment added: maas-bootstrap.log
https://bugs.launchpad.net/juju-core/+bug/1271144/+attachment/4282230/+files/maas-bootstrap.log
--
You received this bug
And these are the juju and cloud logs from the node which was
bootstrapped. This node is working fine right now but once it is
rebooted I will get the cloud-init problem. I'll reboot it now and then
post the logs after the problematic boot.
** Attachment added: logs.zip
And lastly the logs from the node after it is rebooted. On this boot it
takes a very long time to come up as cloud-init waits for the network
bridge to come up and then eventually errors out.
** Attachment added: logs2.zip
Sorry I seem to have done something wrong. This is obviously not a
Launchpad bug. I was trying to submit a bug for the version of Nautilus
in Ubuntu 13.10 which I believe is just called File now.
Does anyone know how I can correct this bug report?
** Summary changed:
- nautilus takes long
I also have had a problem with this. In my case I had changed the user
that apache runs as to make it compatible with freePBX which requires
apache to run as the asterisk user.
I have created an edited version of the init script which you will find
attached. This appears to work with whatever
I also have had a problem with this. In my case I had changed the user
that apache runs as to make it compatible with freePBX which requires
apache to run as the asterisk user.
I have created an edited version of the init script which you will find
attached. This appears to work with whatever
This is an old version. 0.16.999.49898-1 is in Debian unstable and matches the
versions of the rest of the EFL in Ubuntu.
However, all the EFL have now gone alpha removing the svn-version thing.
http://www.enlightenment.org/p.php?p=news
--
E17 is not installible due to unmet depends
This is only a bug for me in Gnome, in enlightenment e17 the bug does
not appear. Anyway, if it's fixed, it's fixed.
--
mouse button clicks not detected in windowed mode
https://bugs.launchpad.net/bugs/528957
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Macbook 2.1 no internal microphone
info at http://www.alsa-
project.org/db/?f=d6bdaf87d19a357860d7952dd0d4175c71e8c4de
--
Choppy and jerky recorded sound with snd-hda-intel
https://bugs.launchpad.net/bugs/69306
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Binary package hint: moodle
In the installer there are currently only options for configuring
various apache webservers. An option for lighttp would be beneficial
with the correct script 50-moodle.conf being added to /etc/lighttpd
/conf-available and enabled on install
** Attachment added: Sample moodle conf file for lighttpd
http://launchpadlibrarian.net/15873197/50-moodle.conf
** Description changed:
Binary package hint: moodle
In the installer there are currently only options for configuring
various apache webservers. An option for lighttp
26 matches
Mail list logo
