- This topic has 11 replies, 1 voice, and was last updated 1 year, 6 months ago by Thijs Eilander.
-
AuthorPosts
-
-
ivanGuest
hello,
today i tried to do anapt get update && apt get upgrade
but i get this error. How could I fix it?
https://gist.githubusercontent.com/ivanionut/950da7a1c1a0eb1a7ae1318cb0d22a52/raw/e08798c5bb39f769a2aa660072150f39f29a8643/nginx_error_update.logthanks,
Ivan -
Thijs EilanderKeymaster
Hmmm, you’re probably upgrading from an old version, I moved all naxsi related stuff to the naxsi package a while back.
You can probably uninstall nginx-common and reinstall it
-
Thijs EilanderKeymaster
Ok, due to some git error I had some old files laying around, rebuilding now. hopefully its fixed
-
ivanGuest
Ok, thank you!
the next few days I’ll try again and I’ll let you know if I succeeded! -
ivanGuest
I am trying to install on a clean test server, but I get this error:
sudo apt install nginx-full
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:The following packages have unmet dependencies:
libnginx-mod-http-lua : Depends: lua-resty-core but it is not installable
Depends: lua-resty-lrucache but it is not installable
libnginx-mod-stream-lua : Depends: lua-resty-core but it is not installable
Depends: lua-resty-lrucache but it is not installable
E: Unable to correct problems, you have held broken packages.-
Thijs EilanderGuest
Are you installing from my own rep or from launchpad? I see there is something wrong with launchpad.
Rebuilding lua-resty-* now just to make sure
-
Thijs EilanderGuest
There was a faulty lua module, (healthcheck), removed it for now. Compiling and uploading now.
Thanks for your report
-
-
-
ivanGuest
I still can’t complete the installation:
-
Thijs EilanderGuest
Can you remove /etc/nginx/modules-enabled/50-mod-nchan.conf before upgrading/starting nginx?
I don’t know why this is happening, but will take a look at it
-
ivanGuest
Setting up nginx-core (1.23.2-3myguard2~jammy) …
Job for nginx.service failed because the control process exited with error code.
See “systemctl status nginx.service” and “journalctl -xeu nginx.service” for details.
invoke-rc.d: initscript nginx, action “start” failed.
× nginx.service – A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2022-10-23 18:47:52 CEST; 31ms ago
Docs: man:nginx(8)
Process: 4871 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)
CPU: 28msOct 23 18:47:52 vmi1019973.contaboserver.net systemd[1]: Starting A high performance web server and a reverse proxy server…
Oct 23 18:47:52 vmi1019973.contaboserver.net nginx[4871]: nginx: [emerg] dlopen() “/usr/share/nginx/modules/ngx_http_ssl_ct_module.so” failed (/usr/share/nginx/modules/ngx_http_ssl_ct_module.so: undefined symbol: ngx_ssl_ct_create_srv_conf) in /etc/nginx/modules-enabled/50-mod-http-ssl-ct.conf:1
Oct 23 18:47:52 vmi1019973.contaboserver.net nginx[4871]: nginx: configuration file /etc/nginx/nginx.conf test failed
Oct 23 18:47:52 vmi1019973.contaboserver.net systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Oct 23 18:47:52 vmi1019973.contaboserver.net systemd[1]: nginx.service: Failed with result ‘exit-code’.
Oct 23 18:47:52 vmi1019973.contaboserver.net systemd[1]: Failed to start A high performance web server and a reverse proxy server.
dpkg: error processing package nginx-core (–configure):
installed nginx-core package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of nginx-full:
nginx-full depends on nginx-core (>= 1.23.2-3myguard2~jammy); however:
Package nginx-core is not configured yet.
nginx-full depends on nginx-core (<< 1.23.2-3myguard2~jammy.1~); however:
Package nginx-core is not configured yet.dpkg: error processing package nginx-full (–configure):
dependency problems – leaving unconfigured
Errors were encountered while processing:
nginx-core
nginx-full
E: Sub-process /usr/bin/dpkg returned an error code (1) -
ivanGuest
I’m sorry, I solved this last problem…
It was the same one I had encountered here: https://deb.myguard.nl/forums/topic/nginx-emerg-dlopen-usr-share-nginx-modules-ngx_http_ssl_ct_module-so/ -
Thijs EilanderGuest
Good to hear.
It’s wise to remove all *conf files from the modules-enabled directory if you don’t need that module. It can speed up reloading/starting a lot. If you need that module later you can symlink it from the modules-available directory.
-
-
AuthorPosts