Where 192.168.0.136 is my CC, and 192.168.0.121 is my NC.
I am also seeing my network traffic flooded for ~15 minutes as it downloads 10GB+, and I see
root@node:/var/lib/eucalyptus/instances# find /var/lib/eucalyptus/instances/ -type f
/var/lib/eucalyptus/instances/admin/i-3BEB06F3/kernel
/var/lib/eucalyptus/instances/admin/i-3BEB06F3/ramdisk
/var/lib/eucalyptus/instances/admin/i-3BEB06F3/disk-digest
/var/lib/eucalyptus/instances/admin/i-3BEB06F3/disk
/var/lib/eucalyptus/instances/eucalyptus/cache/eki-8F0A139D/kernel
/var/lib/eucalyptus/instances/eucalyptus/cache/eki-8F0A139D/kernel-digest
/var/lib/eucalyptus/instances/eucalyptus/cache/eri-E64F14E8/ramdisk
/var/lib/eucalyptus/instances/eucalyptus/cache/eri-E64F14E8/ramdisk-digest
/var/lib/eucalyptus/instances/eucalyptus/cache/emi-D5871527/disk-staging
However, I never see my instance move from "pending" to "running", so there is a bug here, but perhaps different from whatever you're seeing on your end.
RESERVATION r-31500705 admin default
INSTANCE i-3BEB06F3 emi-D5871527 192.168.0.250 172.19.1.2 pending mykey 0 m1.xlarge
2009-09-30T22:37:49.042Z canyonedge eki-8F0A139D eri-E64F14E8
Thierry,
I *definitely* am not reproducing the 127.0.0.1 error. In my nc.log, I'm seeing:
[Wed Sep 30 17:37:49 2009][008286] [EUCAINFO ] from http:// 192.168. 0.136:8773/ services/ Walrus/ ueckernel/ vmlinuz- 2.6.31- 11-generic. manifest. xml [EUCAINFO ] from http:// 192.168. 0.136:8773/ services/ Walrus/ uecramdisk/ initrd. img-2.6. 31-11-generic. manifest. xml [EUCAINFO ] from http:// 192.168. 0.136:8773/ services/ Walrus/ uecimage/ ubuntu- uec-jaunty- amd64.img. manifest. xml [EUCAINFO ] from http:// 192.168. 0.136:8773/ services/ Walrus/ uecimage/ ubuntu- uec-jaunty- amd64.img. manifest. xml
[Wed Sep 30 17:37:49 2009][008286]
[Wed Sep 30 17:37:49 2009][008286]
[Wed Sep 30 17:37:49 2009][008286]
Where 192.168.0.136 is my CC, and 192.168.0.121 is my NC.
I am also seeing my network traffic flooded for ~15 minutes as it downloads 10GB+, and I see /var/lib/ eucalyptus/ instances# find /var/lib/ eucalyptus/ instances/ -type f eucalyptus/ instances/ admin/i- 3BEB06F3/ kernel eucalyptus/ instances/ admin/i- 3BEB06F3/ ramdisk eucalyptus/ instances/ admin/i- 3BEB06F3/ disk-digest eucalyptus/ instances/ admin/i- 3BEB06F3/ disk eucalyptus/ instances/ eucalyptus/ cache/eki- 8F0A139D/ kernel eucalyptus/ instances/ eucalyptus/ cache/eki- 8F0A139D/ kernel- digest eucalyptus/ instances/ eucalyptus/ cache/eri- E64F14E8/ ramdisk eucalyptus/ instances/ eucalyptus/ cache/eri- E64F14E8/ ramdisk- digest eucalyptus/ instances/ eucalyptus/ cache/emi- D5871527/ disk-staging
root@node:
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
However, I never see my instance move from "pending" to "running", so there is a bug here, but perhaps different from whatever you're seeing on your end. 30T22:37: 49.042Z canyonedge eki-8F0A139D eri-E64F14E8
RESERVATION r-31500705 admin default
INSTANCE i-3BEB06F3 emi-D5871527 192.168.0.250 172.19.1.2 pending mykey 0 m1.xlarge
2009-09-
:-Dustin