Shared object "libintl.so.9" not found, required by "bash"

[Jerry]

Fri, 1 Aug 2014 08:26:26 -0400

I just used "freebsd-update" to update my system to FreeBSD 10.0-RELEASE-p7
from "p3". Now, when I boot up, I am greeted with this friendly message:

Shared object "libintl.so.9" not found, required by "bash"

The file does exist. I rebuilt bash and rebooted the system; however, the
message still appears. I do not see any evidence of a failure by bash, so I
am wondering if this is just a harmless error message.

--
Jerry

[Roland Smith]

On Fri, Aug 01, 2014 at 08:34:37AM -0400, Jerry wrote:
> Fri, 1 Aug 2014 08:26:26 -0400
>
> I just used "freebsd-update" to update my system to FreeBSD 10.0-RELEASE-p7
> from "p3". Now, when I boot up, I am greeted with this friendly message:
>
> Shared object "libintl.so.9" not found, required by "bash"

This means that bash cannot be loaded. But it shouldn't have anything to do
with updating the base system, because libintl.so.9 is part of the
devel/gettext port.

> The file does exist. I rebuilt bash and rebooted the system; however, the
> message still appears.

Are you sure you also *installed* the new bash?
What does `ldd /usr/local/bin/bash` tell you?

> I do not see any evidence of a failure by bash, so I
> am wondering if this is just a harmless error message.

The default shell is tcsh, not bash. If the shell set in your entry in
/etc/passwd would fail to start, you'd get an "access denied" notice from
login(8).


Roland
--
R.F.Smith http://rsmith.home.xs4all.nl/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 5753 3324 1661 B0FE 8D93 FCED 40F6 D5DC A38A 33E0 (keyID: A38A33E0)

[Jerry]

On Fri, 1 Aug 2014 19:58:45 +0200, Roland Smith stated:

>On Fri, Aug 01, 2014 at 08:34:37AM -0400, Jerry wrote:
>> Fri, 1 Aug 2014 08:26:26 -0400
>>
>> I just used "freebsd-update" to update my system to FreeBSD 10.0-RELEASE-p7
>> from "p3". Now, when I boot up, I am greeted with this friendly message:
>>
>> Shared object "libintl.so.9" not found, required by "bash"
>
>This means that bash cannot be loaded. But it shouldn't have anything to do
>with updating the base system, because libintl.so.9 is part of the
>devel/gettext port.
>
>> The file does exist. I rebuilt bash and rebooted the system; however, the
>> message still appears.
>
>Are you sure you also *installed* the new bash?
>What does `ldd /usr/local/bin/bash` tell you?

ldd /usr/local/bin/bash
/usr/local/bin/bash:
libncurses.so.8 => /lib/libncurses.so.8 (0x8008e7000)
libintl.so.9 => /usr/local/lib/libintl.so.9 (0x800b33000)
libc.so.7 => /lib/libc.so.7 (0x800d3c000)

locate libintl.so.9
/usr/local/lib/libintl.so.9

>> I do not see any evidence of a failure by bash, so I
>> am wondering if this is just a harmless error message.

bash --version
GNU bash, version 4.3.18(2)-release (amd64-portbld-freebsd10.0)

echo $0
/usr/local/bin/bash

>The default shell is tcsh, not bash. If the shell set in your entry in
>/etc/passwd would fail to start, you'd get an "access denied" notice from
>login(8).

My default shell is Bash.

--
Jerry
_______________________________________________
freebsd-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"

[Roland Smith]

On Fri, Aug 01, 2014 at 03:24:13PM -0400, Jerry wrote:
> On Fri, 1 Aug 2014 19:58:45 +0200, Roland Smith stated:
>
> >On Fri, Aug 01, 2014 at 08:34:37AM -0400, Jerry wrote:
> >> Fri, 1 Aug 2014 08:26:26 -0400
> >>
> >> I just used "freebsd-update" to update my system to FreeBSD 10.0-RELEASE-p7
> >> from "p3". Now, when I boot up, I am greeted with this friendly message:
> >>
> >> Shared object "libintl.so.9" not found, required by "bash"
> >
> >This means that bash cannot be loaded. But it shouldn't have anything to do
> >with updating the base system, because libintl.so.9 is part of the
> >devel/gettext port.
> >
> >> The file does exist. I rebuilt bash and rebooted the system; however, the
> >> message still appears.
> >
> >Are you sure you also *installed* the new bash?
> >What does `ldd /usr/local/bin/bash` tell you?
>
> ldd /usr/local/bin/bash
> /usr/local/bin/bash:
> libncurses.so.8 => /lib/libncurses.so.8 (0x8008e7000)
> libintl.so.9 => /usr/local/lib/libintl.so.9 (0x800b33000)
> libc.so.7 => /lib/libc.so.7 (0x800d3c000)
>
> locate libintl.so.9
> /usr/local/lib/libintl.so.9
>
> >> I do not see any evidence of a failure by bash, so I
> >> am wondering if this is just a harmless error message.

Everything seems to be OK. Weird.

The only causes I can think of is that the system tries to start bash before
ldconfig(8) is run to update the hints file /var/run/ld-elf.so.hints. Or that
the hints file is inaccessible for some reason.

Since the dynamic linker only looks in /lib and /usr/lib by default, that
would make the linking with a library in /usr/local/lib fail.

But how that could happen I don't know.

[unixfr...@gmail.com]

Happened here on 4 VPS using 9.3-RELEASE-p2
there are some program using bash shell login by remote and all went *poof*
with the error message pic I attached together with ldd output.
1. I really don't understand why bash now need to use libintl.so.9
(gettext's lib), can't see any announce for that too.
2. It supposed to be linked like the below:
$ uname -m
i386
$ ldd /usr/local/bin/bash
/usr/local/bin/bash:
libncurses.so.8 => /lib/libncurses.so.8 (0x2811c000)
libintl.so.9 => /usr/local/lib/libintl.so.9 (0x2815c000)
libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x28165000)
libc.so.7 => /lib/libc.so.7 (0x2825d000)

3. funny thing is all my 9.3 release freebsd amd is having this bug now and
bash user can't login. Yet 9.1 but in intel x32 wasn't occured

rgds / @unixfreaxjp