Zenn
📝

【Linux】「libnsl.so.1」が存在しない場合の対処法とは？

2024/05/08に公開
Linux
yum
RHEL
systemwalker
tech

はじめに

Systemwalker Operation Managerを立ち上げる際に、以下のエラーが表示されたため対処方法を書く。

エラーメッセージ
/opt/FJSVftlo/bin/toolaudito: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory

環境

  • RHEL9.2
$ cat /etc/redhat-release
Red Hat Enterprise Linux release 9.2 (Plow)
$

  • RHELのリポジトリサーバが存在し、yumでパッケージをインストールできる状態

  • Systemwalker Operation Manager Standard Edition V17.0.1

# /opt/FJSVftlo/bin/swpkginfo
*************************************************
Systemwalker Operation Manager Information
*************************************************
PRODUCTNAME   : Systemwalker Operation Manager Standard Edition (64bit)
VERSION       : V17.0.1
VENDER        : COPYRIGHT FUJITSU LIMITED 1995-2022
CODE          : UTF-8
INSTALLDATE   : 2024.05.01
PLATFORM      : Linux
INSTALLCLASS  : Server
INSTALLPATH   : /opt
                /etc/opt
                /var/opt
#

事象

Systemwalker Operation Managerを立ち上げる際に、「libnsl.so.1」が存在しない旨表示される。

# /opt/systemwalker/bin/soperationmgr
/opt/FJSVftlo/bin/toolaudito: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory
/opt/systemwalker/bin/soperationmgr start...
component start : sh /opt/systemwalker/bin/rc.mpfwsec start
component started normally:  /opt/systemwalker/bin/rc.mpfwsec
component start : sh /opt/FJSVJMCMN/etc/rc0.d/stsjmcmn
component has been started : /opt/FJSVJMCMN/etc/rc3.d/start_jmcmn
component start : sh /opt/FJSVjmcal/bin/S99JMCAL
/opt/FJSVjmcal/bin/f3crhcs2: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory
component started normally:  /opt/FJSVjmcal/bin/S99JMCAL
component start : sh /etc/opt/FJSVMJS/etc/rc3.d/S99MJS
/usr/lib/mjes/mjsdaemon: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory
component did not start:  /etc/opt/FJSVMJS/etc/rc3.d/S99MJS
soperationmgr: ERROR: Failed to start daemons.
/opt/FJSVftlo/bin/toolaudito: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory
#

対処

libnslパッケージをインストールする。

コマンド
yum install libnsl

パッケージインストール後に再度Systemwalker Operation Managerを起動すると、無事起動に成功する。

# /opt/systemwalker/bin/soperationmgr
/opt/systemwalker/bin/soperationmgr start...
component start : sh /opt/systemwalker/bin/rc.mpfwsec start
component started normally:  /opt/systemwalker/bin/rc.mpfwsec
component start : sh /opt/FJSVJMCMN/etc/rc0.d/stsjmcmn
component has been started : /opt/FJSVJMCMN/etc/rc3.d/start_jmcmn
component start : sh /opt/FJSVjmcal/bin/S99JMCAL
component started normally:  /opt/FJSVjmcal/bin/S99JMCAL
component start : sh /etc/opt/FJSVMJS/etc/rc3.d/S99MJS
component started normally:  /etc/opt/FJSVMJS/etc/rc3.d/S99MJS
component start : sh /opt/FJSVJOBSC/etc/rc0.d/stsjobsc
component start : sh /opt/FJSVJOBSC/etc/rc3.d/start_jobs
component start : sh /opt/FJSVJOBSC/etc/rc0.d/stsjobsc
component started normally:  /opt/FJSVJOBSC/etc/rc3.d/start_jobs
component start : sh /opt/FJSVftlo/pmon/bin/strmppmon.sh
component started normally:  /opt/FJSVftlo/pmon/bin/strmppmon.sh
/opt/systemwalker/bin/soperationmgr normal end.
#

備考

Systemwalker公式ナレッジに本エラーの対処として、elfutilsパッケージが必要と記載がある。

今回は、elfutilsパッケージは既にインストールされている前提での記事になる。

# rpm -qa | grep elfutils
elfutils-libelf-0.188-3.el9.x86_64
elfutils-libelf-devel-0.188-3.el9.x86_64
elfutils-default-yama-scope-0.188-3.el9.noarch
elfutils-libs-0.188-3.el9.x86_64
elfutils-debuginfod-client-0.188-3.el9.x86_64
elfutils-0.188-3.el9.x86_64
elfutils-devel-0.188-3.el9.x86_64
#

参考

https://www.ibm.com/docs/ja/capm?topic=systems-preinstallation-linux

https://access.redhat.com/documentation/ja-jp/red_hat_enterprise_linux/9/html-single/package_manifest/index

https://www.fujitsu.com/jp/about/faq/sfw-systemwalker/operationmanager/14011.html

Discussion