Bug 735

Summary:	Installation fails at 'Bootloader' step with error 'Too many open files' (Beta1)
Product:	Mageia	Reporter:	Frank Eisele <franksf77>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	Normal	CC:	davidwhodgins, mageia, phhusson, pterjan
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	drakx-installer-stage2	CVE:
Status comment:

Description Frank Eisele 2011-04-09 13:07:13 CEST

Description of problem:
Installation halts at step 'Bootlader'. After the message 'Configuring bootloader. This may take a while' (or something like that) a blank info screen appears and the installation halts. Switching to console (Alt-F3) reveals the problem: A continuous stream of messages saying

Starting ConfigureX
Error: Too many open files

Installed from x86_64 DVD, graphical installer, installed to a freshly formatted partition on sdb. Installed to a 'real' system.

An installation in VirtualBox did run through smoothly.

Version-Release number of selected component (if applicable): Beta1


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:

Ahmad Samir 2011-04-12 08:10:55 CEST

CC: (none) => mageia, pterjan
Source RPM: (none) => drakx-installer-stage2

Comment 1 Pierre Hugues Husson 2011-04-24 17:55:32 CEST

I've got the error too, it totally prevents me from installing Mageia.
The error isn't specifically in Bootloader component.
Depending on how I do the first steps (expert partitioning mode or such), it hangs at various places, so the problem seems "only" to be that something (the whole installer ?) is opening too many files.
At some point, it hit this error before even starting to install packages ! (I think the error was that it couldn't load KDE's icon)
A fix could just be to extent the limit from 1024 to higher values.

CC: (none) => phhusson

Comment 2 Dave Hodgins 2011-04-24 20:13:04 CEST

I'm guessing this is related to messages seen in a konsole when running
harddrake2.  I'm getting messages ...
File descriptor 134 (/dev/input/event2) leaked on lvm2 invocation. Parent PID 5183: /usr/bin/perl
File descriptor 135 (/dev/input/event3) leaked on lvm2 invocation. Parent PID 5183: /usr/bin/perl
File descriptor 136 (/dev/input/event4) leaked on lvm2 invocation. Parent PID 5183: /usr/bin/perl

Syslog has messages like "running: lvm2 lvs --noheadings --nosuffix --units s -o lv_size /dev/bk/usr", so this appears to be a problem with
/usr/lib/libDrakX/lvm.pm in the section

sub get_lv_size {
    my ($lvm_device) = @_;
    to_int(run_program::get_stdout('lvm2', 'lvs', '--noheadings', '--nosuffix', '--units', 's', '-o', 'lv_size', "/dev/$lvm_device"));
}

I don't know what the fix is, but hopefully this will help narrow it down.

CC: (none) => davidwhodgins

Comment 3 Pascal Terjan 2011-04-24 20:24:18 CEST

Thanks, this is unrelated to lvm call (lvm gives such warning when you have open file descriptors) but that gives some information regarding which are the open files

Comment 4 Pascal Terjan 2011-04-24 21:22:43 CEST

Bug was in c::EVIocGBitKey, fixed in svn

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