Red Hat Bugzilla – Bug 594034
missing shared libraries in rescue mode for shutdown
Last modified: 2013-07-04 08:50:06 EDT
Description of problem: Running shutdown in rescue mode ends with error complaining about missing shared libraries. Version-Release number of selected component (if applicable): RHEL6.0-20100512.0 x86_64 Server anaconda-13.21.39-1.el6.x86_64 How reproducible: always Steps to Reproduce: 1. start rescue mode 2. start shell 3. run shutdown Actual results: bash-4.1# shutdown shutdown: error while loading shared libraries: libnih.so.1: cannot open shared object file: no such file or directory Expected results: shutdown should work or shouldn't be present Additional info:
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion.
Ok, I've found now, that this happens only if previously installed system is mounted into /mnt/sysimage (without manual chroot-ing).
The problem is in PATH variable, it contains /mnt/sysimage/bin, /mnt/sysimage/sbin, /mnt/sysimage/usr/bin/ ...
The problem was with library paths on 64 bit architectures, fixed in version anaconda-13.21.48-1
With anaconda-13.21.48 there's no error message about the missing shared library. However the system will not shutdown: In the rescue shell type: shutdown -h now - nothing happens. Martin, is this related or a separate bug?
(In reply to comment #6) > With anaconda-13.21.48 there's no error message about the missing shared > library. However the system will not shutdown: > > In the rescue shell type: shutdown -h now - nothing happens. > Discussed with Martin on IRC and filed as bug #601607. Moving this one to VERIFIED.
Red Hat Enterprise Linux Beta 2 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you.