Indeed, this still happens with 16.04. More weird, this happens without
user running atop, just system suddenly pops up an window that atop
crashed. Why on earth Ubuntu runs atop behind user's back?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I got hit by the same issue, with the same unlucky kernel (installed
from normal update channel):
root@x230:~# uname -a
Linux x230 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
Will read suggestions above before going to back to classical VM...
--
The above report is against:
lxc 1.0.7-0ubuntu0.7
amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Upgrading to 1.0.7-0ubuntu0.9 from updates fixed it. Sorry for the
noise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504781
Title:
lxc-test-ubuntu hangs forever in trusty-proposed with Linux
The above report is against:
lxc 1.0.7-0ubuntu0.7
amd64
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I got hit by the same issue, with the same unlucky kernel (installed
from normal update channel):
root@x230:~# uname -a
Linux x230 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
Will read suggestions above before going to back to classical VM...
--
Upgrading to 1.0.7-0ubuntu0.9 from updates fixed it. Sorry for the
noise.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1504781
Title:
lxc-test-ubuntu hangs forever in trusty-proposed
This is especially annoying, as if Go is not installed, typing go
proposes to install gccgo, at least in Trusty, instead of the official
golang package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In Ubuntu 14.04, I had the same error page trying to use ML-1660 driver.
As suggested, I used CLP-310 driver, and there were actually two of
them, one marked foomatic and one not. I chose foomatic and indeed, it
works (I set resolution to 600x600 as was suggested, didn't try 1200).
One difference
Brave guy at http://www.linuxquestions.org/questions/linux-newbie-8
/what-is-gvfsd-metadata-4175458624/ proposes more permanent workaround:
chmod -x /usr/lib/gvfs/gvfsd-metadata. If you think about it for a
bit, that solution has its merit: if you already have your metadata in
your file system,
Public bug reported:
When running 64-bit guests in 32-bit Ubuntu 12.04, the host with high
probably goes into abrupt reboot sooner or later. There's upstream bug
for this:
https://www.virtualbox.org/ticket/10528
It reports that the issue was fixed in Virtualbox 4.1.18 . Please
consider upgrade
Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655202
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071344
Title:
12.04's current virtualbox 4.1.12 crashes (reboots) 32-bit host on
Today we're having 403's on ci.linaro.org again, see attachment for a
sample log.
** Attachment added: i-18e33761.log
https://bugs.launchpad.net/linaro-android-infrastructure/+bug/932088/+attachment/3177116/+files/i-18e33761.log
--
You received this bug notification because you are a
+ + echo Acquire::http::Pipeline-Depth 0;^M
tee /etc/apt/apt.conf.d/99no-pipelining^M
Acquire::http::Pipeline-Depth 0;^M
Well, this command exactly disables pipelining.
so, what are the exact changes on a-b* that we have that fixes this
problem ?
The best way probably will be to compare
so, what are the exact changes on a-b* that we have that fixes this
problem ?
And it fixed it for Ubuntu version we use on android-build (Natty).
They may be different/additional issues with OS versions we use on ci.*.
That's why I think that we should just switch to custom AMI as a
sustainable
This seems to be stably fixed for linaro-android-infrastructure, closing
in it (may still be pertinent for linaro-ci and ubuntu).
** Changed in: linaro-android-infrastructure
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Just for stats, Linaro's https://android-build.linaro.org/jenkins/
didn't have any issues lately (is on S3 mirror w/o pipelining).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932088
Title:
Ubuntu
Thanks Scott!
I've just re-enabled S3 mirror, it works ok now:
Get:23 http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/
natty/main g++-4.5 amd64 4.5.2-8ubuntu4 [6,511 kB]
Get:24 http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/
natty/main g++ amd64
As of now (well, for couple of hours at least) we're having following
errors. These are known to happen from time to time, and dissolve after
some time (we usually attribute it to to ongoing package repository
update), but this ones seems like taking longer then usual, so figure
I'd post about it
Switching back to standard EC2 mirror (from S3 one) fixed that for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932088
Title:
Ubuntu EC2 package mirror intermitent failures
To manage
We just had a case of 10+ broken builds slave being started up in short
time. Typical Jenkins instance init log:
https://ci.linaro.org/jenkins/computer/i-185d097f/log
As you can see, Acquire::http::Pipeline-Depth 0; is set, but still
there's hashsum mismatch error (but the fact that dozen of
Also, if you look that log carefully, you can see following weird thing:
we do two apt-get updates in row, with sleep 2 inbetween. First update
hits *only*
http://security.ubuntu.com
http://archive.ubuntu.com
doesn't hit in-EC2 mirror at all. Second updates starts to hit http
That's with ami-b5ea34dc just in case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932088
Title:
Ubuntu EC2 package mirror intermitent failures
To manage notifications about this bug go to:
Yes, those slave log links expire with slaves, that's why I pasted it
in . https://bugs.launchpad.net/linaro-android-
infrastructure/+bug/932088/comments/27/+download should give the same
info as if it was attached.
And yes, this latest issue and log from ci.linaro.org, which is not yet
uses S3
But on ci.linaro.org (non-S3 mirror):
$ grep -l -a Hash Sum mismatch *|wc
40 401309
So, I'm going to leverage same config to ci.linaro.org and see how it
goes (it uses different set of AMIs, so results may not match android-
build).
--
You received this bug notification because
Update on android-build.linaro.org (uses S3):
$ grep -l -a -E '^Failed to fetch.+s3' * | tail -n3
2012-04-03-slave-i-69bb4e0e.log
2012-04-04-slave-i-0f32c068.log
2012-04-04-slave-i-a5a153c2.log
$ grep -l -a Hash Sum mismatch * | tail -n3
2012-04-04-slave-i-25629242.log
I personally not sure what happens here, but:
Just opening http://us-
east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/natty-
updates/ in a browser leads to 403 XML. Ok, suppose it's limited to only
EC2. From out EC2 machine:
ubuntu@ip-10-243-34-224:~$ wget
On the other hand:
$ grep -l -a -E '^Failed to fetch.+s3' * | tail -n3
2012-04-03-slave-i-69bb4e0e.log
2012-04-04-slave-i-0f32c068.log
2012-04-04-slave-i-a5a153c2.log
Last line matches the line in comment #15 which I made shortly before
turning off pipelining. Which means we didn't have (that
Ok, now I eyeballed few logs and tentative conclusion - thank you very
much, turning off pipelining seem to have solved our issues! Not even
those weird 403's don't pop up after 2012-04-04. If you're interested
what it was here's example:
2012-04-04-slave-i-a5a153c2.log:W: Failed to fetch
Sorry for delays with responses. The story on our side was that we
implemented auto-retries for failed apt-get invocations in our scripts
with exponential back-off on 2012-03-06, and that fixed it for us, at
least I never saw slaves failed to launch. Soon after that we were
swamped into other
$ grep -l -a -E '^Failed to fetch.+s3' *
...
2012-03-06-slave-i-63954a07.log
2012-03-06-slave-i-7d12c119.log
2012-03-06-slave-i-e1c51a85.log
2012-03-07-slave-i-31c66355.log
2012-03-07-slave-i-fbd9029f.log
2012-03-08-slave-i-5961c23d.log
2012-03-08-slave-i-5f40ee3b.log
echo Acquire::http::Pipeline-Depth 0; | sudo tee /etc/apt/apt.conf.d
/99no-pipelining - was added to our EC2 instance init scripts, I'll be
watching how it goes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Previous note is about applying to android-build.linaro.org. Now also
applied to ci.linaro.org, where have slave apt-get issues, albeit errors
we get there are different %).
** Changed in: linaro-android-infrastructure
Status: Fix Released = In Progress
** Also affects: linaro-ci
We worked that around by adding retries for apt-get operations with
exponential backoff and eventual abort after 6 retries (64s wait last
time). Of 51 instances which were launched since that fix was deployed,
18 had retries kick in. And 10 still failed in the end (i.e. after 6
retries). However,
This latest round of issues is tracked in our bug lp:941784, which may
have more info.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932088
Title:
Ubuntu EC2 package mirror intermitent failures
To
Here's good AWS forum thread from 2008:
https://forums.aws.amazon.com/thread.jspa?threadID=21514 . According to
it, 403 Forbidden in AWS-speak means there may be unusually long
propagation delay.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This miscalculation causes the OMAP4 bootloader to fail to boot.
Fix a bug where sector counts would be off-by-one due to a division error.
Required for OMAP3/4 bootROM to always be happy with a partition
Can you please confirm that this patch actually fixes FS metadata fields
and makes
We started to see following issues with beta S3 mirror:
Get:40 http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/
natty/main zip amd64 3.0-3build1 [265 kB]
Failed to fetch
Have been working ok for android-build.linaro.org , and at the end of
our monthly cycle, we'd like to close this in linaro-android-
infrastructure project. We still hope this we be open in Ubuntu for
reference and to allow to communicate any issues/observations. Thanks.
** Changed in:
-infrastructure
Assignee: (unassigned) = Paul Sokolovsky (pfalcon)
** Changed in: linaro-android-infrastructure
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932088
Deployed, I mean, source.list editing per
http://groups.google.com/group/ec2ubuntu/browse_thread/thread/507f58dd51b6b631
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932088
Title:
Ubuntu EC2
** Branch linked: lp:~pfalcon/linaro-android-build-tools/ec2-s3-mirror
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932088
Title:
Ubuntu EC2 package mirror intermitent failures
To manage
** Changed in: linaro-android-infrastructure
Importance: Undecided = High
** Changed in: linaro-android-infrastructure
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
With announcement https://lists.ubuntu.com/archives/ubuntu-security-
announce/2012-January/001554.html going into force, it seems that
underlying load balancing servers behind
http://archive.canonical.com/ubuntu/pool/partner/s/sun-java6/ have
inconsistent set of packages.
Thanks for quick reply, Scott. I'll RFC switching to new S3 sources, and
unless our service stakeholder raise serious concerns with that, going
to try them soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For what it's worth, I'm seeing this issue (100% CPU usage, Gnome
desktop hangs completely on start) with Jaunty installed from http
://old-releases.ubuntu.com/ubuntu/ , running in a chroot under Android
on a Tegra2 tablet %).
--
You received this bug notification because you are a member of
Installing http://old-releases.ubuntu.com/ubuntu/pool/main/g/gnome-
keyring/gnome-keyring_2.28.1-0ubuntu1_armel.deb (using dpkg -i --force-
all) makes desktop not hang on start (like with 2.26.1-0ubuntu1), but
gnome-keyring-daemon still eats 100% CPU.
So, rm
Public bug reported:
0.9.6 is required for recently released ffmpeg 0.8, and without package
available trying it drowns in dependency hell. Thanks.
** Affects: libvpx (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
48 matches
Mail list logo
