Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ubuntu 16.04: “Out of memory” errors after upgrade to 4.4.0-59

bugs.launchpad.net

Post reply on HN
Print view View original

161–170 of 175 posts

Re: Ubuntu 16.04: “Out of memory” errors after upgrade to 4.4.0-59

#161

Post by [deleted] »

amluto wrote: post #11
Pxtl wrote: post #7

Earlier quoted context omitted.

Yeah, Ubuntu still keeps running out of space in /boot by filling it w old kernels in the default partition profile. A bug that I've been hitting since about 2011. In spite of their best efforts, it is not the "grandma friendly" quality software it hoped to be.

My M.O. is: # apt-get update # aptitude full-upgrade # apt-get autoremove Because as far as I can tell, apt-get sometimes fails to actually update things, whereas aptitude can't autoremove. I'm sure there's a better way. This is my major gripe with the dpkg ecosystem. There are (AFAICT) multiple different tools to build dpgks and multiple different tools for updating your system, and none of them are adequately docum…

[deleted]

Re: Ubuntu 16.04: “Out of memory” errors after upgrade to 4.4.0-59

#162

Post by antod »

lima wrote: post #137
JdeBP wrote: post #112

Earlier quoted context omitted.

andrewshadura is right. Here's just one of your items that is bunkum, for an example. > their own custom [...] init system of Upstart when they could have contributed to System upstart was developed several years, just under half a decade, before systemd even existed; it was used by Fedora for three years.

It's true though that Canonical consistently "does their own thing" and then fails to establish it as a standard for whatever reason (technical, political, CLA...). Anyone who adopted the new thing then has to migrate. Eucalyptus vs OpenStack (ever heard of Eucalyptus?) Bazaar vs Git (Git won) LaunchPad vs Github (LaunchPad is alive and well, but Github won the popularity contest) Wayland vs Mir (Wayland won) upstart…

In a lot of those cases (Mir being the obvious exception), the Ubuntu backed solution predated the alternative.

I can't help wonder if this will keep happening as their competition waits to see everything new Canonical chooses to back, then works to thwart it :)

Re: Ubuntu 16.04: “Out of memory” errors after upgrade to 4.4.0-59

#163

Post by quotemstr »

quotemstr wrote: post #32
userbinator wrote: post #24

Earlier quoted context omitted.

IMHO if you can't not use swap without running out of memory in normal workloads, you either need more RAM or to work on reducing your memory consumption; swapping is for temporary overloads or gracefully recovering from one, not a substitute for RAM. It's not just a bunch of people setting cm.swappieness to 0 is it? That behaviour changed and now prevents going into swap /ever/ where it used to mean go into swap as…

I think that the new behavior at zero (documented anywhere?) is a discontinuity. There should be a separate setting for mlocking code pages. Swap is useful even if you have plenty of RAM. It's better to swap out a cold file-backed page and use that page for cache instead than to pin that cold page in memory for no reason.

Gah. I meant non-file-backed

Re: Ubuntu 16.04: “Out of memory” errors after upgrade to 4.4.0-59

#164

Post by kasabali »

mrmondo wrote: post #2

It's not just a bunch of people setting cm.swappieness to 0 is it? That behaviour changed and now prevents going into swap /ever/ where it used to mean go into swap as a last resort. Changing it to 1 fixes the issue and will act like the old behaviour or only swapping as a last result. Regardless, it's things like this why we never recommend people use Ubuntu - years of poorly packaged and tested software. If you wan…

RHEL has had a similar behavioral change during lifetime of a release so this particular case is not actually a good example for recommending RHEL over Ubuntu for stability.

https://www.percona.com/blog/2014/04/28/oom-relation-vm-swap...

Re: Ubuntu 16.04: “Out of memory” errors after upgrade to 4.4.0-59

#165

Post by alyandon »

alyandon wrote: post #148
pacifika wrote: post #115

Earlier quoted context omitted.

