#576250 febootstrap: segfaults and fails to complete bootstrapping

#576250#5
Date:
2010-04-02 07:17:09 UTC
From:
To:
I tried a febootstrap of Fedora 12 and it failed. The failure seems to
be coming at the end, probably from fakeroot or febootstrap itself.


Attached is the full log with the details.


Regards,
Ritesh

#576250#10
Date:
2010-04-08 03:39:00 UTC
From:
To:
Hi,

I ran the commands (also tried with fedora-12 with same result):

    mkdir fed10-64
    febootstrap fedora-10 fed10-64 http://mirror/pub/fedora/linux/releases/10/Everything/x86_64/os

which seemed to go ok but than at the end it does this:

Failed:
  filesystem.x86_64 0:2.4.19-1.fc10

Complete!
/usr/bin/fakeroot: line 1:  5294 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5295 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5296 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5297 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5298 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5299 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5300 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5301 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5302 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5303 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5304 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5305 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5306 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5307 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5308 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5309 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5310 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5311 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1:  5312 Segmentation fault      exit $RESULT
/usr/bin/febootstrap: line 246:  5313 Segmentation fault      rm -rf "$target"/var/cache/yum/febootstrap
/usr/bin/febootstrap: line 246:  5314 Segmentation fault      rm -rf "$target"/var/cache/yum/febootstrap-updates
/usr/bin/febootstrap: line 93:  5315 Segmentation fault      rm -rf "$target"/var/cache/yum/febootstrap-updates



Cheers,
Erik

#576250#15
Date:
2010-04-08 09:19:04 UTC
From:
To:
Which package is this?

Segfaults are in any case caused by incompatibilities between glibc in
the host and appliance.  You have to only install an operating system
which is compatible with the host OS.  In Fedora we recommend only
installing (eg) Fedora 12 on Fedora 12, because that way you know that
glibc won't have problems.

Rich.

#576250#20
Date:
2010-04-08 10:17:16 UTC
From:
To:
Richard W.M. Jones wrote:

    ii  febootstrap   2.1-4    tool for bootstrapping a Fedora system (like Debian debootstrap)

I use debootstrap to install debian and ubuntu versions in chroots.
I have installed ubuntu 8.04 on debian testing and a bunch of other
combinations and never seen that before.

So why is febootstrap even made available to be installed under debian?

Erik

#576250#25
Date:
2010-04-08 10:31:52 UTC
From:
To:
This is kind of old, I really need to update this to the
latest version.

It does in fact work, but not in all cases.

Rich.

#576250#30
Date:
2010-04-08 10:34:55 UTC
From:
To:
Richard W.M. Jones wrote:

Thanks. I'll try again when the new version is available.

Cheers,
Erik

#576250#35
Date:
2010-06-17 00:04:26 UTC
From:
To:
Hi,

I'm using febootstrap since some week and indeed, I'm able to reproduce the bug.
However, I disagree with the severity serious as it doesn't renders
package unusable.

After the segfault and the febootstrap cache removal failure, the
boostrap is functional.
You can chroot and use it as expected (note: you should cleanup the
cache yourself if you want more space).

Anyway, a new upstream release will be appreciated. If you don't mind,
I could upload a NMU if needed.

Cheers,

Fathi

#576250#38
Date:
2010-06-17 00:04:26 UTC
From:
To:
Hi,

I'm using febootstrap since some week and indeed, I'm able to reproduce the bug.
However, I disagree with the severity serious as it doesn't renders
package unusable.

After the segfault and the febootstrap cache removal failure, the
boostrap is functional.
You can chroot and use it as expected (note: you should cleanup the
cache yourself if you want more space).

Anyway, a new upstream release will be appreciated. If you don't mind,
I could upload a NMU if needed.

Cheers,

Fathi

#576250#43
Date:
2010-06-17 07:19:36 UTC
From:
To:
Yes please.  The version in Debian is ancient.

Rich.

#576250#46
Date:
2010-06-17 07:19:36 UTC
From:
To:
Yes please.  The version in Debian is ancient.

Rich.

#576250#51
Date:
2010-06-17 08:45:02 UTC
From:
To:
Hi,

I have uploaded febootstrap 2.7-1 to Debian.

Unfortunately, this version still segfault:
Complete!
/usr/bin/fakeroot: line 1: 17946 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17947 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17948 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17949 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17950 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17951 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17952 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17953 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17954 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17955 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17956 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17957 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17958 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17959 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17960 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17961 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17962 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17963 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17964 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17965 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17966 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17967 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17968 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17969 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17970 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17971 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17972 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17973 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17974 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17975 Segmentation fault      exit $RESULT
febootstrap-run: problem parsing the command line arguments
febootstrap-run: problem parsing the command line arguments
/usr/bin/febootstrap: line 93: 17980 Segmentation fault
febootstrap-run "$target" -- rm -rf /var/cache/yum/febootstrap-updates

