【标题描述】能够简要描述问题:说明什么场景下,做了什么操作,出现什么问题(尽量使用正向表达方式)
系统架构AARCH64
系统版本:
[root@kunlun-rk3588 build]# rpm -qa | grep -i iSulad
iSulad-2.0.18-17.oe2203.aarch64
[root@kunlun-rk3588 build]# rpm -qa | grep -i clibcni
clibcni-2.0.7-8.oe2203.aarch64
clibcni-devel-2.0.7-8.oe2203.aarch64
一、缺陷信息
[root@kunlun-rk3588 iSulad]# journalctl -f -u isulad
Apr 22 06:28:01 kunlun-rk3588 systemd[1]: Starting iSulad Application Container Engine...
Apr 22 06:28:01 kunlun-rk3588 isulad[1288]: /usr/bin/isulad: symbol lookup error: /usr/lib64/libclibcni.so: undefined symbol: free_cni_version
Apr 22 06:28:01 kunlun-rk3588 systemd[1]: isulad.service: Main process exited, code=exited, status=127/n/a
Apr 22 06:28:01 kunlun-rk3588 systemd[1]: isulad.service: Failed with result 'exit-code'.
Apr 22 06:28:01 kunlun-rk3588 systemd[1]: Failed to start iSulad Application Container Engine.
Apr 22 06:28:01 kunlun-rk3588 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 3.
Apr 22 06:28:01 kunlun-rk3588 systemd[1]: Stopped iSulad Application Container Engine.
Apr 22 06:28:01 kunlun-rk3588 systemd[1]: isulad.service: Start request repeated too quickly.
Apr 22 06:28:01 kunlun-rk3588 systemd[1]: isulad.service: Failed with result 'exit-code'.
Apr 22 06:28:01 kunlun-rk3588 systemd[1]: Failed to start iSulad Application Container Engine.
缺陷简述:
]# isulad -l DEBUG
isulad: symbol lookup error: /usr/lib64/libclibcni.so: undefined symbol: free_cni_version
操作:
eular:openEuler-22.03-LTS
isulad:yum install -y iSulad
[root@kunlun-rk3588 c-ares]# isulad --version
isulad: symbol lookup error: /usr/lib64/libclibcni.so: undefined symbol: free_cni_version
[root@kunlun-rk3588 depend]# yum install -y iSulad
Last metadata expiration check: 0:38:11 ago on Tue Apr 23 02:58:16 2024.
Dependencies resolved.
Package Architecture Version Repository Size
Installing:
iSulad aarch64 2.0.18-17.oe2203 update 1.9 M
Transaction Summary
Install 1 Package
Total download size: 1.9 M
Installed size: 11 M
Downloading Packages:
iSulad-2.0.18-17.oe2203.aarch64.rpm 1.5 MB/s | 1.9 MB 00:01
Total 964 kB/s | 1.9 MB 00:02
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Running scriptlet: iSulad-2.0.18-17.oe2203.aarch64 1/1
Installing : iSulad-2.0.18-17.oe2203.aarch64 1/1
Running scriptlet: iSulad-2.0.18-17.oe2203.aarch64 1/1
Created symlink /etc/systemd/system/multi-user.target.wants/isulad.service → /usr/lib/systemd/system/isulad.service.
Job for isulad.service failed because the control process exited with error code.
See "systemctl status isulad.service" and "journalctl -xeu isulad.service" for details.
Verifying : iSulad-2.0.18-17.oe2203.aarch64 1/1
Installed:
iSulad-2.0.18-17.oe2203.aarch64
Complete!
[root@kunlun-rk3588 depend]# systemctl status isulad.service
× isulad.service - iSulad Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/isulad.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2024-04-23 03:36:31 UTC; 8s ago
Process: 79711 ExecStart=/usr/bin/isulad $OPTIONS (code=exited, status=127)
Main PID: 79711 (code=exited, status=127)
Apr 23 03:36:31 kunlun-rk3588 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 5.
Apr 23 03:36:31 kunlun-rk3588 systemd[1]: Stopped iSulad Application Container Engine.
Apr 23 03:36:31 kunlun-rk3588 systemd[1]: isulad.service: Start request repeated too quickly.
Apr 23 03:36:31 kunlun-rk3588 systemd[1]: isulad.service: Failed with result 'exit-code'.
Apr 23 03:36:31 kunlun-rk3588 systemd[1]: Failed to start iSulad Application Container Engine.
[root@kunlun-rk3588 depend]# journalctl -f -u isulad
Apr 23 03:36:31 kunlun-rk3588 systemd[1]: Starting iSulad Application Container Engine...
Apr 23 03:36:31 kunlun-rk3588 isulad[79711]: /usr/bin/isulad: symbol lookup error: /usr/lib64/libclibcni.so: undefined symbol: free_cni_version
Apr 23 03:36:31 kunlun-rk3588 systemd[1]: isulad.service: Main process exited, code=exited, status=127/n/a
Apr 23 03:36:31 kunlun-rk3588 systemd[1]: isulad.service: Failed with result 'exit-code'.
Apr 23 03:36:31 kunlun-rk3588 systemd[1]: Failed to start iSulad Application Container Engine.
Apr 23 03:36:31 kunlun-rk3588 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 5.
Apr 23 03:36:31 kunlun-rk3588 systemd[1]: Stopped iSulad Application Container Engine.
Apr 23 03:36:31 kunlun-rk3588 systemd[1]: isulad.service: Start request repeated too quickly.
Apr 23 03:36:31 kunlun-rk3588 systemd[1]: isulad.service: Failed with result 'exit-code'.
Apr 23 03:36:31 kunlun-rk3588 systemd[1]: Failed to start iSulad Application Container Engine.
Hi chiminghao777, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: iSulad, and any of the maintainers: @haomintsai , @JingWoo , @lifeng_isula , @xuxuepeng , @zhongtao , @haozi007 , @jingxiaolu
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。
补充一下系统版本、isulad版本、clibcni版本信息
麻烦你看一下是版本不对吗?
Apr 23 03:36:31 kunlun-rk3588 isulad[79711]: /usr/bin/isulad: symbol lookup error: /usr/lib64/libclibcni.so: undefined symbol: free_cni_version
[root@kunlun-rk3588 lxc-4.0.3]# yum provides /usr/lib64/libclibcni.so
Last metadata expiration check: 0:09:06 ago on Wed Apr 24 03:23:35 2024.
clibcni-2.0.7-1.oe2203.aarch64 : CNI - the Container Network Interface
Repo : OS
Matched from:
Filename : /usr/lib64/libclibcni.so
clibcni-2.0.7-1.oe2203.aarch64 : CNI - the Container Network Interface
Repo : everything
Matched from:
Filename : /usr/lib64/libclibcni.so
clibcni-2.0.7-2.oe2203.aarch64 : CNI - the Container Network Interface
Repo : update
Matched from:
Filename : /usr/lib64/libclibcni.so
clibcni-2.0.7-8.oe2203.aarch64 : CNI - the Container Network Interface
Repo :
Matched from:
Filename : /usr/lib64/libclibcni.so
clibcni-2.0.7-8.oe2203.aarch64 : CNI - the Container Network Interface
Repo : update
Matched from:
Filename : /usr/lib64/libclibcni.so
@zhongtao
lcr的版本不对,需要更新lcr
你好请问要更新到那些版本呢?
[root@kunlun-rk3588 lxc-4.0.3]# yum list installed | grep lcr
lcr.aarch64 2.0.9-8.oe2203 @openEuler-update
lcr-devel.aarch64 2.0.9-8.oe2203 @JohnnyStrong
[root@kunlun-rk3588 lxc-4.0.3]# yum list installed | grep lxc
lxc.aarch64 4.0.3-2022102417.oe2203 @openEuler-update
lxc-devel.aarch64 4.0.3-2022102417.oe2203 @ update
lxc-libs.aarch64 4.0.3-2022102417.oe2203 @ openEuler-update
lxcfs.aarch64 4.0.11-2.oe2203 @ openEuler
[root@kunlun-rk3588 lxc-4.0.3]# yum list installed | grep iSulad
iSulad.aarch64 2.0.18-17.oe2203 @ update
这里的版本不对吗? @jake
Installing:
iSulad aarch64 2.0.18-17.oe2203 update 1.9 M
Installing dependencies:
clibcni aarch64 2.0.7-8.oe2203 update 39 k
lcr aarch64 2.0.9-8.oe2203 update 329 k
Install 3 Packages
Total download size: 2.3 M
Installed size: 13 M
Is this ok [y/N]:
update之后应该可以了吧
安装之后没有symbol lookup error: /usr/lib64/libclibcni.so: undefined symbol: free_cni_version
但是service还是起不来
Installing:
iSulad aarch64 2.0.18-17.oe2203 update 1.9 M
Installing dependencies:
clibcni aarch64 2.0.7-8.oe2203 update 39 k
lcr aarch64 2.0.9-8.oe2203 update 329 k
Install 3 Packages
Total 92 kB/s | 2.3 MB 00:25
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Running scriptlet: lcr-2.0.9-8.oe2203.aarch64 1/3
Installing : lcr-2.0.9-8.oe2203.aarch64 1/3
Running scriptlet: lcr-2.0.9-8.oe2203.aarch64 1/3
Running scriptlet: clibcni-2.0.7-8.oe2203.aarch64 2/3
Installing : clibcni-2.0.7-8.oe2203.aarch64 2/3
Running scriptlet: clibcni-2.0.7-8.oe2203.aarch64 2/3
Running scriptlet: iSulad-2.0.18-17.oe2203.aarch64 3/3
Installing : iSulad-2.0.18-17.oe2203.aarch64 3/3
Running scriptlet: iSulad-2.0.18-17.oe2203.aarch64 3/3
Created symlink /etc/systemd/system/multi-user.target.wants/isulad.service → /usr/lib/systemd/system/isulad.service.
Job for isulad.service failed because the control process exited with error code.
See "systemctl status isulad.service" and "journalctl -xeu isulad.service" for details.
Verifying : clibcni-2.0.7-8.oe2203.aarch64 1/3
Verifying : iSulad-2.0.18-17.oe2203.aarch64 2/3
Verifying : lcr-2.0.9-8.oe2203.aarch64 3/3
Installed:
clibcni-2.0.7-8.oe2203.aarch64 iSulad-2.0.18-17.oe2203.aarch64 lcr-2.0.9-8.oe2203.aarch64
Complete!
[root@kunlun-rk3588 build]# systemctl status isulad.service
× isulad.service - iSulad Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/isulad.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2024-04-24 06:28:42 UTC; 26s ago
Process: 178100 ExecStart=/usr/bin/isulad $OPTIONS (code=exited, status=1/FAILURE)
Main PID: 178100 (code=exited, status=1/FAILURE)
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 5.
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: Stopped iSulad Application Container Engine.
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: isulad.service: Start request repeated too quickly.
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: isulad.service: Failed with result 'exit-code'.
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: Failed to start iSulad Application Container Engine.
[root@kunlun-rk3588 build]# journalctl -xeu isulad.service
░░ Subject: A start job for unit isulad.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit isulad.service has finished with a failure.
░░
░░ The job identifier is 5259 and the job result is failed.
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit isulad.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: Stopped iSulad Application Container Engine.
░░ Subject: A stop job for unit isulad.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit isulad.service has finished.
░░
░░ The job identifier is 5312 and the job result is done.
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: isulad.service: Start request repeated too quickly.
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: isulad.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit isulad.service has entered the 'failed' state with result 'exit-code'.
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: Failed to start iSulad Application Container Engine.
░░ Subject: A start job for unit isulad.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit isulad.service has finished with a failure.
░░
░░ The job identifier is 5312 and the job result is failed.
[root@kunlun-rk3588 build]# sudo isulad -l debug
engine 20240424063041.174 WARN /home/abuild/rpmbuild/BUILD/lcr-v2.0.9/third_party/log.c:isula_libutils_log_enable:403 - Log already initialized
engine 20240424063041.174 WARN /home/abuild/rpmbuild/BUILD/lcr-v2.0.9/third_party/log.c:isula_libutils_log_enable:403 - Log already initialized
iSula 20240424063041.174 INFO /home/abuild/rpmbuild/BUILD/iSulad-v2.0.18/src/daemon/modules/log/log_gather.c:log_gather:378 - Begin to gather logs...
[root@kunlun-rk3588 build]# yum update iSulad
Last metadata expiration check: 0:03:46 ago on Wed Apr 24 06:28:47 2024.
Dependencies resolved.
Nothing to do.
Complete!
[root@kunlun-rk3588 iSulad]# journalctl -f -u isulad
Apr 24 06:28:42 kunlun-rk3588 isulad[178100]: engine 20240424062842.750 ERROR /home/abuild/rpmbuild/BUILD/iSulad-v2.0.18/src/daemon/modules/image/image.c:bims_init:1901 - Failed to init bim oci
Apr 24 06:28:42 kunlun-rk3588 isulad[178100]: engine 20240424062842.750 ERROR /home/abuild/rpmbuild/BUILD/iSulad-v2.0.18/src/cmd/isulad/main.c:isulad_server_init_common:1389 - Failed to init image manager
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: isulad.service: Main process exited, code=exited, status=1/FAILURE
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: isulad.service: Failed with result 'exit-code'.
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: Failed to start iSulad Application Container Engine.
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 5.
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: Stopped iSulad Application Container Engine.
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: isulad.service: Start request repeated too quickly.
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: isulad.service: Failed with result 'exit-code'.
Apr 24 06:28:42 kunlun-rk3588 systemd[1]: Failed to start iSulad Application Container Engine.
[ 1048.144037] systemd[1]: systemd v249-72.oe2203 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA -SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID -CURL -ELFUTILS -FIDO2 +IDN2 -IDN -IPTC +KMOD -LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB -ZSTD +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=legacy)
[ 1048.144963] systemd[1]: Detected architecture arm64.
[ 1048.226291] systemd[1]: /usr/lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket \xe2\x86\x92 /run/dbus/system_bus_socket; please update the unit file accordingly.
[ 1048.243246] systemd[1]: Configuration file /usr/lib/systemd/system/isulad.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
[root@kunlun-rk3588 yum.repos.d]# systemctl status isulad.service
× isulad.service - iSulad Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/isulad.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2024-04-25 02:41:07 UTC; 10min ago
Main PID: 1362 (code=exited, status=1/FAILURE)
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: isulad.service: Main process exited, code=exited, status=1/FAILURE
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: isulad.service: Failed with result 'exit-code'.
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: Failed to start iSulad Application Container Engine.
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 3.
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: Stopped iSulad Application Container Engine.
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: isulad.service: Start request repeated too quickly.
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: isulad.service: Failed with result 'exit-code'.
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: Failed to start iSulad Application Container Engine.
[root@kunlun-rk3588 yum.repos.d]# rpm -qa | grep -i iSulad
iSulad-2.0.18-17.oe2203.aarch64
[root@kunlun-rk3588 yum.repos.d]# rpm -qa | grep -i clibcni
clibcni-2.0.7-8.oe2203.aarch64
[root@kunlun-rk3588 yum.repos.d]# rpm -qa | grep -i lcr
lcr-2.0.9-8.oe2203.aarch64
[root@kunlun-rk3588 yum.repos.d]# journalctl -f -u isulad
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: Stopped iSulad Application Container Engine.
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: Starting iSulad Application Container Engine...
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: isulad.service: Main process exited, code=exited, status=1/FAILURE
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: isulad.service: Failed with result 'exit-code'.
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: Failed to start iSulad Application Container Engine.
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 3.
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: Stopped iSulad Application Container Engine.
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: isulad.service: Start request repeated too quickly.
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: isulad.service: Failed with result 'exit-code'.
Apr 25 02:41:07 kunlun-rk3588 systemd[1]: Failed to start iSulad Application Container Engine.
麻烦老师看一下是什么问题呢
@zhongtao @jake
[root@kunlun-rk3588 yum.repos.d]# /usr/bin/isulad
engine 20240425034633.806 ERROR /home/abuild/rpmbuild/BUILD/iSulad-v2.0.18/src/utils/cutils/utils_fs.c:try_probe_overlay_module:188 - modprobe overlay exec failed: [], ["modprobe: FATAL: Module overlay not found in directory /lib/modules/5.10.66\n"]
engine 20240425034633.806 ERROR /home/abuild/rpmbuild/BUILD/iSulad-v2.0.18/src/daemon/modules/image/oci/storage/layer_store/graphdriver/overlay2/driver_overlay2.c:overlay2_init:341 - driver 'overlay'not supported
engine 20240425034633.806 ERROR /home/abuild/rpmbuild/BUILD/iSulad-v2.0.18/src/daemon/modules/image/oci/storage/storage.c:storage_module_init:1892 - Failed to init layer store
engine 20240425034633.806 ERROR /home/abuild/rpmbuild/BUILD/iSulad-v2.0.18/src/daemon/modules/image/oci/oci_image.c:storage_module_init_helper:272 - Failed to init storage module
engine 20240425034633.806 ERROR /home/abuild/rpmbuild/BUILD/iSulad-v2.0.18/src/daemon/modules/image/image.c:bims_init:1901 - Failed to init bim oci
engine 20240425034633.806 ERROR /home/abuild/rpmbuild/BUILD/iSulad-v2.0.18/src/cmd/isulad/main.c:isulad_server_init_common:1389 - Failed to init image manager
长时间未回复,暂时关闭问题,若有问题可再次打开此issue
登录 后才可以发表评论