Created
June 17, 2011 15:42
-
-
Save rentalcustard/1031669 to your computer and use it in GitHub Desktop.
Chef/EC2/Java problem
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#Running knife bootstrap, I get this: | |
ec2-46-137-58-164.eu-west-1.compute.amazonaws.com [Fri, 17 Jun 2011 15:03:45 +0000] INFO: execute[apt-get update] ran successfully | |
ec2-46-137-58-164.eu-west-1.compute.amazonaws.com [Fri, 17 Jun 2011 15:03:45 +0000] INFO: Processing ruby_block[reload_ohai] action nothing (java::default line 24) | |
ec2-46-137-58-164.eu-west-1.compute.amazonaws.com [Fri, 17 Jun 2011 15:03:45 +0000] INFO: Processing execute[update-java-alternatives] action nothing (java::default line 33) | |
ec2-46-137-58-164.eu-west-1.compute.amazonaws.com [Fri, 17 Jun 2011 15:03:45 +0000] INFO: Processing package[sun-java6-jre] action install (java::default line 42) | |
ec2-46-137-58-164.eu-west-1.compute.amazonaws.com [Fri, 17 Jun 2011 15:03:45 +0000] INFO: Processing cookbook_file[/var/chef/cache/preseed/java/sun-java6-jre-6.24-1build0.10.04.1.seed] action create (dynamically defined) | |
ec2-46-137-58-164.eu-west-1.compute.amazonaws.com [Fri, 17 Jun 2011 15:03:45 +0000] INFO: cookbook_file[/var/chef/cache/preseed/java/sun-java6-jre-6.24-1build0.10.04.1.seed] created file /var/chef/cache/preseed/java/sun-java6-jre-6.24-1build0.10.04.1.seed | |
ec2-46-137-58-164.eu-west-1.compute.amazonaws.com [Fri, 17 Jun 2011 15:03:45 +0000] INFO: package[sun-java6-jre] pre-seeding package installation instructions |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#EC2's server log shows this... | |
[ 2198.709869] BUG: soft lockup - CPU#0 stuck for 121s! [java:7864] | |
[ 2198.709869] Modules linked in: ipv6 | |
[ 2198.709869] | |
[ 2198.709869] Pid: 7864, comm: java Tainted: G D (2.6.32-316-ec2 #31-Ubuntu) | |
[ 2198.709869] EIP: 0061:[<c01013a7>] EFLAGS: 00200246 CPU: 0 | |
[ 2198.709869] EIP is at 0xc01013a7 | |
[ 2198.709869] EAX: 00000000 EBX: 00000003 ECX: e52e3e64 EDX: 00000008 | |
[ 2198.709869] ESI: 00000015 EDI: e52e3e74 EBP: e52e3e80 ESP: e52e3e60 | |
[ 2198.709869] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069 | |
[ 2198.709869] CR0: 8005003b CR2: b760e5d8 CR3: 01864000 CR4: 00002620 | |
[ 2198.709869] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 | |
[ 2198.709869] DR6: ffff0ff0 DR7: 00000000 | |
[ 2198.709869] Call Trace: | |
[ 2198.709869] [<c044693d>] ? xen_poll_irq+0x7d/0xc0 | |
[ 2198.709869] [<c044a09a>] xen_spin_wait+0x6a/0x130 | |
[ 2198.709869] [<c0535acd>] _spin_lock+0x4d/0x60 | |
[ 2198.709869] [<c0114c6a>] _pin_lock+0x1da/0x210 | |
[ 2198.709869] [<c03e67af>] ? cpumask_next_and+0x1f/0x40 | |
[ 2198.709869] [<c015d69f>] ? smp_call_function_many+0x4f/0x220 | |
[ 2198.709869] [<c01159d9>] mm_unpin+0x19/0x30 | |
[ 2198.709869] [<c0115a68>] arch_exit_mmap+0x78/0x80 | |
[ 2198.709869] [<c01b6e1f>] exit_mmap+0x2f/0x190 | |
[ 2198.709869] [<c012ff65>] ? mm_release+0xc5/0xe0 | |
[ 2198.709869] [<c0130496>] mmput+0x26/0xd0 | |
[ 2198.709869] [<c0134bc6>] exit_mm+0xe6/0x120 | |
[ 2198.709869] [<c0420538>] ? tty_audit_exit+0x28/0xe0 | |
[ 2198.709869] [<c01352f3>] do_exit+0x103/0x300 | |
[ 2198.709869] [<c01359ed>] do_group_exit+0x3d/0xe0 | |
[ 2198.709869] [<c0135aa3>] sys_exit_group+0x13/0x20 | |
[ 2198.709869] [<c01047e0>] syscall_call+0x7/0xb |
Sorry, should be clearer. It hangs on the last line from the first file. Maybe just a problem with running on a micro instance? Scaling up to small to see if there's any change.
Hmm possibly, not something I have come across before on Rackspace cloud.
I'll give it a go myself
…On Fri, Jun 17, 2011 at 4:52 PM, mortice < ***@***.***>wrote:
Sorry, should be clearer. It hangs on the last line from that file. Maybe
just a problem with running on a micro instance? Scaling up to small to see
if there's any change.
##
Reply to this email directly or view it on GitHub:
https://gist.github.com/1031669
Seems fine on a small instance.
cool
…On Fri, Jun 17, 2011 at 5:13 PM, mortice < ***@***.***>wrote:
Seems fine on a small instance.
##
Reply to this email directly or view it on GitHub:
https://gist.github.com/1031669
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
what's the issue? does it install?