I worked around the missing /etc/apt/sources.list file… but got bitten afterwards by the fact that mailman was installed… and ensued a dirty mess related to conflicting upgrade options… I fear that in this case, the upgrade script won’t be usable :-/
Fortunately, that was a tests instance, so I’m gonna kill it and start over with attempting a fresh installation over a Debian bullseye system :-/
I’ve started over on a fresh Debian 11/bullseye server at Gandi Cloud, and got a but (see Installation script doesn't work on fresh Gandi VPS with Debian 10 - it's missing debconf · Issue #1828 · YunoHost/issues · GitHub) which I solved by performing a dpkg-reconfigure debconf before launching the installation. FWIW.
Hi,
I have an error with Nginx.
2022/04/28 09:34:08 [info] 1834#1834: Using 131072KiB of shared memory for nchan in /etc/nginx/nginx.conf:61
2022/04/28 09:34:14 [warn] 2375#2375: could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size
2022/04/28 11:22:12 [warn] 1881#1881: could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size
2022/04/28 11:22:12 [info] 1881#1881: Using 131072KiB of shared memory for nchan in /etc/nginx/nginx.conf:61
How can solve this ?
Thank…
Edit:
$ cat /etc/nginx/nginx.conf
user www-data;
worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;
events {
worker_connections 768;
# multi_accept on;
}
http {
##
# Basic Settings
##
sendfile on;
tcp_nopush on;
types_hash_max_size 2048;
# server_tokens off;
# server_names_hash_bucket_size 64;
# server_name_in_redirect off;
include /etc/nginx/mime.types;
default_type application/octet-stream;
##
# SSL Settings
##
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; # Dropping SSLv3, ref: POODLE
ssl_prefer_server_ciphers on;
##
# Logging Settings
##
access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log;
##
# Gzip Settings
##
gzip on;
# gzip_vary on;
# gzip_proxied any;
# gzip_comp_level 6;
# gzip_buffers 16 8k;
# gzip_http_version 1.1;
# gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;
##
# Virtual Host Configs
##
include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;
}
#mail {
# # See sample authentication script at:
# # http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
#
# # auth_http localhost/auth.php;
# # pop3_capabilities "TOP" "USER";
# # imap_capabilities "IMAP4rev1" "UIDPLUS";
#
# server {
# listen localhost:110;
# protocol pop3;
# proxy on;
# }
#
# server {
# listen localhost:143;
# protocol imap;
# proxy on;
# }
#}
The upgrade failed for me, but I haven’t investigated the logs deeply yet: https://paste.yunohost.org/raw/epalatehon
It’s here in the log you shared…
…
2022-04-29 03:04:03,551: INFO - + The following packages have unmet dependencies:
2022-04-29 03:04:03,616: INFO - + archivebox-ynh-deps : Depends: python-dev
2022-04-29 03:04:03,640: WARNING - E: Unable to correct problems, you have held broken packages.
…
Meaning that some package dependencies cannot be met for the application ArchiveBox. So you have to try to fix the things regarding python-dev like, checking if it is hold
sudo dpkg --get-selections | grep hold
And if it’s because of some package on hold, you can try
sudo apt-mark unhold package_name
And retry the migration…
Or you can also remove the App ArchiveBox if you don’t use it.
I just removed it to see but now it seems that all packages are broken, based on my skim of the logs
They are here https://paste.yunohost.org/raw/anonesaqej
Maybe remove archivebox-ynh-deps ?
If you have access to the command line through ssh, you can do:
sudo apt remove archivebox-ynh-deps and retry the migration if the package have been removed properly.
this worked! thanks so much
Trying to upgrade from Buster to Bullseye but seems like apt-get dist-upgrade or apt full-upgrade isn’t working.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
moulinette ssowat yunohost yunohost-admin
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Even with yunohost tools upgrade ?
Is there are roadmap / release date?
We’ll talk about it and work on it tomorrow night during the contributors meeting. (cf. Instance Etherpad Publique de La Quadrature Du Net )
There is a new release candidate:
I had the same issue as @micohau
After switching to testing, I had to upgrade YunoHost package from 4.3 to 4.4 so the upgrade to bullseye is proposed
Before switching to testing
root@myServer:~# yunohost --version
yunohost:
repo: stable
version: 4.3.6.3
yunohost-admin:
repo: testing
version: 4.3.4.1
moulinette:
repo: stable
version: 4.3.3.1
ssowat:
repo: stable
version: 4.3.3.1
root@myServer:~#
switching to testing
root@myServer:~# curl https://install.yunohost.org/switchtoTesting | bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 462 100 462 0 0 3818 0 --:--:-- --:--:-- --:--:-- 3818
----
Patching sources.list to enable testing repository...
----
----
Running 'apt-get update'
----
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian buster-updates InRelease
Hit:3 http://security.debian.org buster/updates InRelease
Hit:4 http://mirror.hetzner.com/debian/packages buster InRelease
Hit:5 http://mirror.hetzner.com/debian/packages buster-updates InRelease
Hit:6 http://mirror.hetzner.com/debian/security buster/updates InRelease
Hit:7 http://forge.yunohost.org/debian buster InRelease
Get:8 http://forge.yunohost.org/debian buster/testing amd64 Packages [5,505 B]
Fetched 5,505 B in 1s (3,878 B/s)
Reading package lists... Done
----
Running 'apt-get dist-upgrade'
----
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
moulinette ssowat yunohost yunohost-admin
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
root@myServer:~#
nothing happens
"fix":
root@myServer:~# yunohost tools upgrade
Warning: Using 'yunohost tools upgrade' with --apps / --system is deprecated, just write 'yunohost tools upgrade apps' or 'system' (no -- prefix anymore)
Error: Please specify 'apps', or 'system'
root@myServer:~# yunohost tools upgrade --system
Warning: Using 'yunohost tools upgrade' with --apps / --system is deprecated, just write 'yunohost tools upgrade apps' or 'system' (no -- prefix anymore)
Info: Upgrading packages...
Info: Now upgrading 'special' (yunohost-related) packages...
Warning: The special upgrade will continue in the background. Please don't start any other actions on your server for the next ~10 minutes (depending on hardware speed). After this, you may
have to re-log in to the webadmin. The upgrade log will be available in Tools → Log (in the webadmin) or using 'yunohost log list' (from the command-line).
Running scope as unit: run-r9eae4a1ad6ef48e884a2a034d5f9669e.scope
root@myServer:~# Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
....
root@myServer:~# yunohost --version
yunohost:
repo: testing
version: 4.4.1
yunohost-admin:
repo: testing
version: 4.4.0
moulinette:
repo: testing
version: 4.4.0
ssowat:
repo: testing
version: 4.4.0
start migration
root@myServer:~# yunohost tools migrations run
Warning: To run the migration 0021_migrate_to_bullseye, your must accept the following disclaimer:
---
N.B.: **THIS MIGRATION IS STILL IN BETA-STAGE** ! If your server hosts critical services and if you are not too confident with debugging possible issues, we recommend you to wait a little bit more while we gather more feedback and polish things up. If on the other hand you are relatively confident with debugging small issues that may arise, you are encouraged to run this migration ;)! You can read and share feedbacks on this forum thread: https://forum.yunohost.org/t/18531
Please note that this migration is a delicat
....
Upgrade went fine for this mock up server. (Install is only one month old and not real usage on it)
apps installed
root@myServer:~# yunohost app list | grep id
id: dokuwiki
id: grav
id: kanboard
id: my_webapp
id: my_webapp__2
id: nextcloud
id: wordpress
One thing is “strange” in the service part:
root@myServer:~# yunohost service status
...
php7.3-fpm:
configuration: valid
description: The PHP 7.3 FastCGI Process Manager
last_state_change: 1970-01-01 00:00:00
start_on_boot: disabled
status: dead
php7.4-fpm:
configuration: valid
description: The PHP 7.4 FastCGI Process Manager
last_state_change: 2022-05-18 19:11:43
start_on_boot: enabled
status: running
...
Does restarting php7.3-fpm work? If not, what’s its error log?
Not really an error as all apps are fine and php 7.4 seems fine too.
It’s more cosmetic as it could be confusing if someone ends in this part of the webadmin and gets a “red warning”
I expect php 7.4 to replace and mabye remove the old php 7.3 but there might be some usecases for it. I have no idea.
# ps aux | grep -i php
root 774 0.0 1.0 271048 39992 ? Ss May18 0:08 php-fpm: master process (/etc/php/7.4/fpm/php-fpm.conf)
grav 990 0.0 0.2 270984 10156 ? S May18 0:00 php-fpm: pool grav
grav 991 0.0 0.2 270984 10156 ? S May18 0:00 php-fpm: pool grav
kanboard 993 0.0 0.3 270980 12232 ? S May18 0:00 php-fpm: pool kanboard
kanboard 994 0.0 0.3 270980 12232 ? S May18 0:00 php-fpm: pool kanboard
kanboard 999 0.0 0.3 270980 12232 ? S May18 0:00 php-fpm: pool kanboard
nextclo+ 1000 0.0 0.4 271440 15816 ? S May18 0:00 php-fpm: pool nextcloud
nextclo+ 1003 0.0 0.3 270984 12172 ? S May18 0:00 php-fpm: pool nextcloud
nextclo+ 1004 0.0 0.3 270984 12172 ? S May18 0:00 php-fpm: pool nextcloud
wordpre+ 1010 0.0 0.9 274040 38040 ? S May18 0:00 php-fpm: pool wordpress
wordpre+ 1011 0.0 0.2 270984 10160 ? S May18 0:00 php-fpm: pool wordpress
wordpre+ 1015 0.0 0.2 270984 10160 ? S May18 0:00 php-fpm: pool wordpress
wordpre+ 1017 0.0 0.2 271116 10160 ? S May18 0:00 php-fpm: pool wordpress
wordpre+ 1019 0.0 0.2 271116 10160 ? S May18 0:00 php-fpm: pool wordpress
wordpre+ 1020 0.0 0.2 271116 10160 ? S May18 0:00 php-fpm: pool wordpress
wordpre+ 1021 0.0 0.2 271116 10160 ? S May18 0:00 php-fpm: pool wordpress
wordpre+ 1022 0.0 0.2 271116 10160 ? S May18 0:00 php-fpm: pool wordpress
www-data 1024 0.0 0.2 271112 10160 ? S May18 0:00 php-fpm: pool www
www-data 1026 0.0 0.2 271112 10160 ? S May18 0:00 php-fpm: pool www
root 26744 0.0 0.0 6272 712 pts/0 S+ 19:04 0:00 grep -i php
php 7.3 logs
https://paste.yunohost.org/veguvitube
Shouldn’t be php7.3 removed?
As I read here
The version 7.3 is not receiving any security updates since December 2021 and should not be used anymore.
Security updates for 7.4 will end in 6 months.
Update made on my main server. After a quick test:
La migration 0023_postgresql_11_to_13 a échoué avec l’exception PostgreSQL 11 est installé, mais pas PostgreSQL 13 ! ? Quelque chose d’anormal s’est peut-être produit sur votre système :(… : annulation
all other apps seems fine, thanks a lot !
id: agendav
id: baikal
id: diagramsnet
id: dokuwiki
id: dokuwiki__2
id: ethercalc
id: freshrss
id: grav
id: kanboard
id: nextcloud
id: shellinabox
id: wallabag2
id: wordpress