DHB-liuhong opened a new issue #2156:
URL: https://github.com/apache/apisix/issues/2156
### Issue description
### Environment
* apisix version (cmd: `apisix version`): 1.4
* OS: arm linux 7.6
### Minimal test code / Steps to reproduce the issue
1. apisix start
### What's the actual result? (including assertion message & call stack if
applicable)
root@node0002 conf]# apisix start
nginx: [error] init_by_lua error:
/usr/local/apisix//deps/share/lua/5.1/resty/radixtree.lua:76:
/usr/local/apisix//deps/lib64/lua/5.1/librestyradixtree.so: cannot open shared
object file: No such file or directory
stack traceback:
[C]: in function 'load_shared_lib'
/usr/local/apisix//deps/share/lua/5.1/resty/radixtree.lua:76: in
main chunk
[C]: in function 'require'
/usr/local/apisix/apisix/admin/init.lua:19: in main chunk
[C]: in function 'require'
/usr/local/apisix/apisix/init.lua:22: in main chunk
[C]: in function 'require'
init_by_lua:3: in main chunk
2. i find that，because ffi.load(fpath) is failed。
3. i use openresty's luajit to run a test ,is failed
[root@node0002 bin]# pwd
/usr/local/openresty/luajit/bin
[root@node0002 bin]# cat test.lua
local ffi = require("ffi")
local t="/usr/local/apisix/deps/lib64/lua/5.1/librestyradixtree.so"
--local f = io.open(t)
--if f ~= nil then
-- print("test")
--end
print("test11111")
local c = ffi.load(t)
print("test22222")
[root@node0002 bin]# ll
total 520
lrwxrwxrwx 1 root root 18 Sep 3 14:28 luajit -> luajit-2.1.0-beta3
-rwxr-xr-x 1 root root 527096 Sep 3 14:24 luajit-2.1.0-beta3
-rw-r--r-- 1 root root 226 Sep 3 14:01 test.lua
[root@node0002 bin]# ./luajit test.lua
test11111
./luajit: test.lua:8:
/usr/local/apisix/deps/lib64/lua/5.1/librestyradixtree.so: cannot open shared
object file: No such file or directory
stack traceback:
[C]: in function 'load'
test.lua:8: in main chunk
[C]: at 0x00404bd0
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
