Hi All;

I have a issue when I run sas-linux on my linux redhat server after installed glibc.i686, how can I fix this issue, thank you.

[root@cark2nnobkup-media9 ~]# cd /tmp/sas-linux/
[root@cark2nnobkup-media9 sas-linux]# ./sas-linux -t 192.168.168.12 -b 20
./sas-linux: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
[root@cark2nnobkup-media9 sas-linux]#



[root@cark2nnobkup-media9 sas-linux]# yum -y install glibc.i686
Loaded plugins: product-id, search-disabled-repos, subscription-manager
Repodata is over 2 weeks old. Install yum-cron? Or run: yum makecache fast
rhel-7-server-rpms | 2.0 kB 00:00:00
Resolving Dependencies
--> Running transaction check
---> Package glibc.i686 0:2.17-157.el7_3.1 will be installed
--> Processing Dependency: glibc-common = 2.17-157.el7_3.1 for package: glibc-2.17-157.el7_3.1.i686
--> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.17-157.el7_3.1.i686
--> Processing Dependency: libfreebl3.so for package: glibc-2.17-157.el7_3.1.i686
--> Running transaction check
---> Package glibc-common.x86_64 0:2.17-105.el7 will be updated
--> Processing Dependency: glibc-common = 2.17-105.el7 for package: glibc-2.17-105.el7.x86_64
---> Package glibc-common.x86_64 0:2.17-157.el7_3.1 will be an update
---> Package nss-softokn-freebl.i686 0:3.16.2.3-14.4.el7 will be installed
--> Running transaction check
---> Package glibc.x86_64 0:2.17-105.el7 will be updated
---> Package glibc.x86_64 0:2.17-157.el7_3.1 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

==================================================================================================== ===================================================================================================
Package Arch Version Repository Size
==================================================================================================== ===================================================================================================
Installing:
glibc i686 2.17-157.el7_3.1 rhel-7-server-rpms 4.2 M
Installing for dependencies:
nss-softokn-freebl i686 3.16.2.3-14.4.el7 rhel-7-server-rpms 188 k
Updating for dependencies:
glibc x86_64 2.17-157.el7_3.1 rhel-7-server-rpms 3.6 M
glibc-common x86_64 2.17-157.el7_3.1 rhel-7-server-rpms 11 M

Transaction Summary
==================================================================================================== ===================================================================================================
Install 1 Package (+1 Dependent package)
Upgrade ( 2 Dependent packages)

Total download size: 19 M
Downloading packages:
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
(1/4): glibc-2.17-157.el7_3.1.i686.rpm | 4.2 MB 00:00:00
(2/4): glibc-2.17-157.el7_3.1.x86_64.rpm | 3.6 MB 00:00:00
(3/4): nss-softokn-freebl-3.16.2.3-14.4.el7.i686.rpm | 188 kB 00:00:00
(4/4): glibc-common-2.17-157.el7_3.1.x86_64.rpm | 11 MB 00:00:00
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 12 MB/s | 19 MB 00:00:01
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Updating : glibc-2.17-157.el7_3.1.x86_64 1/6
warning: /etc/nsswitch.conf created as /etc/nsswitch.conf.rpmnew
Updating : glibc-common-2.17-157.el7_3.1.x86_64 2/6
Installing : nss-softokn-freebl-3.16.2.3-14.4.el7.i686 3/6
Installing : glibc-2.17-157.el7_3.1.i686 4/6
Cleanup : glibc-2.17-105.el7.x86_64 5/6
Cleanup : glibc-common-2.17-105.el7.x86_64 6/6
Verifying : glibc-common-2.17-157.el7_3.1.x86_64 1/6
Verifying : nss-softokn-freebl-3.16.2.3-14.4.el7.i686 2/6
Verifying : glibc-2.17-157.el7_3.1.x86_64 3/6
Verifying : glibc-2.17-157.el7_3.1.i686 4/6
Verifying : glibc-common-2.17-105.el7.x86_64 5/6
Verifying : glibc-2.17-105.el7.x86_64 6/6

Installed:
glibc.i686 0:2.17-157.el7_3.1

Dependency Installed:
nss-softokn-freebl.i686 0:3.16.2.3-14.4.el7

Dependency Updated:
glibc.x86_64 0:2.17-157.el7_3.1 glibc-common.x86_64 0:2.17-157.el7_3.1

Complete!
[root@cark2nnobkup-media9 sas-linux]#

Welcome to LQ.

If glibc.i686 is required for your application, libstdc++.i686 is probably required too:

# yum install libstdc++.i686

1 members found this post helpful.

I did , but still has same error.

