[bosh-users] Compilation task hangs during sample release deploy on AWS

On Thu, Aug 2, 2012 at 6:51 AM, Ankit wrote:
Hello,

I am trying to deploy a sample release on AWS backed micro bosh instance
(following
https://github.com/drnic/bosh-getting-started/blob/master/create-a-bosh/creating-a-micro-bosh-from-stemcell.md
and
https://github.com/drnic/bosh-getting-started/blob/master/deploying-sample-release.md)
But when I try to deploy the release, the compilation tasks fail after
waiting for 5 mins for the instance to come up. Similar to problem resolved
in
https://groups.google.com/a/cloudfoundry.org/forum/#!topic/bosh-users/Oh0IiTLbQMI
I tweaked the stemcell manifest, but that did not solve the issue as well :(
System logs from the aws instance show the following text,

Xen Minimal OS!
start_info: 0xce2000(VA)
nr_pages: 0x6a400
shared_inf: 0x901be000(MA)
pt_base: 0xce5000(VA)
nr_pt_frames: 0xb
mfn_list: 0x990000(VA)
mod_start: 0x0(VA)
mod_len: 0
flags: 0x0
cmd_line: root=/dev/sda ro 4
stack: 0x94f860-0x96f860
MM: Init
_text: 0x0(VA)
_etext: 0x5ffbd(VA)
_erodata: 0x78000(VA)
_edata: 0x80ae0(VA)
stack start: 0x94f860(VA)
_end: 0x98fe68(VA)
start_pfn: cf3
max_pfn: 6a400
Mapping memory range 0x1000000 - 0x6a400000
setting 0x0-0x78000 readonly
skipped 0x1000
MM: Initialise page allocator for 103e000(103e000)-6a400000(6a400000)
MM: done
Demand map pfns at 6a401000-206a401000.
Heap resides at 206a402000-406a402000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x6a401000.
Initialising scheduler
Thread "Idle": pointer: 0x206a402010, stack: 0x13b0000
Initialising xenbus
Thread "xenstore": pointer: 0x206a4027c0, stack: 0x13c0000
Dummy main: start_info=0x96f960
Thread "main": pointer: 0x206a402f70, stack: 0x13d0000
"main" "root=/dev/sda" "ro" "4"
vbd 2048 is hd0
******************* BLKFRONT for device/vbd/2048 **********


backend at /local/domain/0/backend/vbd/373/2048
Failed to read /local/domain/0/backend/vbd/373/2048/feature-barrier.
Failed to read /local/domain/0/backend/vbd/373/2048/feature-flush-cache.
4194304 sectors of 512 bytes
**************************
vbd 2051 is hd1
******************* BLKFRONT for device/vbd/2051 **********


backend at /local/domain/0/backend/vbd/373/2051
Failed to read /local/domain/0/backend/vbd/373/2051/feature-barrier.
Failed to read /local/domain/0/backend/vbd/373/2051/feature-flush-cache.
1835008 sectors of 512 bytes
**************************
vbd 2064 is hd2
******************* BLKFRONT for device/vbd/2064 **********


backend at /local/domain/0/backend/vbd/373/2064
Failed to read /local/domain/0/backend/vbd/373/2064/feature-barrier.
Failed to read /local/domain/0/backend/vbd/373/2064/feature-flush-cache.
312705024 sectors of 512 bytes
**************************

[H
[J

GNU GRUB version 0.97 (1740800K lower / 0K upper memory)



[ Minimal BASH-like line editing is supported. For

the first word, TAB lists possible command

completions. Anywhere else TAB lists the possible

completions of a device/filename. ]




grubdom>
[9;10H




Has anyone encountered this or similar issue?

Another issue that I faced is that when the micro bosh instance is restarted
the agent doesn't startup cleanly complaining about aws registry which
complains about nats_server and nats_server complains about some
components
missing. What is the standard way to start agent service and the rest of the
required components?

Thanks in advance!