Skip to content
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

FreeNginx 1.27.2 - resty.shell Module Load Failure and HAVE_SOCKET_CLOEXEC_PATCH Issue #485

Closed
3 tasks
JIFVGWHvAseSovQ opened this issue Aug 2, 2024 · 0 comments

Comments

@JIFVGWHvAseSovQ
Copy link

JIFVGWHvAseSovQ commented Aug 2, 2024

I am encountering an issue while using FreeNginx version 1.27.2 (https://freenginx.org/). Other Lua modules are functioning correctly, but I receive an error when attempting to load the resty.shell module. The error log is as follows:

location / {
	content_by_lua_block {
		require("resty.shell")
	}
}
2024/08/02 10:05:31 [error] 25#25: *9 lua entry thread aborted: runtime error: pipe API is not supported due to either a platform issue or lack of the HAVE_SOCKET_CLOEXEC_PATCH patch

2024/08/02 10:08:17 [error] 22#22: *13 lua entry thread aborted: runtime error: /usr/local/lib/resty/core/base.lua:80: loop or previous error loading module 'resty.shell'
nginx version: nginx/1.27.2

configure arguments: --prefix=/etc/nginx --pid-path=/tmp/nginx.pid --lock-path=/tmp/nginx.lock --sbin-path=/usr/local/bin/nginx --modules-path=/etc/nginx/modules --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --http-log-path=/var/log/nginx/access.log --http-scgi-temp-path=/etc/nginx/cache/scgi_temp --http-uwsgi-temp-path=/etc/nginx/cache/uwsgi_temp --http-proxy-temp-path=/etc/nginx/cache/proxy_temp --http-fastcgi-temp-path=/etc/nginx/cache/fastcgi_temp --http-client-body-temp-path=/etc/nginx/cache/client_temp --with-mail --user=nginx --group=nginx --with-stream --with-compat --with-threads --with-file-aio --with-http_v2_module --with-http_v3_module --with-http_ssl_module --with-http_dav_module --with-http_flv_module --with-http_mp4_module --with-http_sub_module --with-mail_ssl_module --with-http_slice_module --with-stream_ssl_module --with-http_realip_module --with-http_addition_module --with-stream_realip_module --with-http_secure_link_module --with-http_stub_status_module --with-http_auth_request_module --with-http_random_index_module --with-stream_ssl_preread_module --with-openssl-opt='no-weak-ssl-ciphers -DOPENSSL_TLS_SECURITY_LEVEL=5 enable-tls1_3' --with-ld-opt='-lrt -ljemalloc -Wl,-z,relro -Wl,-rpath,/usr/local/lib,--as-needed,-O3,--sort-common' --with-cc-opt='-g -O3 -ffile-prefix-map=/data/builder/debuild/nginx-$NGINX_VERSION/debian/debuild-base/nginx-$NGINX_VERSION=. -fstack-protector-strong -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fPIC -flto -m64 -mtune=native --param=ssp-buffer-size=4' --add-module=../ngx_devel_kit-0.3.3 --add-module=../lua-nginx-module-0.10.26  --add-module=../headers-more-nginx-module-0.37 --add-module=../stream-lua-nginx-module-0.0.14

I have attempted the following:

Searched the internet for solutions.
Consulted an AI assistant (Claude 3.5), but did not find an effective remedy.
Checked the compilation configuration, but found no obvious issues.
My questions are:

Is this error related to FreeNginx version 1.27.2, or is it due to my system configuration?
Should the HAVE_SOCKET_CLOEXEC_PATCH be included in FreeNginx 1.27.2? If so, why has it not been applied correctly?
Are there any methods to resolve this issue and enable the resty.shell module to work properly?
Is any special compilation or configuration needed for FreeNginx to support resty.shell?
My system information:

Operating System: [Please provide your operating system information]
FreeNginx Version: 1.27.2
NDK Version: 0.3.3
lua-nginx Version: 0.10.26
resty-core Version: https://github.com/openresty/lua-resty-core/archive/refs/heads/master.tar.gz
LuaJIT Version: 2.1-20240626
Thank you very much for your help and guidance. I am happy to provide any additional information if needed.

This place is for bug reports and development discussions only. For general questions and
discussions, please join the openresty-en mailing list instead: https://groups.google.com/group/openresty-en.
If you want to use Chinese, please join the openresty (Chinese) mailing list instead: https://groups.google.com/group/openresty.
Do not use Chinese in this place.

Before you open a new issue, please search the internet and make sure it is not duplicate.

Ensure you have provided the following details while reporting a problem:

  • The exact version of the related software, including but not limited to the OpenResty version
    (if any), the NGINX core version, the ngx_lua module version(via openresty -V or nginx -V),
    and the lua-resty-core version(via resty -e 'print(require("resty.core").version)'),
    and your operating system version(via uname -a).
  • A minimal and standalone test case that others can easily run on their side and
    reproduce the issue you are seeing.
  • Do not simply say "something is broken" or "something does not work". Always provide
    as much details as possible. Always describe the symptoms and your expected results.

You can (temporarily) enable the nginx debugging logs to see the internal workings
of NGINX in your nginx''s error.log file. See http://nginx.org/en/docs/debugging_log.html
The same instructions apply equally well to OpenResty.

If you are seeing crashes, please provide the full backtrace for the crash. See
https://www.nginx.com/resources/wiki/start/topics/tutorials/debugging/#core-dump
for more details.

Thanks for your cooperation.

@JIFVGWHvAseSovQ JIFVGWHvAseSovQ closed this as not planned Won't fix, can't repro, duplicate, stale Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant