-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
apisix-2.1/apisix/init.lua:89: module 'resty.worker.events' not found: #3207
Comments
@idbeta @Firstsawyou you can make a check the steps are fine. If we can not reproduce this issue, can you supply the login information of your machine? @hifou then we can make a check |
@membphis 非常感谢,我这边可以提供账号,帮忙看一下。 |
Ok, let me make sure. |
@hifou $ make init
Warning! Running apisix under /root is only suitable for development environments and it is dangerous to do so. It is recommended to run APISIX in a directory other than /root.
./bin/apisix init_etcd $ cat ./logs/error.log
init_worker_by_lua error: /root/apisix-2.1/apisix/init.lua:89: module 'resty.worker.events' not found:
no field package.preload['resty.worker.events']
no file '/root/apisix-2.1//deps/share/lua/5.1/resty/worker/events.lua'
no file '/root/apisix-2.1//deps/share/lua/5.1/resty/worker/events/init.lua'
no file '/root/apisix-2.1/resty/worker/events.lua'
no file '/root/apisix-2.1/resty/worker/events/init.lua'
no file '/usr/local/openresty/site/lualib/resty/worker/events.ljbc'
no file '/usr/local/openresty/site/lualib/resty/worker/events/init.ljbc' |
I think this is a bug, and the apisix service should be prohibited from starting when |
@Firstsawyou would you like to fix this issue? ^_^ |
Yes, let me try it. |
Cause of the bug: After APISIX is started, the
|
@Firstsawyou do you know why we can capture this error in CLI? Is there any way we can capture this error when the user calls |
When calling the
and the running of apisix is prohibited. |
I want to know why the lack of permissions cannot be detected in the old version of CLI. How does Kong solve similar problems? |
This problem exists in the old version. I need to check the solutions to similar problems in kong. |
The text was updated successfully, but these errors were encountered: