Bug 10065

Summary:	mondoarchive crashes after identifying GRUB, possibly since recent glibc update
Product:	Mageia	Reporter:	Mark Dawson Butterworth <mageia>
Component:	RPM Packages	Assignee:	Bruno Cornec <bruno>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	Keywords:	Triaged
Version:	2
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	mondo	CVE:
Status comment:
Attachments:	mondoarchive.log

Description Mark Dawson Butterworth 2013-05-11 17:09:29 CEST

I think this may be related to the glibc update that I received via MageiaUpdate this morning. However, it looks like it may be a bug in mondoarchive itself which has been exposed:

Number of media required: UNKNOWN
Done.
Copying Mondo's core files to the scratch directory
Done.
Calling MINDI to create boot+data disks
Your boot loader is GRUB and it boots from /dev/cciss/c0d0
*** glibc detected *** mondoarchive: double free or corruption (!prev): 0x09cc8140 ***
======= Backtrace: =========
/lib/i686/libc.so.6(+0x6cbe2)[0xb75adbe2]
mondoarchive[0x8086986]
mondoarchive[0x804cb59]
mondoarchive[0x805598a]
mondoarchive[0x804a665]
/lib/i686/libc.so.6(__libc_start_main+0xf3)[0xb755a3e3]
mondoarchive[0x804add9]
======= Memory map: ========
08048000-080a0000 r-xp 00000000 68:01 160684     /usr/sbin/mondoarchive
080a0000-080a1000 r--p 00057000 68:01 160684     /usr/sbin/mondoarchive
080a1000-080a2000 rw-p 00058000 68:01 160684     /usr/sbin/mondoarchive
080a2000-080a8000 rw-p 00000000 00:00 0
09cc5000-0a1dc000 rw-p 00000000 00:00 0          [heap]
b73b1000-b73cd000 r-xp 00000000 68:01 520325     /lib/libgcc_s-4.6.3.so.1
b73cd000-b73ce000 rw-p 0001b000 68:01 520325     /lib/libgcc_s-4.6.3.so.1
b73eb000-b73ec000 rw-p 00000000 00:00 0
b73ec000-b7415000 r-xp 00000000 68:01 520201     /lib/i686/libm-2.14.1.so
b7415000-b7416000 r--p 00028000 68:01 520201     /lib/i686/libm-2.14.1.so
b7416000-b7417000 rw-p 00029000 68:01 520201     /lib/i686/libm-2.14.1.so
b7417000-b741a000 r-xp 00000000 68:01 520222     /lib/libdl-2.14.1.so
b741a000-b741b000 r--p 00002000 68:01 520222     /lib/libdl-2.14.1.so
b741b000-b741c000 rw-p 00003000 68:01 520222     /lib/libdl-2.14.1.so
b741c000-b741d000 rw-p 00000000 00:00 0
b741d000-b74f5000 r-xp 00000000 68:01 146064     /usr/lib/libslang.so.2.2.4
b74f5000-b74f8000 r--p 000d7000 68:01 146064     /usr/lib/libslang.so.2.2.4
b74f8000-b7506000 rw-p 000da000 68:01 146064     /usr/lib/libslang.so.2.2.4
b7506000-b7541000 rw-p 00000000 00:00 0
b7541000-b76b8000 r-xp 00000000 68:01 520350     /lib/i686/libc-2.14.1.so
b76b8000-b76b9000 ---p 00177000 68:01 520350     /lib/i686/libc-2.14.1.so
b76b9000-b76bb000 r--p 00177000 68:01 520350     /lib/i686/libc-2.14.1.so
b76bb000-b76bc000 rw-p 00179000 68:01 520350     /lib/i686/libc-2.14.1.so
b76bc000-b76bf000 rw-p 00000000 00:00 0
b76bf000-b76d5000 r-xp 00000000 68:01 520203     /lib/i686/libpthread-2.14.1.so
b76d5000-b76d6000 r--p 00015000 68:01 520203     /lib/i686/libpthread-2.14.1.so
b76d6000-b76d7000 rw-p 00016000 68:01 520203     /lib/i686/libpthread-2.14.1.so
b76d7000-b76d9000 rw-p 00000000 00:00 0
b76d9000-b76ed000 r-xp 00000000 68:01 160517     /usr/lib/libnewt.so.0.52.14
b76ed000-b76ee000 r--p 00014000 68:01 160517     /usr/lib/libnewt.so.0.52.14
b76ee000-b76ef000 rw-p 00015000 68:01 160517     /usr/lib/libnewt.so.0.52.14
b770a000-b770d000 rw-p 00000000 00:00 0
b770d000-b772a000 r-xp 00000000 68:01 520209     /lib/ld-2.14.1.so
b772a000-b772b000 r--p 0001c000 68:01 520209     /lib/ld-2.14.1.so
b772b000-b772c000 rw-p 0001d000 68:01 520209     /lib/ld-2.14.1.so
bfe92000-bfeb4000 rw-p 00000000 00:00 0          [stack]
ffffe000-fffff000 r-xp 00000000 00:00 0          [vdso]
SIGABRT signal received from OS
Abort - probably failed assertion. I'm sleeping for a few seconds so you can rea
Fatal error... MondoRescue is terminating in response to a signal from the OS
---FATALERROR--- MondoRescue is terminating in response to a signal from the OS
If you require technical support, please contact the mailing list.
See http://www.mondorescue.org for details.
The list's members can help you, if you attach that file to your e-mail.
Log file: /var/log/mondoarchive.log
Mondo has aborted.
Execution run ended; result=254
Type 'less /var/log/mondoarchive.log' to see the output log

I've marked this major because I am now unable to back-up, as Mondo is my back-up and disaster recovery solution.

Manuel Hiebel 2013-05-11 23:04:09 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => bruno
Source RPM: (none) => mondo

Comment 1 Bruno Cornec 2013-05-12 02:07:50 CEST

Could you please attach your /var/log/mondoarchive.log file as well.

Status: NEW => ASSIGNED

Comment 2 Mark Dawson Butterworth 2013-05-12 21:19:34 CEST

Created attachment 3950 [details]
mondoarchive.log

Comment 3 Mark Dawson Butterworth 2013-05-23 19:57:50 CEST

Is there any progress on this please?

Comment 4 Mark Dawson Butterworth 2013-05-29 23:36:36 CEST

Severity dropped to normal as this no longer preventing me backing up - the solution is to download the mga2 packages for mondo 3.0.3 and mindi 2.1.5 from http://www.mondorescue.org/.
Once these are included in the Mageia repos then all will be well.

Severity: major => normal

Comment 5 Manuel Hiebel 2013-10-22 12:09:56 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Comment 6 Mark Dawson Butterworth 2013-10-31 23:38:33 CET

Can't test this on Mageia 3 at the moment as Mindi fails for another reason - it looks like it may not be able to handle the symlink from /lib to /usr/lib. I'm just about to raise another bug for this issue and will then cross-reference.

Comment 7 Mark Dawson Butterworth 2013-10-31 23:45:33 CET

Not currently testable due to https://bugs.mageia.org/show_bug.cgi?id=11572

Comment 8 Manuel Hiebel 2013-11-23 16:13:32 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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