Opened 3 years ago

Closed 18 months ago

#754 closed defect (worksforme)

newt problem in mondorestore at mondorescue.iso boot

Reported by: vicgat Owned by: bruno
Priority: normal Milestone: 3.0.5
Component: mondo Version: 3.0.4
Severity: normal Keywords: libnewt mondorestore
Cc:

Description

If I run mondorestore in the SLES 11 SP1, I don't get any newt error, mondorestore starts well and display the interactive (GUI) mode.

# yum list installed | grep -iE "mindi|mondo"
mindi.x86_64          2.1.7-1.sles11                installed
mindi-busybox.x86_64  1.18.5-3.sles11               installed
mondo.x86_64          3.0.4-1.sles11                installed

# ldd /usr/sbin/mondorestore
        linux-vdso.so.1 =>  (0x00007fffcadff000)
        libnewt.so.0.52 => /usr/lib64/libnewt.so.0.52 (0x00007f79f33d9000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f79f31bb000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f79f2e5d000)
        libslang.so.2 => /usr/lib64/libslang.so.2 (0x00007f79f2b39000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f79f3622000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f79f2934000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f79f26de000)

I did a mondoarchive on that machine (using NFS).

I booted from the mondorescue.iso generated, in interactive mode, and when it executes mondorestore I got a newt error :

mondorestore: error while loading shared libraries: libnewt.so.0.52: cannot open shared object file: No such file or directory

The solution was to boot with "interactive textonly", then mondorestore worked well.

Attachments (8)

libnewt pb interactive.jpg (154.1 KB) - added by vicgat 3 years ago.
interactive mondorestore libnewt error
libnewt pb expert.jpg (131.2 KB) - added by vicgat 3 years ago.
expert mode mondorestore libnewt error
mindi.log.gz (30.9 KB) - added by vicgat 3 years ago.
mondoarchive.log.gz (39.5 KB) - added by vicgat 3 years ago.
mondorestore.log (117.1 KB) - added by vicgat 3 years ago.
mondorestore ok only in mode interactive textonly
mondorestore libnewt ok.gif (46.6 KB) - added by vicgat 3 years ago.
Today it's ok, no mondorestore libnewt problem
no libnewt in lib64.gif (58.4 KB) - added by vicgat 3 years ago.
no libnewt in this lib64 too.gif (54.5 KB) - added by vicgat 3 years ago.

Download all attachments as: .zip

Change History (15)

Changed 3 years ago by vicgat

interactive mondorestore libnewt error

Changed 3 years ago by vicgat

expert mode mondorestore libnewt error

Changed 3 years ago by vicgat

Changed 3 years ago by vicgat

Changed 3 years ago by vicgat

mondorestore ok only in mode interactive textonly

comment:1 Changed 3 years ago by vicgat

Note : The mondorestore.log attached here is the one of mode "interactive textonly".

comment:2 Changed 3 years ago by vicgat

Note : I'm not sure if "libnewt pb expert.jpg" screenshot was a test in expert mode or in interactive mode...

comment:3 Changed 3 years ago by bruno

  • Status changed from new to assigned

Seems similar to #653 at first approach, even if on a different distro.

comment:4 Changed 3 years ago by bruno

Could you try at restore time to find the library ? What reports:

find / -name libnewt.so.0.52

And do you have /usr/lib64/libnewt.so.0.52.10 as well ?

For sure they are not part of the initrd.

Also what gives:

# mindi --locatedeps /usr/sbin/mondorestore
# ls -al `mindi --locatedeps /usr/sbin/mondorestore`

I don't understand yet why they are not included, but we'll find out !

comment:5 Changed 3 years ago by vicgat

I booted again to the same mondorescue.iso.

Today I get no libnewt problem when I start mondorestore, nor with interactive textonly, nor with interactive mode.

I attach the results of the test at restore time.

Changed 3 years ago by vicgat

Today it's ok, no mondorestore libnewt problem

comment:6 Changed 3 years ago by vicgat

I checked in mondorescue.iso, I didn't found any libnewt (see attachments).

Changed 3 years ago by vicgat

Changed 3 years ago by vicgat

comment:7 Changed 18 months ago by bruno

  • Resolution set to worksforme
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.