IMHO, the bug should be downgraded to important.
As I said in a previous mail: the boostrap is functional. You can
chroot and use it as expected.

Cheers,

Fathi

#576250#54
Date:
2010-06-17 08:45:02 UTC
From:
To:
Hi,

I have uploaded febootstrap 2.7-1 to Debian.

Unfortunately, this version still segfault:
Complete!
/usr/bin/fakeroot: line 1: 17946 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17947 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17948 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17949 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17950 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17951 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17952 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17953 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17954 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17955 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17956 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17957 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17958 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17959 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17960 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17961 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17962 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17963 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17964 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17965 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17966 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17967 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17968 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17969 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17970 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17971 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17972 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17973 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17974 Segmentation fault      exit $RESULT
/usr/bin/fakeroot: line 1: 17975 Segmentation fault      exit $RESULT
febootstrap-run: problem parsing the command line arguments
febootstrap-run: problem parsing the command line arguments
/usr/bin/febootstrap: line 93: 17980 Segmentation fault
febootstrap-run "$target" -- rm -rf /var/cache/yum/febootstrap-updates

IMHO, the bug should be downgraded to important.
As I said in a previous mail: the boostrap is functional. You can
chroot and use it as expected.

Cheers,

Fathi

#576250#59
Date:
2010-06-17 09:26:22 UTC
From:
To:
These segfaults are almost certainly caused by glibc in the chroot not
matching glibc outside the chroot.  In practice when we do this in
Fedora we ensure that the glibc versions are identical.

This in turn may be caused because we aren't setting the correct
LD_LIBRARY_PATH(s) up inside febootstrap, so that we're in effect
mixing internal parts of the two different glibc versions.  I haven't
really had time to look into this in any detail.

Rich.

#576250#62
Date:
2010-06-17 09:26:22 UTC
From:
To:
These segfaults are almost certainly caused by glibc in the chroot not
matching glibc outside the chroot.  In practice when we do this in
Fedora we ensure that the glibc versions are identical.

This in turn may be caused because we aren't setting the correct
LD_LIBRARY_PATH(s) up inside febootstrap, so that we're in effect
mixing internal parts of the two different glibc versions.  I haven't
really had time to look into this in any detail.

Rich.

#576250#67
Date:
2010-06-19 05:48:43 UTC
From:
To:
Hello Fabo,

I don't recollect now but there were issues with the half baked chroot
environment. That was the justification for the severity.

#576250#72
Date:
2010-07-17 13:47:11 UTC
From:
To:
Hi,
[...]

Do you get those segfaults as well if you run febootstrap with
--no-clean?

If it is just the clean which fails, I agree.  At least in the original
logfile, I do not see any other segfaults.


Michael

#576250#75
Date:
2010-07-17 13:47:11 UTC
From:
To:
Hi,
[...]

Do you get those segfaults as well if you run febootstrap with
--no-clean?

If it is just the clean which fails, I agree.  At least in the original
logfile, I do not see any other segfaults.


Michael

#576250#80
Date:
2010-07-17 17:49:42 UTC
From:
To:
Complete!
/usr/bin/febootstrap: line 93: 15649 Segmentation fault      [
"$clean" = "yes" ]

You know my opinion on the severity of the bug.

Ritesh, could you describe the issues ?

The segfaults seems related to yum cache cleanup and it doesn't seems
a big deal.

Cheers,

Fathi

#576250#83
Date:
2010-07-17 17:49:42 UTC
From:
To:
Complete!
/usr/bin/febootstrap: line 93: 15649 Segmentation fault      [
"$clean" = "yes" ]

You know my opinion on the severity of the bug.

Ritesh, could you describe the issues ?

The segfaults seems related to yum cache cleanup and it doesn't seems
a big deal.

Cheers,

Fathi

#576250#88
Date:
2010-07-17 17:56:05 UTC
From:
To:
severity 576250 normal
thanks

That clears that up.

If there indeed is an issue, please bump the severity back again.


Michael

#576250#93
Date:
2010-07-17 17:56:05 UTC
From:
To:
severity 576250 normal
thanks

That clears that up.

If there indeed is an issue, please bump the severity back again.


Michael

#576250#98
Date:
2010-07-17 18:52:34 UTC
From:
To:
I can't recollect the actual issues now.

If you think it is yum, shouldn't this bug then be re-assigned ?


Ritesh