Wowza Community

Creating EBS based installation - instance do not initialize

I’m not a Unix nerd - anyway I try to do my best :slight_smile:

I’m would like to an Amazon Wowza instance that I can start and stop. I can understand that I need the instance storage to be of type EBS.

This is what I have tried:

Creating the instance: ec2-run-instances -z eu-west-1c --key myThirdKeyPair ami-80d221f7 (I gave up on DevPay and went for the LicKey model)

Stopped Engine and Engine Manager

Used the following to create a EBS-based snapshot: http://sebastiandahlgren.se/2014/01/16/convert-an-aws-instance-store-ami-to-an-ebs-backed-ami/

Create image from snapshot

Created an new Instance (using my new EBS Image)

When the instance start, it takes a long time and results in “1/2 checks passed”

The system log is below - can someone help?

Linux version 2.6.16-xenU (builder@xenbat.amazonsa) (gcc version 4.0.1 20050727 (Red Hat 4.0.1-5)) #1 SMP Mon May 28 03:41:49 SAST 2007

BIOS-provided physical RAM map:

Xen: 0000000000000000 - 000000006a400000 (usable)

980MB HIGHMEM available.

727MB LOWMEM available.

NX (Execute Disable) protection: active

IRQ lockup detection disabled

Built 1 zonelists

Kernel command line: root=/dev/sda1 ro 4

Enabling fast FPU save and restore… done.

Enabling unmasked SIMD FPU exception support… done.

Initializing CPU#0

PID hash table entries: 4096 (order: 12, 65536 bytes)

Xen reported: 1799.999 MHz processor.

Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)

Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)

Software IO TLB disabled

vmalloc area: ee000000-f53fe000, maxmem 2d7fe000

Memory: 1718700k/1748992k available (1958k kernel code, 20948k reserved, 620k data, 144k init, 1003528k highmem)

Checking if this processor honours the WP bit even in supervisor mode… Ok.

Calibrating delay using timer specific routine… 3601.83 BogoMIPS (lpj=18009150)

Mount-cache hash table entries: 512

CPU: L1 I cache: 32K, L1 D cache: 32K

CPU: L2 cache: 256K

CPU: L3 cache: 20480K

Checking ‘hlt’ instruction… OK.

Brought up 1 CPUs

migration_cost=0

Grant table initialized

NET: Registered protocol family 16

Brought up 1 CPUs

xen_mem: Initialising balloon driver.

highmem bounce pool size: 64 pages

VFS: Disk quotas dquot_6.5.1

Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

Initializing Cryptographic API

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler deadline registered

io scheduler cfq registered

i8042.c: No controller found.

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

Xen virtual console successfully installed as tty1

Event-channel device installed.

netfront: Initialising virtual ethernet driver.

mice: PS/2 mouse device common for all mice

md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27

md: bitmap version 4.39

NET: Registered protocol family 2

Registering block device major 8

IP route cache hash table entries: 65536 (order: 6, 262144 bytes)

TCP established hash table entries: 262144 (order: 9, 2097152 bytes)

TCP bind hash table entries: 65536 (order: 7, 524288 bytes)

TCP: Hash tables configured (established 262144 bind 65536)

TCP reno registered

TCP bic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

NET: Registered protocol family 15

Using IPI No-Shortcut mode

XENBUS: Timeout connecting to devices!

md: Autodetecting RAID arrays.

md: autorun …

md: … autorun DONE.

kjournald starting. Commit interval 5 seconds

EXT3-fs: mounted filesystem with ordered data mode.

VFS: Mounted root (ext3 filesystem) readonly.

Freeing unused kernel memory: 144k freed

request_module: runaway loop modprobe binfmt-464c

request_module: runaway loop modprobe binfmt-464c

request_module: runaway loop modprobe binfmt-464c

request_module: runaway loop modprobe binfmt-464c

request_module: runaway loop modprobe binfmt-464c

Unable to handle kernel paging request at virtual address ed438000

printing eip:

c01123c4

00589000 -> *pde = 0000000e:a759d027

Unable to handle kernel paging request at virtual address 0ae62b50

printing eip:

c0112ffc

00589000 -> *pde = 00000000:00000000

Oops: 0000 [#1]

SMP

Modules linked in:

CPU: 0

EIP: 0061:[] Not tainted VLI

EFLAGS: 00010206 (2.6.16-xenU #1)

EIP is at do_page_fault+0x54c/0x931

eax: 00000b50 ebx: 0ae62b50 ecx: f578d000 edx: 4ae62000

esi: c0589018 edi: c0112ab0 ebp: eb6dfee0 esp: eb6dfe80

ds: 007b es: 007b ss: e021

Process khelper (pid: 7793, threadinfo=eb6de000 task=eb8f7030)

Stack: <0>c0307ef8 00589000 0000000e a759d027 eb6dfee8 00000000 eb8f7030 eb6dfe9c

ed438000 00000001 00000001 fffffff8 c0555200 eb6dff28 c012fc1a 00000003

eb6dfee8 c03080f4 00000003 0000000e 0000000b 00000000 ed438000 c0112ab0

Call Trace:

[] show_stack_log_lvl+0xcd/0x120

[] show_registers+0x1ab/0x240

[] die+0x111/0x240

[] do_page_fault+0x5f7/0x931

[] error_code+0x2b/0x30

[] error_code+0x2b/0x30

[] __mmdrop+0x1b/0x50

[] do_execve+0x1dc/0x215

[] sys_execve+0x42/0xa0

[] syscall_call+0x7/0xb

Code: 07 c1 e0 14 09 c2 80 3d 82 4d 38 c0 00 75 07 8b 14 95 00 00 80 f5 8b 45 c0 c1 e2 0c c1 e8 12 25 f8 0f 00 00 8d 9c 02 00 00 00 c0 <8b> 03 89 44 24 0c 8b 43 04 89 54 24 04 c7 04 24 18 7f 30 c0 89

<1>Unable to handle kernel paging request at virtual address ed45f000

printing eip:

c01123c4

00589000 -> *pde = 0000000e:a759d027

Unable to handle kernel paging request at virtual address 0ae62b50

printing eip:

c0112ffc

00589000 -> *pde = 00000000:00000000

Oops: 0000 [#2]

SMP

Modules linked in:

CPU: 0

EIP: 0061:[] Not tainted VLI

EFLAGS: 00010206 (2.6.16-xenU #1)

EIP is at do_page_fault+0x54c/0x931

eax: 00000b50 ebx: 0ae62b50 ecx: f578d000 edx: 4ae62000

esi: c0589018 edi: c0112ab0 ebp: eb453ee0 esp: eb453e80

ds: 007b es: 007b ss: e021

Process khelper (pid: 22663, threadinfo=eb452000 task=eacc7a70)

Stack: <0>c0307ef8 00589000 0000000e a759d027 eb453ee8 00000000 eacc7a70 eb453e9c

ed45f000 00000001 00000001 fffffff8 ed6fd800 eb453f28 c012fc1a 00000003

etc.

I found the solution.

When creating the image, it is crucial to specify the appropiate KernelId (I got it from the original instance)

Great.

Thanks for sharing.

Zoran