[root@cark2nnobkup-media9 ~]# yum install libstdc++.i686
Loaded plugins: product-id, search-disabled-repos, subscription-manager
rhel-7-server-rpms | 2.0 kB 00:00:00
Resolving Dependencies
--> Running transaction check
---> Package libstdc++.i686 0:4.8.5-11.el7 will be installed
--> Processing Dependency: libgcc_s.so.1(GLIBC_2.0) for package: libstdc++-4.8.5-11.el7.i686
--> Processing Dependency: libgcc_s.so.1(GCC_4.2.0) for package: libstdc++-4.8.5-11.el7.i686
--> Processing Dependency: libgcc_s.so.1(GCC_3.3) for package: libstdc++-4.8.5-11.el7.i686
--> Processing Dependency: libgcc_s.so.1(GCC_3.0) for package: libstdc++-4.8.5-11.el7.i686
--> Processing Dependency: libgcc_s.so.1 for package: libstdc++-4.8.5-11.el7.i686
--> Running transaction check
---> Package libgcc.x86_64 0:4.8.5-4.el7 will be updated
---> Package libgcc.i686 0:4.8.5-11.el7 will be installed
---> Package libgcc.x86_64 0:4.8.5-11.el7 will be an update
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:

1. You have an upgrade for libstdc++ which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libstdc++ of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude libstdc++.otherarch ... this should give you an error
message showing the root cause of the problem.

2. You have multiple architectures of libstdc++ installed, but
yum can only see an upgrade for one of those architectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.

3. You have duplicate versions of libstdc++ installed already.
You can use "yum check" to get yum show these errors.

...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).

Protected multilib versions: libstdc++-4.8.5-11.el7.i686 != libstdc++-4.8.5-4.el7.x86_64
[root@cark2nnobkup-media9 ~]# ./sas-linux -t 192.168.168.12 -b 20
-bash: ./sas-linux: No such file or directory
[root@cark2nnobkup-media9 ~]# cd /tmp/sas-linux/
[root@cark2nnobkup-media9 sas-linux]# ./sas-linux -t 192.168.168.12 -b 20
./sas-linux: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
[root@cark2nnobkup-media9 sas-linux]#

[root@cark2nnobkup-media9 sas-linux]# yum check
Loaded plugins: product-id, search-disabled-repos, subscription-manager
ipa-admintools-4.4.0-14.el7_3.7.noarch has installed conflicts freeipa-admintools: ipa-admintools-4.4.0-14.el7_3.7.noarch
ipa-client-4.4.0-14.el7_3.7.x86_64 has installed conflicts freeipa-client: ipa-client-4.4.0-14.el7_3.7.x86_64
ipa-client-common-4.4.0-14.el7_3.7.noarch has installed conflicts freeipa-client-common: ipa-client-common-4.4.0-14.el7_3.7.noarch
ipa-common-4.4.0-14.el7_3.7.noarch has installed conflicts freeipa-common: ipa-common-4.4.0-14.el7_3.7.noarch
ipa-python-compat-4.4.0-14.el7_3.7.noarch has installed conflicts freeipa-python-compat: ipa-python-compat-4.4.0-14.el7_3.7.noarch
ipa-server-4.4.0-14.el7_3.7.x86_64 has installed conflicts freeipa-server: ipa-server-4.4.0-14.el7_3.7.x86_64
ipa-server-common-4.4.0-14.el7_3.7.noarch has installed conflicts freeipa-server-common: ipa-server-common-4.4.0-14.el7_3.7.noarch
ipa-server-dns-4.4.0-14.el7_3.7.noarch has installed conflicts freeipa-server-dns: ipa-server-dns-4.4.0-14.el7_3.7.noarch
Error: check all
[root@cark2nnobkup-media9 sas-linux]#

anyone can help me to fix that ? Thank you.

If the binary is dynamically linked you can probably confirm that the loader can't find the library by doing
And if the installed library is compatible this may work:
If nothing works you may be able to find out why by running strace:
(and see where it tries to find the library)

I am not sure why it cannot find libstdc++.so.6 , I beleive, I already installed it

[root@cark2nnobkup-media9 sas-linux]# ldd sas-linux
linux-gate.so.1 => (0xf76e1000)
libdl.so.2 => /lib/libdl.so.2 (0xf76d2000)
libpthread.so.0 => /lib/libpthread.so.0 (0xf76b7000)
librt.so.1 => /lib/librt.so.1 (0xf76ae000)
libstdc++.so.6 => not found
libm.so.6 => /lib/libm.so.6 (0xf766a000)
libgcc_s.so.1 => not found
libc.so.6 => /lib/libc.so.6 (0xf74ac000)
/lib/ld-linux.so.2 (0xf76e2000)
[root@cark2nnobkup-media9 sas-linux]# ./sas-linux
./sas-linux: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

I installed libstdc++.so.6 but get error, how can I fix it? I am not linux exppert

