version no more maintained
** Changed in: linux-ec2 (Ubuntu Lucid)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when
Closing only the linux (Ubuntu) task as Java was removed from the Ubuntu
repositories due to Oracle dissolving the Operating System Distributor
License for Java [1][2], Oracle has sunsetted Java 6 for the general
public [3], and this issue being reproducible in linux-ec2.
[1]
eol reached https://wiki.ubuntu.com/Releases
** Changed in: linux (Ubuntu Natty)
Status: Confirmed = Invalid
** Changed in: linux (Ubuntu Maverick)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have this same issue running node.js on a t1.micro in eu-west-1a,
identical kernel oops as Matt notes for erlang/postgresql. Every
invocation of node immediately goes into this state. :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same experience here, please be aware that the zone naming is specific
for an account and not globally. So if you see eu-west-1a that can for
me be 1b or 1c. There is not consistency between accounts for that.
How I worked around this is that I've started 3 instances and found out
that in only
In reply to comments #73 and #74, I believe my erlang issue to be
identical to the java issue in this report because the kernel oops is
identical. Do you have the same oops or a different one? Is there any
benefit to filing this against erlang and postgresql now the underlying
hypervisor issue
Matt, I suspect you are correct that this is the same issue hit another way.
I also suspect that if we had a tiny C test case that illustrated the issue
(which I've never gone after) we'd have a much better likelyhood of finding a
guest or host level work around. However, I think most parties
Re comment#72, can you file a new bug for erlang and postgresql?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when installing java
To manage notifications
I believe that the erlang issue is something different entirely, so
would also like to see another bug report filed. I have experienced some
lockup/CPU drag oddness with erlang on c1.xlarge's, not just t1.micro..
but haven't had the time to debug it just yet. Matt, please post back
here with the
I've experienced this exact issue on t1.micro instances in eu-west-1
running erlang and postgresql. Java isn't even installed. Does Amazon
have a publicly accessible page tracking the issue and the rollout of
the fix to regions other than us-west-2?
--
You received this bug notification
** Also affects: openjdk-6 (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when installing java
To manage
Just confirming that it's working for my instances launched in us-
west-2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when installing java
To manage
Ben, do you have a link to Amazon confirming this issue being fixed in
US-WEST-2? Is it on the AWS developer forums? I would like to follow up
to see if they could then fix it in other regions :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
US-West-2 availability region I suggest is a misnomer.
There are availability zones us-west-2a and us-west-2b in the us-west-2 region.
On 9 November 2011 15:33, Ben Howard 634...@bugs.launchpad.net wrote:
On 2011-11-08, Amazon launched the US-West-2 availability region. (
On 2011-11-08, Amazon launched the US-West-2 availability region. (
http://aws.typepad.com/aws/2011/11/now-open-us-west-portland-region.html
)
This region appears to NOT be affected by the bug. If you are
experiencing this bug and are not bound to a particular EC2 region,
please try the
PS Thanks for the heads up.
On 9 November 2011 15:50, Daniel Sikar dsi...@gmail.com wrote:
US-West-2 availability region I suggest is a misnomer.
There are availability zones us-west-2a and us-west-2b in the us-west-2
region.
On 9 November 2011 15:33, Ben Howard 634...@bugs.launchpad.net
Amazon has verified that this issue does not exist in the US-West-2
region and has suggested that users who are affected should consider
using US-West-2 as a viable and easy work around. US-West-2 has the
same pricing as US-East-1 for the t1.micro,.
--
You received this bug notification because
We have investigated the problem and can confirm that the bug lies in
the underlying EC2 hypervisor; this bug cannot be fixed at the AMI
level. The problem only affects launches on 32-bit t1.micro instances.
Canonical has been in contact with and remains in contact with Amazon
regarding a final
We also seeing this Issue : [Command Log]
Updating category cmap..
Setting up openjdk-6-jre-lib (6b20-1.9.9-0ubuntu1~10.04.2) ...
Setting up openjdk-6-jre-headless (6b20-1.9.9-0ubuntu1~10.04.2) ...
update-alternatives: using /usr/lib/jvm/java-6-openjdk/jre/bin/java to provide
/usr/bin/java
We are also having the same problem with a micro machine. Any news on this?
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when installing java
To
Does anyone know if Amazon has incorporated the patch? Is this still an
open bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when installing java
To
I had the same problem on a hardy amd64 hardy dom0 running xen 3.2 and
kernel 2.6.24-21-xen. When I tried to install sun-java6-jdk on an i386
lucid domU.
I can confirm that the xen patch mentioned by Stefan in comment 58
solved my problem.
Before patching, the installation of sun-java6-bin
I run into this with: apt-get install ec2-api-tools
You may want to let Amazon know. It's a bad user experience to hang at the EC2
tools installation.
Until I saw this bug report, I thought this was an example of the t1.micro
instance CPU throttling:
At last I think I can point at one single patch which would need to get
applied to the kernel running as dom0 on Amazon EC2 hosts:
http://xenbits.xen.org/hg/staging/xen-3.1-testing.hg/rev/f1574ad9f702
I took the CentOS5.3 kernel, compiled it as a base for the comparison.
Installed it as dom0
Sent the patch to Amazon for consideration and comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when installing java
To manage notifications about this
Finally was able to recreate this behaviour locally. Using CentOS 5.3 as
dom0, then I took a current oneiric ec2 image for domU, started a
javajdk-6-jdk install and got the endless look of multicall failed
messages in domU. Meanwhile I could see in dom0 that there was a
matching stream of
If this is useful in diagnosing the problem or solution, I tried using
nice when running the install, and it worked 2 times. Failed 2 times.
The last time I added the --adjustment=19, and it succeeded. Is it an IO
related problem? Here's my full script.
#!/bin/bash
sudo add-apt-repository deb
I think that the root cause is a corrupted p2m_host[] list via a PV-GRUB
bug. Updated PV-GRUB AKIs are now available. These can be used in us-
east-1 to verify the fix:
32-bit: aki-805ea7e9
64-bit: aki-825ea7eb
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Does not seem to fix the problem. Tested using Maverick (ami-ccf405a5)
and aki-805ea7e9 it still triggers a 100% CPU state when installing the
Sun JDK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The stack trace is different though:
Jun 21 17:35:36 ip-10-244-167-3 kernel: [ 110.935506] [ cut here
]
Jun 21 17:35:36 ip-10-244-167-3 kernel: [ 110.935508] WARNING: at
/build/buildd/linux-2.6.38/arch/x86/xen/multicalls.c:182
xen_mc_flush+0x1a8/0x1b0()
Jun 21
I've moved the oneiric builds to using the new AKIs. If we find that we
can fix this issue by some combination of kernel changes and pv-grub
changes we can then apply that to the defaults for stable releases.
tomorrows' oneiric builds should use these new akis.
--
You received this bug
I hope that since it remains as confirmed in linux-ec2 and
new/confirmed in linux that the Ubuntu team is still following up with
the root cause, and the release notes being updated doesn't de-
prioritize fixing the root issue. Is this understanding correct?
--
You received this bug notification
** Changed in: linux (Ubuntu Maverick)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when installing java
--
ubuntu-bugs
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when installing java
--
** Changed in: ubuntu-release-notes
Status: New = In Progress
** Changed in: ubuntu-release-notes
Assignee: (unassigned) = Andy Whitcroft (apw)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Natty release note text added:
Installing Java in a 32 bit t1.micro instance will hang, as a work
around you may install Java in a t1.small instance and then resize the
instance (see comment #13 for details). (634487)
** Changed in: ubuntu-release-notes
Status: In Progress = Fix
Please tell me this is not intended to be a the fix @Andy... If you have
been following the discussion you will know that the process of
installing on a different size instance and resizing to a micro will
cause random instability and crashes.
The method of changing the instance size should only
I second @Andrew Manson: the workaround is just that, it is not a fix.
It's also been known for 6 months.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when
** Changed in: linux (Ubuntu Natty)
Milestone: None = natty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when installing java
--
ubuntu-bugs
I also think that this is a very severe bug. Can it be expected to be
fixed for the Natty release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when
I have this exact issue with the bitnami cloud joomla image.
i686 GNU/Linux
Ubuntu 10.04.2 LTS
*** Welcome to the BitNami Joomla! Stack 1.5.23-0 ***
*** Please visit http://bitnami.org/faq/cloud_images
It fails installing the amazon ec2 tools, at the point of installing
openjdk. Machine hangs,
Now I know how I ended up with CentOS 5.5... yum upgrade is probably
more than I intended to do. So at least that gives one more test: CentOS
5.5 + Xen 3.0.3 which seems to work as well with the current Natty test.
Which would leave the dom0 kernel as the place a fix would need to go...
Here
Ok, so same test environment moved to an Intel, i7 920 box and the
openjdk install works as well. That seems to point strongly into some
interaction issue with the hypervisor/dom0. Hm, I thought I went for
CentOS 5.4 but apparently I ended up with 5.5 running a
2.6.18-194.32.1.el5xen kernel in
I repeated the Natty test with some extended debugging on another micro
instance. The (annotated) output is below. As far as I understand it
xen_set_pud() initiates a mmu_update multicall but by the time it gets
flushed, there is still only one call present. This is a MMU_UPDATE
hypervisor call.
I just want to add the results of some quick tests I did for Natty. The
test (as it was described above) was to install openjdk-6-jdk (there is
no sun package for Natty, yet). I tried on two us-east-1 t1.micro 32bit
instances and one us-west-1 64bit instance, plus on a 32bit instance
that used the
I'd like to confirm that workaround works. I say works, because,
while it allows dpkg to finish installing package, when instance type is
reverted to t1.micro, instance is unable to run anything java-based.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On how to fix corrupted apt-get/dpkg:
1. Run: dpkg -l |grep -v -E ^ii
This will list all packages that are either not in perfectly installed
state; either incompletely installed, or that have config files
remaining behind them after they have been uninstalled (or some other
variant). You can
Also, if you wish to remove all listed packages, first you can run this,
to see the list of packages-to-be-removed:
echo `dpkg --list | tail -n +6 | grep -v -E ^ii | cut -d -f3`
After you are 100% sure that you know what exactly is going to be
removed (so you don't get your system to even more
Until this bug is fixed, any help on how to fix a corrupted apt-get/dpkg state
would be very helpful.
Basically, after trying to install the JRE, apt-get is unable to install any
other package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: linux (Ubuntu Natty)
Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs
I'm surprised this isn't higher priority. This will kill an entire
instance, and SUN JRE is useful if you plan on trying to use the RDS
command line tools.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu Lucid)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when installing java
--
ubuntu-bugs mailing
** Changed in: linux-ec2 (Ubuntu Lucid)
Importance: Undecided = Medium
** Changed in: linux-ec2 (Ubuntu Lucid)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Closing the java tasks (as per comment #31)
** Changed in: sun-java6 (Ubuntu Lucid)
Status: New = Invalid
** Changed in: sun-java6 (Ubuntu Maverick)
Status: New = Invalid
** Changed in: sun-java6 (Ubuntu Natty)
Status: New = Invalid
** Changed in: linux-ec2 (Ubuntu Natty)
** Changed in: openjdk-6 (Ubuntu Lucid)
Status: New = Incomplete
** Changed in: openjdk-6 (Ubuntu Lucid)
Status: Incomplete = Invalid
** Changed in: linux-ec2 (Ubuntu Maverick)
Status: New = Invalid
** Changed in: openjdk-6 (Ubuntu Maverick)
Status: New = Invalid
**
I had to run 64-bit instance and run java with -XX:+UseCompressedOops to
reduce memory overhead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when installing
Does anyone know how to recover from this issue temporarily? After
requesting the install once, no matter what apt-get command I do, I get:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure
-a' to correct the problem.
When I run that command, the hang occurs again and again.
@Peter The workaround described in comment #13 will probably help you.
Don't run 'sudo dpkg --configure -a' until the instance is started as a
small.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Peter If you only want to pay the cost of a micro instance, the
workaround that worked best for me is to use a 64-bit Ubuntu image,
which runs in a micro instance as well. For our apps, though, there is
no sensitivity whether Java is running 64-bit or 32-bit, so YMMV.
Running 64-bit also causes
** Summary changed:
- t1.micro instance hangs when installing sun java
+ t1.micro instance hangs when installing java
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance
60 matches
Mail list logo
