** Changed in: apt (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/813400
Title:
lxc-create -t ubuntu complains about /dev/pts
To manage
The error seems to have been transient. I killed the hanging eucalyptus
postinst process and I got no further hang.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/851611
Title:
I just updated and still have a hanging wget:
...
Setting up kdepim-runtime (4:4.7.1-0ubuntu3) ...
Setting up libcouchdb-glib-1.0-2 (0.7.4-0ubuntu2) ...
Setting up libdesktopcouch-glib-1.0-2 (0.7.4-0ubuntu2) ...
Setting up oneconf (0.2.6.4) ...
Setting up software-center (4.1.23.4) ...
Updating
Unfortunately killing the wget in a loop is now not continuing the
eucalyptus start job. Also calling 'sudo stop eucalyptus' failed to
change anything, the eucalyptus start job is hanging.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Public bug reported:
Today's upgrade to eucalyptus blocks on my system:
Setting up unity-lens-applications (0.4.6-0ubuntu1) ...
Setting up unity-lens-files (0.6.6-0ubuntu1) ...
Setting up compiz-fusion-plugins-main (1:0.9.5.94+bzr20110915-0ubuntu1) ...
Setting up eucalyptus-admin-tools
apport information
** Attachment added: EucalyptusCCLog.gz
https://bugs.launchpad.net/bugs/851611/+attachment/2411458/+files/EucalyptusCCLog.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
apport information
** Attachment added: EucalyptusCloudOutputLog.gz
https://bugs.launchpad.net/bugs/851611/+attachment/2411460/+files/EucalyptusCloudOutputLog.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
apport information
** Attachment added: EucalyptusCloudDebugLog.gz
https://bugs.launchpad.net/bugs/851611/+attachment/2411459/+files/EucalyptusCloudDebugLog.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
apport information
** Attachment added: EucalyptusAxis2cLog.gz
https://bugs.launchpad.net/bugs/851611/+attachment/2411457/+files/EucalyptusAxis2cLog.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
apport information
** Attachment added: eucalyptus.local.conf.txt
https://bugs.launchpad.net/bugs/851611/+attachment/2411464/+files/eucalyptus.local.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
apport information
** Attachment added: EucalyptusHTTPDErrorLog.gz
https://bugs.launchpad.net/bugs/851611/+attachment/2411461/+files/EucalyptusHTTPDErrorLog.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
apport information
** Attachment added: eucalyptus.conf.txt
https://bugs.launchpad.net/bugs/851611/+attachment/2411463/+files/eucalyptus.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
apport information
** Attachment added: EucalyptusInstalledVersions.txt
https://bugs.launchpad.net/bugs/851611/+attachment/2411462/+files/EucalyptusInstalledVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus
I confirm James finding, I have the wget running as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/851611
Title:
Oneiric: Upgrade to 2.0.1+bzr1256 blocks
To manage
For the record, I killed the post instll script 'eucalyptus-
common.postinst', leaving eucalyptus unconfigured to proceed working on
the system.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
We tried the following to overcome the problem, nothing was successful:
1) Restart eucalyptus-cc
2) Reboot front-end and node-controlle
3) Purge and reinstall eucalyptus-cc
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
Did you enable the accessibility of the instance ports via
euca-authorize? What is the output of euca-describe-groups for the
clouds admin user?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
The only work around for the problem seems to be to terminate instances
and then try again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
https://bugs.launchpad.net/bugs/728018
Title:
10.04 LTS: Failure to
I wonder if the timeout for the termination request leads to a situation
when the pool of network addresses gets empty. Is there a way to see the
internal IP address allocation?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
The problem seems to occur quite randomly, here the statistics from the
last 5 test runs:
Started: 25 Clients, 4 Servers.
Stopped: 21
Started: 340 Clients, 27 Servers.
Stopped: 360
Started: 70 Clients, 8 Servers.
Stopped: 71
Started: 70 Clients, 5 Servers.
Stopped: 68
Started: 30 Clients, 6
From time to time I see these timeouts, could they be related?
4 0 8
path=/services/Eucalyptus/?AWSAccessKeyId=WKy3rMzOWPouVOxK1p3Ar1C2uRBwa2FBXnCwA
ction=TerminateInstancesInstanceId.1=i-47F10968InstanceId.2=i-4D930877Instanc
And another one:
[Thu Mar 3 11:48:55 2011][011912][EUCADEBUG ] RunInstances(): running instance
i-3393055A with emiId emi-0CE515A7...
[Thu Mar 3 11:48:55 2011][011912][EUCAERROR ] vnetAddHost(): failed to add
host d0:0d:33:93:05:5A on vlan 10
[Thu Mar 3 11:48:55 2011][011912][EUCADEBUG ]
Public bug reported:
I'm running tests and launch rather large numbers of instances on a UEC
running with Ubuntu 10.04 LTS. I discovered that instances regularly
fail to start and it seems to be that they never get a network address
assigned. In the cc.log I discovered the following entries:
Another fail during tonight's test run:
[Thu Mar 3 01:36:43 2011][011910][EUCADEBUG ] RunInstances(): running instance
i-49AF07C3 with emiId emi-0CE515A7...
[Thu Mar 3 01:36:43 2011][011910][EUCAERROR ] vnetAddHost(): failed to add
host d0:0d:49:AF:07:C3 on vlan 10
[Thu Mar 3 01:36:43
For completeness the network definition of the cloud. If wanted I can
grant ssh access to the system:
VNET_MODE=MANAGED-NOVLAN
VNET_SUBNET=172.19.0.0
VNET_NETMASK=255.255.0.0
VNET_DNS=172.24.1.1
VNET_ADDRSPERNET=32
VNET_PUBLICIPS=172.24.129.136
Again, when starting new instances it works and
The problem exists on the Ubuntu 10.10 training cloud as well. Maybe a
packaging error?
** Changed in: eucalyptus (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
Public bug reported:
Binary package hint: kvm
I've updated my kernel on an Ubuntu 10.04 host with linux-image-generic-
pae-lts-backport-maverick. Since then two virtual machines using Lucid
do no longer start. The boot hangs with an empty screen and a _
displayed on the top left. When I reboot
Public bug reported:
The default security group of a user can not be deleted with admin
privileges. E.g.
$ euca-describe-groups | grep davidchen
GROUP davidchen default default group
PERMISSION davidchen default ALLOWS tcp 22 22 FROM
CIDR 0.0.0.0/0
There
** Summary changed:
- instances gets public ip address after disassociate-address
+ [10.04] instances gets public ip address after disassociate-address
--
[10.04] instances gets public ip address after disassociate-address
https://bugs.launchpad.net/bugs/660055
You received this bug
Public bug reported:
When I start an instance with --addressing-private option, associate an
elastic IP to it and take this away later, the instance claims another
public ip instead of staying private.
$ euca-describe-instances
RESERVATION r-3B69071E spindlerdefault
INSTANCE
It's Eucalyptus 1.6.2 on Ubuntu 10.04.1.
--
instances gets public ip address after disassociate-address
https://bugs.launchpad.net/bugs/660055
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs
I can reproduce the problem on the training cloud:
$ for i in `seq 1 100`; do euca-create-volume -z TorstenCloud -s1; done
...
VOLUME vol-52B905E31 creating2010-09-02T06:27:50.814Z
VOLUME vol-5F2906521 creating2010-09-02T06:27:51.142Z
VOLUME vol-598F062A
Here we go, the problem is fixed:
$ for i in $(seq 1 32); do euca-create-volume -s 1 -z TorstenCloud; done
$ euca-describe-volumes | grep avail | wc -l
30
$ euca-describe-volumes | grep creat | wc -l
0
$ euca-describe-volumes | grep fail | wc -l
2
$ for i in $(euca-describe-volumes | cut -c8-20
@Carlos,
the cloud of the error reports is long gone. If need be I can try to
recreate the problem on a new one next week.
--
euca-create-volume fails at times with Error communicating with Storage
Controller
https://bugs.launchpad.net/bugs/517086
You received this bug notification because you
Is the cluster registered in the cloud at all? Do you see it with
euca-describe-availability-zones?
--
eucalyptus-cc and uec-component-listener services are not started
https://bugs.launchpad.net/bugs/598182
You received this bug notification because you are a member of Ubuntu
Server Team, which
I created a new cloud and this time via packaged install and this time
the keys were present after registering the cluster controller. Please
close this bug as it cannot be reproduced.
--
Not all keys present
https://bugs.launchpad.net/bugs/592648
You received this bug notification because you
Nope, I didn't do that before hand. I copied it after it failed. But it
seems it's then to late already. I still don't quite understand how the
keys can be missing - I thought they are setup when registering a
cluster. I also believe this is where it went wrong.
--
Not all keys present
Public bug reported:
I've created a new cloud using the install from packages method. The
first unusual thing was that the CC was not automatically registered,
even when running on the same host as the CLC. Now the next problem
manifests in the node not being registered due to missing keys:
$
The first existing cloud was using the simple topology: one front-end,
one node controller. The cloud we installed first was made up of 3
machines: 1 CLC+Walrus, 1 CC+SC, 2 NC.
After installing the second cloud, both clouds had two clusters
registered against it. However, the output of
On Fri, 2010-05-07 at 14:35 +, Jason Rogers wrote:
...
I had a guest vm running on a eucalyptus cloud using virtio for disk and
network I/O. I also had an ssh session on the guest vm. When I attach a
volume to the instance using euca-attach-volume I lose network
connectivity to the guest.
Public bug reported:
The 172.19.1.2 IP address was assigned twice in this cloud:
$ euca-describe-instances
RESERVATION r-4AAA0905 admin default
INSTANCEi-42F507EC emi-6E2F1366172.19.1.2 172.19.1.2
running admin 0 m1.small
This seems to have happened while dnsmasq was running on an instance -
the instance got the ip from itself. After disabling dhcp for dnsmasq on
another trial instance, the problem could no longer be reproduced.
--
private ip address assigned twice
https://bugs.launchpad.net/bugs/574366
You
Public bug reported:
One cloud is already running. When installing a new cloud in the same
subnet, auto registration of nodes to the second cloud does not seem to
work.
From the CLC registration.log:
2010-04-30 10:41:13-04:00 | 3882 - Calling node rockstars-cluster node
10.153.108.113
After stopping the other cloud and reinstalling it worked.
--
NC not available when auto registrating with second cloud present
https://bugs.launchpad.net/bugs/572388
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
Does it work without the -P 1 option?
--
qemu-kvm-0.12.3+noroms-0ubuntu2: qemu-nbd: error while reading
https://bugs.launchpad.net/bugs/546997
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs
On Lucid, I don't get the Volume: Error communicating with Storage
Controller: CreateStorageVolume:Internal Error. error anymore. However,
not all volume groups are deleted:
$ sudo lvscan
ACTIVE'/dev/vg-wsdyiQ../lv-K0hXfA..' [1.00 GiB] inherit
$ sudo vgscan
Reading all physical
On Wed, 2010-03-17 at 13:32 +, Jean-Pierre Dion wrote:
...
2)
euca-upload-bundle -b kernel_bucket -m
/tmp/vmlinuz-2.6.31-14-server.manifest.xml
...
3)
euca-register kernel_buckets/vmlinuz-2.6.31-14-server.manifest.xml
Just to make sure that there is no typing mistake: the euca-register
The bios files are missing from the package, instead there is still a
link pointing nowhere:
lrwxrwxrwx 1 root root 22 2010-03-05 08:26 vgabios.bin
- ../vgabios/vgabios.bin
lrwxrwxrwx 1 root root 29 2010-03-05 08:26 vgabios-cirrus.bin
- ../vgabios/vgabios.cirrus.bin
When the two links
I just tried 0.12.3-0ubuntu5~ppa2 and I don't get any errors when launching
$ kvm -vga std -hda ./lucid.qcow2
--
kvm with -vga std is broken since karmic
https://bugs.launchpad.net/bugs/513273
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
The bug also exists in Lucid, libvirt 0.7.5-5ubuntu9.
--
driver cache='none'/ disappears after adding
https://bugs.launchpad.net/bugs/531741
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs
I tried to reproduce your kernel oops problem with the lucid alpha 3
server CD, but no kernel oops was given. Can you reproduce the error on
a different hardware?
--
daily server ISO install fails with a kernel OOPS in KVM
https://bugs.launchpad.net/bugs/531455
You received this bug notification
*** This bug is a duplicate of bug 531823 ***
https://bugs.launchpad.net/bugs/531823
It's a 32bit system, maybe that's the key difference?
a) uname -a
spind...@spitfire:~/t$ uname -a
Linux spitfire 2.6.32-15-generic #22-Ubuntu SMP Tue Mar 2 02:24:17 UTC
2010 i686 GNU/Linux
b) cat
After reinstallation nothing changes. I removed quiet and splash from the
kernel boot command line and see the following report:
init: eucalyptus-network (lo) main process (704) killed by TERM signal
--
[alpha3] NC fails to be detected.
https://bugs.launchpad.net/bugs/530091
You received this
On Wed, 2010-03-03 at 09:48 +, Thierry Carrez wrote:
Looking at the authorized_keys, might be a node re-registration issue.
Did you register the same Node IP with the CC in the past ?
Yes, it was registered before.
When you
deregistered/registered manually the node, did you get any
On a fresh install of front-end and node controller the cloud works as
expected:
ubu...@frontend:/var/log/eucalyptus$ euca-describe-availability-zones verbose
AVAILABILITYZONEtorsten 192.168.1.103
AVAILABILITYZONE|- vm types free / max cpu ram disk
AVAILABILITYZONE
Having the option to host a complete UEC on one machine is also relevant
for training. Right now we fall back to one UEC per classroom due to the
two machine requirement, or at most students working in pairs.
--
After all-in-one setup node-cert.pem and node-pk.pem not found
I'm pretty sure I waited for the front-end to be ready, e.g. euca-
describe-availability-zones verbose returns a good output. I attach the
registration log from the front-end.
On the node the authorized_keys file contain a good key for the
frontend. As user eucalyptus on the front-end I can do a
I tried the deregister and register but not change in the overall
situation.
For the logs on the node controller, I don't see nc.log:
ubu...@node01:/var/log/eucalyptus$ ls
axis2c.log euca_test_nc.log httpd-nc_error_log
--
[alpha3] NC fails to be detected.
Nothing of interest in there, I attach the two
** Attachment added: httpd-nc_error_log
http://launchpadlibrarian.net/39962164/httpd-nc_error_log
** Attachment added: euca_test_nc.log
http://launchpadlibrarian.net/39962165/euca_test_nc.log
--
[alpha3] NC fails to be detected.
Public bug reported:
I installed a frontend and node with the alpha3 server CD. Frontend works fine,
but
$ euca-describe-availability-zones verbose
does not have any node. I tried
$ euca_conf --discover-nodes --no-rsync
but the node was not discovered. I added it then by hand to
The following command did not give an error for me on Lucid Alpha 3, 2010-03-01
updates installed:
$ qemu-img snapshot -c toast ./lucid.qcow2
Version: 0.12.3-0ubuntu2
Unfortunately I did not find a snapshot thereafter either.
--
'qemu-img snapshot' crashed, corrupting disk image
Cannot reproduce this problem with a Lucid alpha3 guest running on a Lucid
alpha 3 host.
qemu-kvm Version: 0.12.3-0ubuntu2
--
qemu corrupts screen on resize
https://bugs.launchpad.net/bugs/426822
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This seems to be fixed on Lucid alpha 3:
$ qemu -cpu pentium lucid.qcow2
kvm_run: Exec format error
kvm_run returned -8
$ qemu -cpu 486 lucid.qcow2
kvm_run: Exec format error
kvm_run returned -8
$ qemu -cpu pentium -no-kvm lucid.qcow2
(runs, slowly)
--
qemu segfaults with a -cpu option
On Lucid Alpha3 I don't get console error messages, but a
error: unknown command 'terminal'.
unaligned pointer 0x8ecc0002
Aborted. Press any key to exit.
--
kvm with -vga std give error and do not works
https://bugs.launchpad.net/bugs/513273
You received this bug notification because you are a
I upgraded from Karmic to Lucid alpha 3 and cannot reproduce your
problem. virsh start works fine for my old VMs.
--
lucid qemu: could not open disk image
https://bugs.launchpad.net/bugs/512259
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
On Lucid alpha 3 an error is reported and kvm stops:
$ sudo kvm -net nic -net user,hostfwd=tcp:127.0.0.1:-:80 -net
user,hostfwd=tcp:127.0.0.1:-:22 -m 128 -smp 1 -drive file=disk0.qcow2kvm
-net nic -net user,hostfwd=tcp:127.0.0.1:-:80 -net
user,hostfwd=tcp:127.0.0.1:-:22 -m 128
According to the original bug reporter this problem has been resolved in
Lucid.
--
assertion failure when using i82551 network card emulation
https://bugs.launchpad.net/bugs/450309
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm
I enabled karmic-proposed, installed eucalyptus-*-1.6~bzr931-0ubuntu7.5
on the training cloud in the datacenter. I rebooted node and frontend
and the cloud was operational from the start. I started an instance and
ssh'ed to it. All looks good and operational.
--
[SRU] eucalyptus-cloud doesn't
Public bug reported:
I made a mistake when trying to attach a volume to an instance and gave
it device /dev/sda. Instead of failing gracefully the node stopped to
operate. Here's the log:
[Tue Feb 23 15:14:48 2010][001762][EUCAINFO ] started VM instance i-3B530725
[Tue Feb 23 15:18:13
Restarting libvirtd seemed to resolve the issue, albeit state is
inconsistent thereafter.
--
[karmic]: attaching volume to /dev/sda results in non operational node
https://bugs.launchpad.net/bugs/526506
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I first reproduced the problem on the training cloud, then installed the
PPA packages. The problem went away, the cloud is responsive within the
first two minutes of restarting the frontend.
--
eucalyptus-cloud doesn't reply to requests (eucalyptus doesn't work after
reboot or services restart
On Tue, 2010-02-09 at 21:39 +, Boris Devouge wrote:
- ran on 3 nodes: 'sudo apt-get clean all sudo apt-get update
sudo
apt-get upgrade'
Any reason for using this method rather than the recommended
do-release-upgrade -d
procedure?
--
UEC upgrade from 9.10 karmic to Lucid fails
Quite possible, the students are instructed to create a key called
'mykey' in the exercise. With this the problem can be reproduced:
$ euca-add-keypair mykey2 mykey2.priv
$ euca-add-keypair mykey2 mykey2.priv
$ euca-run-instances -t c1.medium -k mykey2 emi-DF481077
$ ssh -i mykey2.priv
Public bug reported:
Happened on the Ubuntu training cloud with Ubuntu 9.10.
For testing purposes for training I create 32 volumes with the following script:
for i in $( seq 1 32); do sleep 5; euca-create-volume -s 1 -z classcloud; done
After creating these I remove them with:
for vol in
From the extra tab select 'Register this cloud with Landscape'
** Attachment added: UEC-landscape-start.png
http://launchpadlibrarian.net/38613962/UEC-landscape-start.png
--
Wrong URL port suggested for Landscape registration
https://bugs.launchpad.net/bugs/491437
You received this bug
From there the Landscape registration form is filled in incorrectly with
the port 8443.
** Attachment added: UEC-landscape-wrongURL.png
http://launchpadlibrarian.net/38613978/UEC-landscape-wrongURL.png
--
Wrong URL port suggested for Landscape registration
The sshd is started, the last few lines from euca-get-console-output:
ec2:
ec2: #
ec2: -BEGIN SSH HOST KEY FINGERPRINTS-
ec2: 2048 c5:e6:f6:21:16:bf:b4:d8:00:fa:1b:ad:29:12:86:de
/etc/ssh/ssh_host_rsa_key.pub (RSA)
ec2: 1024
Public bug reported:
On UEC on Ubuntu 9.10 the following problem occured during last week's
training session:
A student created a key and it worked fine. After some time it stopped
working, e.g. the key can no longer be used to log into an instance. The
key is named mykey and specific for a
Public bug reported:
During the UEC class this week using Ubuntu 9.10 the following problem
surfaced:
The cloud was fully operational. The networking mode was changed from
MANAGED_NOVLAN to SYSTEM. After rebooting the front-end and node no
instance could be started anymore. The instance was left
*** This bug is a duplicate of bug 464384 ***
https://bugs.launchpad.net/bugs/464384
The complete cloud (frontend and node) was rebooted.
--
Changing networking mode left cloud non working
https://bugs.launchpad.net/bugs/514203
You received this bug notification because you are a member of
On Fri, 2010-01-29 at 19:26 +, Dustin Kirkland wrote:
...
Or, rather, did they create and use instances with that key, and then
later, create instances but not be able to use that key?
This I meant with stopped working.
--
SSH key stopped working
https://bugs.launchpad.net/bugs/514198
You
*** This bug is a duplicate of bug 464384 ***
https://bugs.launchpad.net/bugs/464384
You are right, it is a duplicate, the following worked:
$ sudo restart eucalyptus CLEAN=1
--
Changing networking mode left cloud non working
https://bugs.launchpad.net/bugs/514203
You received this bug
I cannot reproduce the problem anymore with the cloud I've got currently
running. I suggest to invalidate the bug.
--
Official UEC image fails to boot
https://bugs.launchpad.net/bugs/464418
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I've seen similar problems in the past, but waiting for some extended
time (15 minutes) solved it. In that time the Web UI was also not
working, the admin user was reported to not exist.
--
eucalyptus-cloud doesn't reply to requests
https://bugs.launchpad.net/bugs/503180
You received this bug
Public bug reported:
The default Ubuntu kernel provides only 8 loopback devices. Setting more
is possible with the max_loop=number on the kernel boot parameters
line in /boot/grub/grub.cfg. It would be great if this can be done
automagically for a host configured as Storage Controller.
I just learned that the number of loop back devices is managed
dynamically by the kernel. However, the number of actual loop back
devices in /dev/ is set to 8 by default. Creating new ones can be done
with
$ sudo mknod b 7 number /dev/loopnumber
--
Maximum number of 8 loopback devices low for
I cannot repeat the problem today.
After specifying the hostname to 'node01' the next screeen says 'Select
cloud installation mode' and informs that no eucalyptus cloud controller
was found on your network. Albeit the cloud controller is up and running
on another machine. I then specify the cloud
Public bug reported:
I just installed UEC with the Lucid installer. First I installed the
front end with clc, walrus, cc and sc. Then the node. The node told me
that it cannot find walrus and the installer suggested to me to install
it first.
I checked ps aux | grep avahi on the frontend and
Public bug reported:
A question that came up in every UEC class I've run so far was how to
make the cloud and cluster controller redundant, so the cloud is more
resilient to failures of those components. Are there any suggestions out
there how to achieve this?
** Affects: eucalyptus (Ubuntu)
Public bug reported:
When using the services tab in the UEC webUI and registering with
Landscape, the 8443 port is suggested instead of the correct 8773.
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
--
Wrong URL port suggested for Landscape registration
At the moment not, as I do not have access to that cloud environment any
longer. From UDS I take that we do not fully support the separation of
cloud and cluster controller in UEC. This needs to be done by changing
the eucalyptus.conf files.
--
eucalyptus-cloud not starting when separating cloud
This seems to be cloud specific to the one at my home. I have the image
running on a different cloud and it works fine there.
--
Official UEC image fails to boot
https://bugs.launchpad.net/bugs/464418
You received this bug notification because you are a member of Ubuntu
Server Team, which is
grep -i deadlock /var/log/eucalyptus/* /tmp/deadlock
** Attachment added: deadlock
http://launchpadlibrarian.net/35653868/deadlock
--
euca-register fails with syntax error
https://bugs.launchpad.net/bugs/480048
You received this bug notification because you are a member of Ubuntu
Server
On Tue, 2009-11-10 at 08:51 +, Eric Hammond wrote:
Torsten: What AMI id are you starting with?
This one was a Jaunty image created with vmbuilder.
part file looks like:
root 2000
swap 1
and first boot looks like:
while (! ping -c 1 archive.ubuntu.com); do sleep 1; done
apt-get -y install
Public bug reported:
After creating a homemade Karmic image with vmbuilder, it fails to
register with:
euca-register karmic-homemade/root.img.manifest.xml
Warning: failed to parse error message from AWS: unknown:1:49: syntax error
Traceback (most recent call last):
File /usr/bin/euca-register,
Here the relevant parts from history:
64 export http_proxy=http://10.153.104.60:3128
65 sudo vmbuilder xen ubuntu
66 sudo vmbuilder xen ubuntu --part ./part --firstboot ./firstboot
67 ls
68 euca-bundle-image -i ubuntu-xen/root.img
69 euca-upload-bundle -m
Here the image manifest.
** Attachment added: root.img.manifest.xml
http://launchpadlibrarian.net/35480755/root.img.manifest.xml
--
euca-register fails with syntax error
https://bugs.launchpad.net/bugs/480048
You received this bug notification because you are a member of Ubuntu
Server Team,
This might be unrelated to euca-register, I get the same error with
euca-describe-availability-zones:
$ euca-describe-availability-zones
Warning: failed to parse error message from AWS: unknown:1:49: syntax error
Traceback (most recent call last):
File
After a reboot, 'euca-describe-availability-zones verbose' worked fine.
'euca-register' still fails, with a different error:
$ euca-register karmic-homemade/root.img.manifest.xmlWarning: failed to parse
error message from AWS: unknown:1:0: syntax error
EC2ResponseError: 403 Forbidden
Failure:
After a wait the last error went away and euca-register worked.
--
euca-register fails with syntax error
https://bugs.launchpad.net/bugs/480048
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs
1 - 100 of 117 matches
Mail list logo
