Bug 4855

Summary:	Installing updates fails with Out of memory!
Product:	Mageia	Reporter:	Dave Hodgins <davidwhodgins>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	thierry.vignaud
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	urpmi-6.46-1.mga2.src.rpm	CVE:
Status comment:

Description Dave Hodgins 2012-03-09 00:05:08 CET

I was just installing update for my cauldron install while chrooted to
it from Mageia 1.

I got ...
Proceed with the installation of the 69 packages? (Y/n) y
<snip>
57/69: kde-wallpapers        ################################################################################
Out of memory!

The Out of memory line is repeated 4 times.

I'm not sure if this is a urpmi or rpm problem.

I'll try a urpmi --debug now to see if it repeats.

Comment 1 Dave Hodgins 2012-03-09 00:11:25 CET

The following run installed the remaining 12 packages ok, so this one
will be difficult to recreate.

Comment 2 Dave Hodgins 2012-03-09 00:28:34 CET

Also, I've saw no indication of a memory problem.
free -m
             total       used       free     shared    buffers     cached
Mem:          2014       1892        121          0        107        484
-/+ buffers/cache:       1300        713
Swap:         6134          0       6134

Note the zero swap usage.

Comment 3 Thierry Vignaud 2012-03-09 07:39:46 CET

rpm -q rpm?
Can you see in dmesg which program reported OOM?

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud

Comment 4 Dave Hodgins 2012-03-09 08:43:40 CET

# rpm -q rpm
rpm-4.9.1.2-20.mga2

I've rebooted since then for other tests, and didn't think
to capture dmesg right after the error.

I've since installed 222 updates, without any problem.

While those updates were installing, I was watching with htop,
and the rss for urpmi never went over 75000 bytes.

I have no idea how to recreate the problem.

Comment 5 Thierry Vignaud 2012-03-09 08:47:28 CET

I would close as OLD then.
Maybe the post-install script of some package went havoc

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 6 Dave Hodgins 2012-04-03 04:20:51 CEST

Happened again.  Did some searching and found it has happened in
the past with Mandriva.

http://us.generation-nt.com/answer/chroot-out-memory-help-173289761.html

Seems the problem is likely caused by booting an older glibc
than what is being used by programs in the chroot environment,
and is somehow effectively making swapping unavailable.

Leaving the bug marked as resolved.  Just wanted to add the
above info, to make it easier for others to find.