load_module with "./configure ... --modules-path=<path> ..."
Fabiano Furtado Pessoa Coelho
fusca14 at gmail.com
Wed Jul 12 21:40:21 UTC 2023
Hello...
I have compiled NGINX 1.24.0 with "./configure ... --modules-path=<path> ...".
Therefore, the "load_module" directive is not reading the path/config
specified in "--modules-path" parameter. For instance, in nginx.conf,
I have declared "load_module ngx_http_module1.so;" and when I test it,
the following message appears:
# nginx -t
nginx: [emerg] dlopen() "/etc/nginx/ngx_http_module1.so" failed
(/etc/nginx/ngx_http_module1.so: cannot open shared object file: No
such file or directory) in /etc/nginx/nginx.conf:12
nginx: configuration file /etc/nginx/nginx.conf test failed
Why? Should the "load_module" directive read "--modules-path" value,
if specified in "./configure"? From the "load_module" official
documentation (http://nginx.org/en/docs/ngx_core_module.html#load_module),
there is no default value defined, but, once "--modules-path" is
configured, the "load_module" directive should read from
"--modules-path", right? If not, what is the purpose of "./configure
... --modules-path=<path> ...", to compile NGINX?
Of course, if I specify the full path "load_module
/<path>/ngx_http_module1.so;", it works fine.
Thanks in advance.
Fabiano Furtado
More information about the nginx
mailing list