[root@cark2nnobkup-media9 ~]# yum install libstdc++.so.6
Loaded plugins: product-id, search-disabled-repos, subscription-manager
rhel-7-server-rpms | 2.0 kB 00:00:00
Resolving Dependencies
--> Running transaction check
---> Package libstdc++.i686 0:4.8.5-11.el7 will be installed
--> Processing Dependency: libgcc_s.so.1(GLIBC_2.0) for package: libstdc++-4.8.5-11.el7.i686
--> Processing Dependency: libgcc_s.so.1(GCC_4.2.0) for package: libstdc++-4.8.5-11.el7.i686
--> Processing Dependency: libgcc_s.so.1(GCC_3.3) for package: libstdc++-4.8.5-11.el7.i686
--> Processing Dependency: libgcc_s.so.1(GCC_3.0) for package: libstdc++-4.8.5-11.el7.i686
--> Processing Dependency: libgcc_s.so.1 for package: libstdc++-4.8.5-11.el7.i686
--> Running transaction check
---> Package libgcc.x86_64 0:4.8.5-4.el7 will be updated
---> Package libgcc.i686 0:4.8.5-11.el7 will be installed
---> Package libgcc.x86_64 0:4.8.5-11.el7 will be an update
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:

1. You have an upgrade for libstdc++ which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libstdc++ of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude libstdc++.otherarch ... this should give you an error
message showing the root cause of the problem.

2. You have multiple architectures of libstdc++ installed, but
yum can only see an upgrade for one of those architectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.

3. You have duplicate versions of libstdc++ installed already.
You can use "yum check" to get yum show these errors.

...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).

Protected multilib versions: libstdc++-4.8.5-11.el7.i686 != libstdc++-4.8.5-4.el7.x86_64
[root@cark2nnobkup-media9 ~]# cd /usr/openv/netbackup/sas-linux/
[root@cark2nnobkup-media9 sas-linux]# ldd sas-linux
linux-gate.so.1 => (0xf770f000)
libdl.so.2 => /lib/libdl.so.2 (0xf7700000)
libpthread.so.0 => /lib/libpthread.so.0 (0xf76e5000)
librt.so.1 => /lib/librt.so.1 (0xf76dc000)
libstdc++.so.6 => not found
libm.so.6 => /lib/libm.so.6 (0xf7698000)
libgcc_s.so.1 => not found
libc.so.6 => /lib/libc.so.6 (0xf74da000)
/lib/ld-linux.so.2 (0xf7710000)
[root@cark2nnobkup-media9 sas-linux]#

this IS redhat right ?
have you opened a support ticket ?
you ARE paying for that required support ? right ?
you might want to use it


to fix this there is a well known shortcut that will install gcc and stc
just double check the name with a yum search
that should install ALL the dependencies including stc6

you also might want to sync your install with the reops

No, you have not installed the library, see the Error above. It looks like the 64-bit version is being kept at 4.8.5-4.
So you may have to either:
first to get the proper 64-bit level, then install the 32-bit version, or try

wrong glibc.

after ran yum update and yum install libstdc++-4.8.5-4.el7.i686 but I still have issue

[root@cark2nnobkup-media9 sas-linux]# yum install libstdc++-4.8.5-4.el7.i686
Loaded plugins: product-id, search-disabled-repos, subscription-manager
rhel-7-server-rpms | 2.0 kB 00:00:00
Resolving Dependencies
--> Running transaction check
---> Package libstdc++.i686 0:4.8.5-4.el7 will be installed
--> Processing Dependency: libgcc_s.so.1(GLIBC_2.0) for package: libstdc++-4.8.5-4.el7.i686
--> Processing Dependency: libgcc_s.so.1(GCC_4.2.0) for package: libstdc++-4.8.5-4.el7.i686
--> Processing Dependency: libgcc_s.so.1(GCC_3.3) for package: libstdc++-4.8.5-4.el7.i686
--> Processing Dependency: libgcc_s.so.1(GCC_3.0) for package: libstdc++-4.8.5-4.el7.i686
--> Processing Dependency: libgcc_s.so.1 for package: libstdc++-4.8.5-4.el7.i686
--> Running transaction check
---> Package libgcc.i686 0:4.8.5-11.el7 will be installed
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:

1. You have an upgrade for libstdc++ which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libstdc++ of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude libstdc++.otherarch ... this should give you an error
message showing the root cause of the problem.

2. You have multiple architectures of libstdc++ installed, but
yum can only see an upgrade for one of those architectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.

3. You have duplicate versions of libstdc++ installed already.
You can use "yum check" to get yum show these errors.

...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).

Protected multilib versions: libstdc++-4.8.5-4.el7.i686 != libstdc++-4.8.5-11.el7.x86_64
[root@cark2nnobkup-media9 sas-linux]#