What does it do?

Take off the xargs part of the command and run it to see. :-D Just looking at it though, it looks like it'll purge kernel packages that are the currently booted one. I don't have a system handy to check though so take that with a grain of salt.

Just for posterity that should have been "are not the currently booted one".

Re: Ubuntu 16.04: “Out of memory” errors after upgrade to 4.4.0-59

#166

Post by rincebrain »

dotancohen wrote: post #60
rincebrain wrote: post #21

Earlier quoted context omitted.

AFAIK, the only supported way to build a deb is using dpkg-buildpackage, and all the others just wrap it (unless we're talking about alien, but that's not really "supported" going any direction). Updating your system is all the same backend, and the Debian-alikes try to tell you to only use one tool for cmdline (apt, now, which just takes the same args as all the various apt-FOO commands did, all of which still work)…

> they wanted to standardize and fix any deficits, rather than working around them. That would work great if would they would take bugs reports seriously. In practice, with Canonical I file a bug and ninety days later get an automated message that the bug was closed due to inactivity.

That's an unfortunate pendulum swing cleaning up from their problem of yester-year - namely, bugs sitting around _forever_ without any comment.

I noticed they changed that policy when I started getting comments on years-old bugs of closed-obsolete. If they're now 90d expiring bugs, I'd _guess_ there's a bit that can be set for your account of whether you're a customer paying for support, and that their support staff have a queue filter that prioritizes those, and the rest get expired if nobody comments.

Re: Ubuntu 16.04: “Out of memory” errors after upgrade to 4.4.0-59

#167

Post by _0w8t »

mrmondo wrote: post #99
_0w8t wrote: post #75

Earlier quoted context omitted.

zswap makes swap useful on the server as it results in gradual slowdown when the system has used all the ram. And if the system runs at 75% of CPU, then there is room for such slowdown.

yes, we run ZRAM of every single server we have, its fantastic and we don't have swap anywhere. It's worth noting though that vm.swappiness is set to 0 then ZRAM wont be used, it must be set to 1 or higher unless you're using a really old kernel (pre 3.5).

I have found that zswap behaves much better than zram when the size of the used ram approaches 150% of RAM. In theory zram compresses better as zswap has very simple mapping for the location of its cache of compressed pages leading to space underutilization. But, as it has real backing store, it can evict unused pages allowing bigger chunk of uncompressed memory for running applications.

Re: Ubuntu 16.04: “Out of memory” errors after upgrade to 4.4.0-59

#168

Post by munin »

Pxtl wrote: post #154
munin wrote: post #37

Earlier quoted context omitted.

I downvoted you for "grandma friendly." My grandma remembers when LaTeX was "new" and was one of the first people to professionally use computer-based typesetting. What exactly does "grandma friendly" look like to her?

Fair enough. I just use the term because I'm "family tech support" for multiple grandmas. I'll avoid that phrasing in the future.

Thank you! :)

Re: Ubuntu 16.04: “Out of memory” errors after upgrade to 4.4.0-59

#169

Post by beagle3 »

pmontra wrote: post #73
Pxtl wrote: post #7

Earlier quoted context omitted.

Yeah, Ubuntu still keeps running out of space in /boot by filling it w old kernels in the default partition profile. A bug that I've been hitting since about 2011. In spite of their best efforts, it is not the "grandma friendly" quality software it hoped to be.

Yep, I had to fix a 14.04 server like that last week. /boot filled with old kernels and apt was falling. I had to manually fix that. I also don't have swap on my laptop (16 GB RAM and SSD) and I rarely hit 10 GB of used space. With no swap I mean no swap partition. I'm getting those out of memory errors in Opera tabs since the new kernel. Luckily my primary browser (FF) is fine. I guess it's trying to swap Opera out…

Likely, opera asks for a disk-based anonymous memory mapping - this goes on the swapfile if you have one, and fails if you don't.
Post reply on HN