- READ ME AND USE THIS TEMPLATE IF YOU WANT TO GET HELP ! You may ask your question in english or french, whichever is easiest for you… But please use one of the templates provided below
- LISEZ-MOI ET UTILISEZ CE MODÈLE DE TOPIC SI VOUS SOUHAITEZ OBTENIR DE L’AIDE ! Vous pouvez poser votre question en anglais ou français, selon ce qui est le plus simple pour vous… Mais de préférence en utilisant l’un des deux modèles fournis ci-dessous
/
Message template (english)
The “support” category is meant to ask for help or troubleshooting related to installing or using YunoHost or its applications. It is not to ask assistance on general system administration, network administration or special use cases that goes beyond the scope of the project. If you wish to discuss more advanced use case, please post in the “Advanced Use Case” category.
Before posting, please :
- Look for similar issues on this forum using the error message.
- If you did not already, consider searching / reading the administrator documentation
- Take the time to say Hi and stay friendly, this is a forum and project 100% ran by volunteer human beings
My YunoHost server
Hardware: Old Celeron Chromebook…
YunoHost version: 11.0.11
I have access to my server : ssh as well as physical access if needed
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : No
If yes, please explain:
Description of my issue
I ran a routine upgrade on my system last night from web ui before going to bed, assuming it would be fine running overnight. Fast forward to now, I try to access the web ui and get a dreaded “Web server is down”… but the system itself is online, so I try again from ssh, revealing the true cause to be an nginx-extras plugin. No idea how to get out of this one.
Do you want to continue? [Y/n]
Reading changelogs... Done
Extracting templates from packages: 100%
Preconfiguring packages ...
Setting up nginx-extras (1.18.0-6.1+deb11u3) ...
Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xe" 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 Mon 2023-01-30 12:12:28 CST; 15ms ago
Docs: man:nginx(8)
Process: 1927233 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)
CPU: 21ms
Jan 30 12:12:28 <snip> systemd[1]: Starting A high performance web server and a reverse proxy server...
Jan 30 12:12:28 <snip> nginx[1927233]: nginx: [emerg] dlopen() "/usr/share/nginx/modules/ngx_http_image_filter_module.so" failed (libx265.so.165: cannot open shared object file: No such file or directory) in /etc/nginx/modules-enabled/50-mod-http-image-filter.conf:1
Jan 30 12:12:28 <snip> nginx[1927233]: nginx: configuration file /etc/nginx/nginx.conf test failed
Jan 30 12:12:28 <snip> systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Jan 30 12:12:28 <snip> systemd[1]: nginx.service: Failed with result 'exit-code'.
Jan 30 12:12:28 <snip> systemd[1]: Failed to start A high performance web server and a reverse proxy server.
dpkg: error processing package nginx-extras (--configure):
installed nginx-extras package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
nginx-extras
E: Sub-process /usr/bin/dpkg returned an error code (1)
It seems the plugin in question depends on an old version of libx265 that’s not packaged in Debian’s repositories anymore… Is this on their side?