Hmpf ben il faudrait essayer de trouver un gros fichier de log un peu vieux et inutile (NB: attention il y a des fichiers de log très important donc faut pas supprimer n’importe quoi)
Si tu peux, essaye d’installer ncdu avec apt install ncdu puis lance ncdu /var/log pour faire un scan qui te montrera ce qui prends de la place (et possibiltié de naviguer dans les dossiers etc)
Ce qui est idéal c’est de supprimer de vieux fichiers de log nginx si il y’en a qui prennent de la place
On peut les télécharger avant (en FTP) pour faire une sauvegarde, et virer les gros logs qui pèsent plus de 10Mo par exemple.
Hurrah! Congratulations! I look forward to the migration \o/
Sur un Raspberry Pi 3 avec un bureau installé, la mise à jour ne passe pas, apparemment à cause des paquets marqués en “hold” durant la procédure, qui bloquent la mise à jour à cause d’un conflit ? 
Info : + Les paquets suivants contiennent des dépendances non satisfaites :
Info : + debhelper : Dépend: dh-autoreconf (>= 17~) mais ne sera pas installé
Info : + libgirepository-1.0-1 : Casse: python3-gi (< 3.34.0-4~) mais 3.30.4-1 devra être installé
edit: I opened a dedicated topic here Upgrade to Debian 11 failing : Raspberry Pi 3B+ / dh-autoreconf python3-gi issues
@lapineige : ce que tu montres ne sont pas des paquets en hold, ce sont des paquets qui ont des problème de dépendance. Tu as le log complet ?
Just to be clear: Is uninstalling postgresql11 the solution to the postgresql 11 to 13 migration problem? I presume that would break things?
(Side note: Mastodon has stopped working on my system. I guess it stores its data in postgresql?)
@eivind : It’s not super clear … it seems that on some system, postgresql is not required anymore but is still installed and not auto-cleanedup by apt … If that’s the case, uninstalling postgresql-11 is fine. But maybe Mastodon does use postgresql indeed.
You can find out with :
grep -A10 "ynh-deps" /var/lib/dpkg/status | grep "Package:\|Depends:" | grep -B1 postgresql
The result from the command is
Package: mastodon-ynh-deps
Depends: imagemagick, ffmpeg, libpq-dev, libxml2-dev, libxslt1-dev, file, git-core, g++, libprotobuf-dev, protobuf-compiler, pkg-config, gcc, autoconf, bison, build-essential, libssl-dev, lib
yaml-dev, libreadline6-dev, zlib1g-dev, libncurses5-dev, libffi-dev, libgdbm3 | libgdbm6, libgdbm-dev, redis-tools, redis-server, postgresql, postgresql-contrib, libidn11-dev, libicu-dev, lib
jemalloc-dev, curl, apt-transport-https, libreadline-dev, libsqlite3-dev, libxslt-dev, automake, libtool, yarn
--
Package: mobilizon-ynh-deps
Depends: postgresql, postgresql-client, postgresql-contrib, postgis, postgresql-postgis-scripts, argon2, imagemagick, webp, gifsicle, jpegoptim, optipng, pngquant, file
--
Package: peertube-ynh-deps
Depends: ffmpeg, postgresql, postgresql-contrib, openssl, g++, mailutils, apt-transport-https, yarn
Package: pixelfed-ynh-deps
Depends: postgresql, libgd3, jpegoptim, optipng, pngquant, ffmpeg, imagemagick, supervisor, php7.4-bcmath, php7.4-cli, php7.4-ctype, php7.4-curl, php7.4-exif, php7.4-gd, php7.4-iconv, php7.4-
intl, php7.4-json, php7.4-mbstring, php7.4-redis, php7.4-tokenizer, php7.4-xml, php7.4-zip, php7.4-pdo, php7.4-pgsql, php7.4-fileinfo, php7.4-imagick, php7.4, php7.4-fpm, php7.4-common
This is consistent with both Mastodon, Peertube and Mobilizon not working properly.
Well that’s … puzzling -_- On bullseye, package postgresql explicitly depends on postgresql-13
Can you share the output of dpkg --list | grep postgresql
Edit: also can you confirm that the error message you’re getting is precisely the one stating that it expected postgresql-13 to be there but is not ?
postgresql 13+225 all object-relational SQL database (supported version)
ii postgresql-11 11.16-0+deb10u1 amd64 object-relational SQL database, version 11 server
ii postgresql-11-postgis-2.5 2.5.1+dfsg-1 amd64 Geographic objects support for PostgreSQL 11
ii postgresql-11-postgis-2.5-scripts 2.5.1+dfsg-1 all Geographic objects support for PostgreSQL 11 -- SQL scripts
ii postgresql-13 13.7-0+deb11u1 amd64 The World's Most Advanced Open Source Relational Database
ii postgresql-client 13+225 all front-end programs for PostgreSQL (supported version)
ii postgresql-client-11 11.16-0+deb10u1 amd64 front-end programs for PostgreSQL 11
ii postgresql-client-13 13.7-0+deb11u1 amd64 front-end programs for PostgreSQL 13
ii postgresql-client-common 225 all manager for multiple PostgreSQL client versions
ii postgresql-common 225 all PostgreSQL database-cluster manager
ii postgresql-contrib 13+225 all additional facilities for PostgreSQL (supported version)
The error message given during migration is on yunopaste. Is there anything else I can do to diagnose?
Well so the error is not about postgresql-13 not being installed … Your error is about the locale issue initdb: could not find suitable text search configuration for locale "nn_NO.UTF-8" for which I have no fix right out of my head, apart from using localectl to tell the system to use en_US.UTF-8 everywhere
I did, and the error messages were basically the same. Thank you very much for your help, even if we have no solution yet. Would you like me to file a bug report?
So I pushed versions 4.4.2.3 (buster) and 11.0.9.2 (bullseye) which include the following fixes in an attempt to address major issues discussed since the stable release. However these are untested because I have no proper real-life server on which to test those. We are looking for tech-savvy users running a Raspberry Pi willing to test the Buster->Bullseye and make sure that those patch don’t make the server explode 
!
Great, I might be able to upgrade ! 
Il y a ~1600 paquets en hold.
Tous à cause des quelques “machin-truc-ynh-deps” liés aux applications. J’ai essayé de toute marqué en unhold, ça se remet au début de la migration.
Et les paquets que j’ai cité sont installé par la mise à jour (j’ai tenté de virer le paquet et sa dépendance, ça ne change rien).
Je peux retrouver le log complet.
To that postgresql problem:
# LC_ALL=C pg_upgradecluster -m upgrade 11 mainChecking for presence of required libraries fatal
Your installation references loadable libraries that are missing from the
new installation. You can add these libraries to the new installation,
or remove the functions using them from the old installation. A list of
problem libraries is in the file:
loadable_libraries.txt
could not load library "$libdir/postgis-2.5": ERROR: could not access file "$libdir/postgis-2.5": No such file or directory
In database: mobilizon
could not load library "$libdir/rtpostgis-2.5": ERROR: could not access file "$libdir/rtpostgis-2.5": No such file or directory
In database: mobilizon
Does that help in any way?
@chmeyer : hmm is it literally written $libdir ?
Naively this sounds like an issue with “postgis” (which as far as I know is a postgresql extension) being missing for version 13 ?
Can you share the output of dpkg --list | grep postgis ?
SInce the upgrade yesterday to the newest version with the postgress11-13 migration error,
my glitch-soc instance is dead
I tried to remove and reinstall this morning:
Die Applikation ‘Glitch-Soc’ installieren
1 20
08:17:44
glitchsoc wird installiert...
Validating installation parameters...
Storing installation settings..
Finding an available port...
Installing dependencies...
Installing rbenv with git...
Installing ruby-build with git...
Installing rbenv-aliases with git...
Installing xxenv-latest with git...
Installing Ruby-3.0.3
Configuring system user...
Creating a PostgreSQL database...
psql: error: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
Could not run script: /usr/share/yunohost/hooks/conf_regen/35-postgresql
psql: error: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
psql: error: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
Installation von glitchsoc fehlgeschlagen: Im Installationsscript ist ein Fehler aufgetreten
Entfernen der App nach fehlgeschlagener Installation...
Loading installation settings...
Stopping and removing the systemd service...
Removing the PostgreSQL database...
psql: error: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
Database glitchsoc_production not found
psql: error: could not connect to server: No such file or directory**
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
User glitchsoc not found
Removing app main directory...
ynh_secure_remove called with empty argument, ignoring.
Removing NGINX web server configuration...
'/etc/nginx/conf.d/fedi.caliandroid.de.d/glitchsoc.conf' wasn't deleted because it doesn't exist.
Removing dependencies...
Removing of Ruby-3.0.3
Removing of rbenv-
'/etc/apt/sources.list.d/glitchsoc.list' wasn't deleted because it doesn't exist.
'/etc/apt/preferences.d/glitchsoc' wasn't deleted because it doesn't exist.
Removing various files...
'/etc/cron.d/glitchsoc' wasn't deleted because it doesn't exist.
Removing the dedicated system user...
Removal of glitchsoc completed
dpkg --list | grep postgresql shows
rc postgresql-11 11.17-0+deb10u1 amd64 object-relational SQL database, version 11 server
ii postgresql-13 13.7-0+deb11u1 amd64 The World's Most Advanced Open Source Relational Database
ii postgresql-client-11 11.17-0+deb10u1 amd64 front-end programs for PostgreSQL 11
ii postgresql-client-13 13.7-0+deb11u1 amd64 front-end programs for PostgreSQL 13
ii postgresql-client-common 225 all manager for multiple PostgreSQL client versions
ii postgresql-common 225 all PostgreSQL database-cluster manager
@Aleks : Yes it’s exactly the content of the file loadable_libraries.txt, including literally $libdir.
# dpkg --list | grep postgis
ii postgis 3.1.1+dfsg-1 amd64 Geographic objects support for PostgreSQL
ii postgis-doc 3.1.1+dfsg-1 all Geographic objects support for PostgreSQL -- documentation
ii postgresql-11-postgis-2.5 2.5.1+dfsg-1 amd64 Geographic objects support for PostgreSQL 11
ii postgresql-11-postgis-2.5-scripts 2.5.1+dfsg-1 all Geographic objects support for PostgreSQL 11 -- SQL scripts
And this is, what trying to backup Mobilizon in this state says:
https://paste.yunohost.org/raw/rigeguqamu
Since this blocks migration from PostgreSQL 11 to 13, I now will try to deinstall Mobilizon and reinstall it after migration.